SRRAUDIT User data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224536	SRG-OS-000259	ZSRRR002	SV-224536r1144986_rule	2025-09-27	7

Description
SRRAUDIT User data sets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their 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(SRRUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSRR0002). Verify that access to the SRRAUDIT User data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict READ and/or greater access to systems programming personnel, security personnel, and auditors. The RACF data set rules for the data sets 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 Data Set and Resource Data Collection: - SENSITVE.RPT(SRRUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZSRR0002). Verify that access to the SRRAUDIT User data sets are properly restricted. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict READ and/or greater access to systems programming personnel, security personnel, and auditors. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access will be logged.

✔️ Fix
The ISSO will ensure that READ, UPDATE, and ALTER access to program product user data sets is limited to System Programmers, Security Personnel, and Auditors and all WRITE and/or greater access is logged. The installing System Programmer will identify and document the product user data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He will identify if any additional groups have UPDATE access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program ) active on the system. Data set prefix to be protected will be: SYS3.SRRAUDIT. The following commands are provided as a sample for implementing data set controls: ad 'sys3.srraudit.' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Vendor DS Profile: SRRAUDIT - security automation project, sso-developed self-audit toolkit') pe 'sys3.srraudit.' id(syspaudt secaaudt audtaudt) acc(a) If doing a full SRR review using the z/OS STIG Instruction, the following data set prefix to be protected will be: SYS3.FSO. The following commands are provided as a sample for implementing data set controls: ad 'sys3.fso.' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Used for full SRR Review') pe 'sys3.fso.' id(syspaudt secaaudt audtaudt) acc(a)

✔️ Fix

The ISSO will ensure that READ, UPDATE, and ALTER access to program product user data sets is limited to System Programmers, Security Personnel, and Auditors and all WRITE and/or greater access is logged. The installing System Programmer will identify and document the product user data sets and categorize them according to who will have WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He will identify if any additional groups have UPDATE access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program ) active on the system. Data set prefix to be protected will be: SYS3.SRRAUDIT. The following commands are provided as a sample for implementing data set controls: ad 'sys3.srraudit.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Vendor DS Profile: SRRAUDIT - security automation project, sso-developed self-audit toolkit') pe 'sys3.srraudit.**' id(syspaudt secaaudt audtaudt) acc(a) If doing a full SRR review using the z/OS STIG Instruction, the following data set prefix to be protected will be: SYS3.FSO. The following commands are provided as a sample for implementing data set controls: ad 'sys3.fso.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Used for full SRR Review') pe 'sys3.fso.**' id(syspaudt secaaudt audtaudt) acc(a)