Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS SRRAUDIT for RACF Security Technical Implementation Guide

V7R2 · · · Released 01 Oct 2025 · 2 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V7R1 · 02 Apr 2025 ✎ 2

Comparison against the immediately-prior release (V7R1). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 2

  • V-224535 Medium check SRRAUDIT installation data sets must be properly protected.
  • V-224536 Medium checkfix SRRAUDIT User data sets are not properly protected.
Sort by
b
SRRAUDIT installation data sets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224535 - SV-224535r1145277_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZSRRR000
Vuln IDs
  • V-224535
  • V-16932
Rule IDs
  • SV-224535r1145277_rule
  • SV-21732
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.
Checks: C-26218r1144981_chk

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: F-26206r1145276_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

b
SRRAUDIT User data sets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224536 - SV-224536r1144986_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZSRRR002
Vuln IDs
  • V-224536
  • V-21592
Rule IDs
  • SV-224536r1144986_rule
  • SV-23903
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.
Checks: C-26219r1144984_chk

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: F-26207r1144985_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)