SRRAUDIT installation datasets must be properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224342	SRG-OS-000080	ZSRRA000	SV-224342r1141639_rule	2025-09-25	7

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

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

ℹ️ Check

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

✔️ Fix
The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation datasets 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 datasets, 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS2.SRRAUDIT The following commands are provided as a sample for implementing dataset 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)

✔️ Fix

The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation datasets 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 datasets, 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 datasets, 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 datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS2.SRRAUDIT The following commands are provided as a sample for implementing dataset 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)