SRRAUDIT User data sets are not properly protected.

From z/OS SRRAUDIT for RACF STIG

Part of ZB000002

Associated with IA controls: ECCD-2, ECAR-2, ECCD-1, ECAR-1, DCSL-1

SV-23903r2_rule SRRAUDIT User data sets are not properly protected.

Vulnerability discussion

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 content

a) 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) b) Verify that access to the SRRAUDIT User data sets are properly restricted. ___ The RACF data set rules for the data sets does not restrict READ, UPDATE, and/or ALTER access to systems programming personnel, security personnel, and auditors. ___ The RACF data set rules for the data sets do not specify that all (i.e., failures and successes) UPDATE and/or ALTER 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 IAO 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 update and alter access is logged. The installing System Programmer will identify and document the product user data sets and categorize them according to who will have update and alter access and if required that all update and alter 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 IAO 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 dataset 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 dataset 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)

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer