z/OS SRRAUDIT for ACF2 STIG Version Comparison

There are 3 differences between versions v6 r5 (Nov. 23, 2022) (the "left" version) and v7 r2 (Oct. 1, 2025) (the "right" version).

Check ZSRRA000 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

SRRAUDIT installation datasets data sets must be properly protected.

Check Content

Refer to the following report produced by the dataset Data Set and Resource Data Collection: - SENSITVE.RPT(SRRPROD) Automated SENSITVE.RPT(SRRPROD). Automated Analysis Refer to the following report produced by the dataset Data Set and Resource Data Collection: - PDI(ZSRR0000) Verify PDI(ZSRR0000). Verify that the accesses to the SRRAUDIT installation datasets data sets are properly restricted. If the following guidance is true, this is not a finding. ___ finding. The The ACF2 dataset data set rules for the datasets data sets do not restrict READ access to systems programming personnel, domain level production control and scheduling personnel, security personnel, and auditors. ___ auditors. The The ACF2 dataset data set rules for the datasets data sets do not restrict WRITE and/or greater access to systems programming personnel. ___ personnel. The The ACF2 dataset data set rules for the datasets data sets do not specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

Discussion

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

Fix

The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation datasets data sets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to Security security personnel, Production production Control control and Scheduling scheduling personnel, and Auditors. auditors. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product datasets, data sets and categorize them according to who will have WRITE and/or greater access access, and, 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 datasets, data sets, and once documented documented, will work with the ISSO to ensure they are properly restricted to the ACP (Access Access Control Program) Program (ACP) active on the system. (Note: The datasets data sets and/or dataset data set prefixes identified below are examples of a possible installation. The actual datasets data 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.) Data specific.) Datasets sets to be protected will be: SYS2.SRRAUDIT. The be: SYS2.SRRAUDIT The following commands are provided as a sample for implementing dataset data 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)