z/OS TADz for ACF2 Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
Digest of Updates ✎ 1
Comparison against the immediately-prior release (V6R7). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.
Content changes 1
- V-224344 Medium descriptioncheckfix Tivoli Asset Discovery for z/OS (TADz) Install data sets are not properly protected.
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- ZTADA000
- Vuln IDs
-
- V-224344
- V-16932
- Rule IDs
-
- SV-224344r1081046_rule
- SV-28469
Checks: C-26021r1070063_chk
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0000) Verify that access to the TADz Install data sets are properly restricted. The ACF2 data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. The ACF2 data set rules for the data sets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. If all of the above are untrue, this is not a finding. If any of the above is true, this is a finding.
Fix: F-26009r1081046_fix
The ISSO will ensure that update and allocate access to program product data sets is limited to system programmers only, and all update and allocate access is logged. Auditors should have read access. The installing systems programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. The installing systems programmer will identify if any additional groups have update access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. Data sets to be protected will be: SYS2.TADZ SYS2.TADZ .V-.SHSIMOD1 SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: $KEY(SYS2) TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.V-.SHSIMOD1 UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.- UID(audtaudt) R(A) E(A) $KEY(SYS3) TADZ.- UID(syspaudt) R(A) W(L) A(L) E(A) TADZ.- UID(audtaudt) R(A) E(A)
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- ZTADA001
- Vuln IDs
-
- V-224345
- V-17067
- Rule IDs
-
- SV-224345r958616_rule
- SV-28547
Checks: C-26022r868234_chk
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(TADZSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZTAD0001) For all (TADz) STC and/or batch data sets: If the UPDATE or greater access is restricted to systems programming personnel and the product STC(s) and/or batch job(s) this is not a finding. If any job scheduling products are in use and access is restricted to READ this is not a finding. If auditors have READ access this is not a finding.
Fix: F-26010r868235_fix
Grant update and alter access to Tivoli Asset Discovery for z/OS (TADz) STC and/or batch data sets are limited to system programmers and TADz STC and/or batch jobs only. Grant read access to any scheduling products that are in use. Grant read access to auditors at the ISSO's discretion. Identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. Identify if any additional groups have update access for specific data sets, and assure that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.TADZ The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) TADZ.- UID(syspaudt) R(A) W(A) A(A) E(A) TADZ.- UID(audtaudt) R(A) E(A) TADZ.-.UM.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.-.IQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.-.UIQ.- UID(batchid TADZINQ) R(A) W(A) A(A) E(A) TADZ.- UID(stc id TADZMON) R(A) W(A) A(A) E(A)
- RMF Control
- IA-2
- Severity
- M
- CCI
- CCI-000764
- Version
- ZTADA030
- Vuln IDs
-
- V-224346
- V-17452
- Rule IDs
-
- SV-224346r958482_rule
- SV-28612
Checks: C-26023r520895_chk
Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(LOGONIDS) Ensure the following field is completed for each STC logonid for the product: STC Ensure the following field is completed for each Batch logonid for the product: JOB If the logonids specified in (b) and/or (c) have all the required field is completed, this is not a FINDING. If the logonids specified in (b) and/or (c) do not have the above field completed, this is a FINDING.
Fix: F-26011r520896_fix
The TADz system programmer and the ISSO will ensure that a product's Started Task(s) is properly identified / defined to the System ACP. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified. Example: SET LID CHANGE TADZMON STC