V7R2 changes
z/OS CA Auditor for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 3 checks updated. It has 3 checks, against 3 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 3 updated
Updated fields: Check text 3Fix text 2Title 2Discussion 2
Updated in V7R2 (3)
V-224265CAT IICA Auditor installation datasets are not properly protected.Title, Check text, Fix text, Discussion
Title
CA Auditor installation data sets are not properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(ADTRPT).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZADT0000).
Verify that the accesses to the CA Auditor installation datadatasets sets are properly restricted.
If the following guidance is true, this is not a finding.
___
The ACF2 datadataset set rules for the datadatasets setsrestrict restricts READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restrictsWRITE UPDATE and/or ALTERgreater access to systems programming personnel.
___ The ACF2 datadataset set rules for the datadatasets sets specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access areis logged.
Fix text
The ISSO will ensure that updateWRITE and/or allocategreater access to CA Auditor installation datadatasets sets is limited to systems programmers only, and all updateWRITE and/or allocategreater 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 datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.
DataDatasets sets to be protected will be:
SYS2.EXAMINE
SYS2A.EXAMINE
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS2)
EXAMINE.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
EXAMINE.- UID(<audtaudt>) R(A) E(A)
EXAMINE.- UID(<secaaudt>) R(A) E(A)
EXAMINE.- UID(EXAMMON) R(A) E(A)
$KEY(SYS2A)
EXAMINE.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
EXAMINE.- UID(<audtaudt>) R(A) E(A)
EXAMINE.- UID(<secaaudt>) R(A) E(A)
EXAMINE.- UID(EXAMMON) R(A) E(A)
Discussion
CA Auditor installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
V-224266CAT IICA Auditor User datasets are not properly protected.Title, Check text, Fix text, Discussion
Title
CA Auditor User data sets are not properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(ADTUSER).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZADT0002).
Verify that the accesses to the CA Auditor User datadatasets sets are properly restricted. If the following guidance is true, this is not a finding.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restrictsWRITE UPDATE and/or ALTERgreater access to systems programming personnel, security personnel, and auditors.
Fix text
The IAOISSO will ensure that updateWRITE and/or allocategreater access to CA Auditor User datadatasets setsis are limited to Systemsystems Programmersprogrammers, security personnel, and auditors.
The installing Systemssystems Programmerprogrammer will identify and document the product datadatasets, sets and categorize them according to who will have updateWRITE and/or altergreater access, and if required, ensure that all updateWRITE and/or allocategreater access is logged. He The systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data setsdatasets, and once documented he will work with the IAOISSO to seeensure that they are properly restricted to the ACP (Access Control Program) active on the system.
DataDatasets sets to be protected will be:
dataasets
SYS3.EXAMINE
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(SYS3)
EXAMINE.- UID(<syspaudt>) R(A) W(A) A(A) E(A)
EXAMINE.- UID(<audtaudt>) R(A) W(A) A(A) E(A)
EXAMINE.- UID(<secaaudt>) R(A) W(A) A(A) E(A)
Discussion
CA Auditor User datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.
V-224267CAT IICA Auditor resources are not properly defined and protected.Check text
Check text
Refer to the following report produced by the ACF2dataset Data Collection and Data Set and Resource Data Collection:
- SENSITVE.RPT(ZADT0020).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.
Automated Analysis
Refer to the following report produced by the Datadataset 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 ACF2 rules for the resources specify a default access of NONE.
___ The ACF2 rules for the resources are restricted access to systems programmers, auditors, and security personnel.
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.