What changed in z/OS CA Auditor for RACF STIG V7R2V7R2 changes

z/OS CA Auditor for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 3 checks updated. It has 3 checks, against 3 in V7R1.

  • 0 added
  • 0 removed
  • 3 updated

Updated fields: Check text 3Fix text 3Discussion 1

Updated in V7R2 (3)

V-224430CAT IICA Auditor installation data sets are not properly protected.Check text, Fix text

Check text

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 restrictsrestrict READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users. ___ The RACF data set rules for the data sets restrictsrestrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel. ___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access are logged.

Fix text

The ISSO will ensure that updateWRITE and/or altergreater access to CA Auditor installation data sets are limited to systems programmers only, and all updateWRITE and/or altergreater access is logged. ReadREAD 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 updateWRITE and/or altergreater access and if required that all updateWRITE and/or altergreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater 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(&ltsyspaudt>) acc(a) pe 'SYS2.EXAMINE.**' id(&ltaudtaudt> &ltsecaaudt> 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(&ltsyspaudt>) acc(a) pe 'SYS2A.EXAMINE.**' id(&ltaudtaudt> &ltsecaaudt> EXAMMON) acc(r) setr generic(dataset) refresh

V-224431CAT IICA Auditor User data sets are not properly protected.Check text, Fix text, Discussion

Check text

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 UPDATEWRITE and/or ALTERgreater access to systems programming personnel, security personnel and auditors.

Fix text

The IAOISSO will ensure that updateWRITE and/or altergreater 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 updateWRITE and/or altergreater access and if required that all updateWRITE and/or altergreater access is logged. He will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented he will work with the IAOISSO 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(&ltsyspaudt>) acc(a) pe 'SYS3.EXAMINE.**' id(&ltaudtaudt> &ltsecaaudt>) acc(A) setr generic(dataset) refresh

Discussion

CA Auditor User data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

V-224432CAT IICA Auditor resources are not properly defined and protected.Check text, Fix text

Check text

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 sytemsystem programmers, auditors, and security personnel. ___ All RACF rules are defined with UACC(NONE).

Fix text

The ISSO will verify that the LTDMMAIN resource in the PROGRAM resource class is restricted to sytemsystem 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

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.