SRRAUDIT installation data sets must be properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224535	SRG-OS-000080	ZSRRR000	SV-224535r1070158_rule	2025-02-24	7

Description
SRRAUDIT installation 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.

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

ℹ️ Check

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

✔️ Fix
The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation data 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 data sets and categorize them according to who will have WRITE and/or greater access and, if required, 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 sets, 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 data sets and/or data set prefixes identified below are examples of a possible installation. The actual 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 sets to be protected will be: SYS2.SRRAUDIT. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.SRRAUDIT.' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('SRRAUDIT Install DS') pe 'SYS2.SRRAUDIT.' id(syspaudt tstcaudt) acc(a) pe 'SYS2.SRRAUDIT.' id(audtaudt pcspaudt) acc(r) pe 'SYS2.SRRAUDIT.' id(secaaudt) acc(r) setr generic(dataset) refresh

✔️ Fix

The ISSO will ensure WRITE and/or greater access to SRRAUDIT installation data 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 data sets and categorize them according to who will have WRITE and/or greater access and, if required, 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 sets, 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 data sets and/or data set prefixes identified below are examples of a possible installation. The actual 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 sets to be protected will be: SYS2.SRRAUDIT. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.SRRAUDIT.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('SRRAUDIT Install DS') pe 'SYS2.SRRAUDIT.**' id(syspaudt tstcaudt) acc(a) pe 'SYS2.SRRAUDIT.**' id(audtaudt pcspaudt) acc(r) pe 'SYS2.SRRAUDIT.**' id(secaaudt) acc(r) setr generic(dataset) refresh