What changed in z/OS SRRAUDIT for ACF2 STIG V7R2V7R2 changes

z/OS SRRAUDIT for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 2 checks updated. It has 2 checks, against 2 in V7R1.

  • 0 added
  • 0 removed
  • 2 updated

Updated fields: Check text 2Fix text 2Title 2Discussion 2

Updated in V7R2 (2)

V-224342CAT IISRRAUDIT installation datasets must be properly protected.Title, Check text, Fix text, Discussion

Title

SRRAUDIT installation data sets must be properly protected.

Check text

Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(SRRPROD). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZSRR0000). Verify that the accesses to the SRRAUDIT 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 sets do not restrict READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors. The ACF2 datadataset set rules for the datadatasets sets do not restrict WRITE and/or greater access to systems programming personnel. The ACF2 datadataset set rules for the datadatasets sets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

Fix text

The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation datadatasets sets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to security personnel, production control and scheduling personnel, and auditors. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have WRITE and/or greater access, and, if required, ensure that all WRITE and/or greater accesses are logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data setsdatasets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system. (Note: The datadatasets sets and/or datadataset set prefixes identified below are examples of a possible installation. The actual datadatasets sets and/or prefixes are determined when the product is actually installed on a system through the product's installation guide and can be site specific.) DataDatasets sets to be protected will be: SYS2.SRRAUDIT. The following commands are provided as a sample for implementing datadataset set controls: $KEY(SYS2) SET RULE $KEY(S2S) $PREFIX(SYS2) SRRAUDIT.- UID(audtaudt) R(A) E(A) DATA(DEFAULT Auditor) SRRAUDIT.- UID(pcspaudt) R(A) E(A) DATA(DEFAULT Production control and Scheduling) SRRAUDIT.- UID(secaaudt) R(A) E(A) DATA(DEFAULT Security) SRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) SRRAUDIT.- UID(tstcaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Trusted STCs)

Discussion

SRRAUDIT 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-224343CAT IISRRAUDIT User datasets are not properly protected.Title, Check text, Fix text, Discussion

Title

SRRAUDIT User data sets are not properly protected.

Check text

a) Refer to the following report produced by the Datadataset Set and Resource Data Collection: - SENSITVE.RPT(SRRUSER). Automated Analysis Refer to the following report produced by the Datadataset Set and Resource Data Collection: - PDI(ZSRR0002). b) Verify that access to the SRRAUDIT User datadatasets setsis are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 datadataset set rules for the datadatasets sets does not restrict READ, UPDATE, and/or ALTERgreater access to systems programming personnel, security personnel, and auditors. ___ The ACF2 datadataset set rules for the datadatasets sets do not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged. b) If all of the above are untrue, there is NO FINDING. c) If any of the above is true, this is a FINDING.

Fix text

The IAOISSO will ensure that readREAD, updateUPDATE, and allocateALTER access to program product user datadatasets sets is limited to Systemsystems Programmersprogrammers, Securitysecurity Personnelpersonnel, and Auditorsauditors, and all updateWRITE and/or allocategreater access is logged. The installing Systemsystems Programmerprogrammer will identify and document the product user datadatasets sets and categorize them according to who will have updateWRITE and/or altergreater access and, if required, that all updateWRITE and/or allocategreater access is logged. HeThe systems programmer will identify if any additional groups have updateUPDATE 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. DataDataset set prefix to be protected will be: SYS3.SRRAUDIT. If doing a full SRR review using the z/OS STIG Instruction, the following datadataset set prefix to be protected will be: SYS3.FSO. The following commands are provided as a sample for implementing dataset controls: SET RULE $KEY(S3S) $PREFIX(SYS3) SRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) SRRAUDIT.- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) SRRAUDIT.- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor) $KEY(S3F) $PREFIX(SYS3) FSO- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) FSO- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) FSO- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor)

Discussion

SRRAUDIT User datadatasets sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

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.