z/OS CA Auditor for RACF Security Technical Implementation Guide
Pick two releases to diff their requirements.
Open a previous version of this STIG.
Digest of Updates ✎ 3
Comparison against the immediately-prior release (V7R1). 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 3
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- ZADTR000
- Vuln IDs
-
- V-224430
- V-16932
- Rule IDs
-
- SV-224430r1145195_rule
- SV-31919
Checks: C-26107r1144641_chk
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ADTRPT). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0000). Verify that the accesses to the CA Auditor installation data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.
Fix: F-26095r1145194_fix
The ISSO will ensure that WRITE and/or greater access to CA Auditor installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, security administrators, and/or CA Auditor's STCs and batch users. The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS2.EXAMINE SYS2A.EXAMINE The following commands are provided as a sample for implementing data set controls: ad 'SYS2.EXAMINE.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: CA Auditor/Examine') pe 'SYS2.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS2.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r) ad 'SYS2A.EXAMINE.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) - data('Vendor DS Profile: CA Auditor/Examine') pe 'SYS2A.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS2A.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r) setr generic(dataset) refresh
- RMF Control
- CM-5
- Severity
- M
- CCI
- CCI-001499
- Version
- ZADTR002
- Vuln IDs
-
- V-224431
- V-21592
- Rule IDs
-
- SV-224431r1145197_rule
- SV-32206
Checks: C-26108r1144644_chk
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ADTUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0002). Verify that the accesses to the CA Auditor User data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel, security personnel and auditors.
Fix: F-26096r1145196_fix
The ISSO will ensure that WRITE and/or greater access to CA Auditor User data sets are limited to System Programmers, security personnel and auditors. The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.EXAMINE The following commands are provided as a sample for implementing data set controls: ad 'SYS3.EXAMINE.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA Auditor') pe 'SYS3.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS3.EXAMINE.**' id(<audtaudt> <secaaudt>) acc(A) setr generic(dataset) refresh
- RMF Control
- AC-3
- Severity
- M
- CCI
- CCI-000213
- Version
- ZADTR020
- Vuln IDs
-
- V-224432
- V-17947
- Rule IDs
-
- SV-224432r1144649_rule
- SV-32209
Checks: C-26109r1144647_chk
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ZADT0020). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0020). Verify that the access to the LTDMMAIN resource in the PROGRAM resource class is restricted. If the following guidance is true, this is not a finding. The RACF rules for the resources specify a default access of NONE. The RACF rules for the resources are restricted access to system programmers, auditors, and security personnel. All RACF rules are defined with UACC(NONE).
Fix: F-26097r1144648_fix
The ISSO will verify that the LTDMMAIN resource in the PROGRAM resource class is restricted to system programmers, auditors, and security personnel. The RACF rules for the LTDMMAIN resource specify a default access of NONE and no RACF rules that allow access to the LTDMMAIN resource. Example: rdef program LTDMMAIN uacc(none) owner(admin) audit(failures(read)) - data('added per PDI ZADT0020') The RACF rules for the LTDMMAIN resource is restricted access to systems programmers, auditors, and security personnel with access of READ. All RACF rules are defined with UACC(NONE). Example: rdef program ltdmmain - addmem('SYS2A.EXAMINE.V120SP01.CAILIB'//nopadchk) - data('Required by SRR PDI ZADTR020') - audit(failures(read)) uacc(none) owner(admin) pe LTDMMAIN cl(program) id(syspaudt) acc(r) pe LTDMMAIN cl(program) id(audtaudt) acc(r) pe LTDMMAIN cl(program) id(secaaudt) acc(r) setr when(program) ref