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

z/OS SRRAUDIT for ACF2 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-224342 Medium descriptioncheckfix SRRAUDIT installation datasets must be properly protected.
  • V-224343 Medium descriptioncheckfix SRRAUDIT User datasets are not properly protected.
Sort by
b
SRRAUDIT installation datasets must be properly protected.
CM-5 - Medium - CCI-001499 - V-224342 - SV-224342r1141639_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZSRRA000
Vuln IDs
  • V-224342
  • V-16932
Rule IDs
  • SV-224342r1141639_rule
  • SV-21724
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.
Checks: C-26019r1141637_chk

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: F-26007r1141638_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)

b
SRRAUDIT User datasets are not properly protected.
CM-5 - Medium - CCI-001499 - V-224343 - SV-224343r1144089_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZSRRA002
Vuln IDs
  • V-224343
  • V-21592
Rule IDs
  • SV-224343r1144089_rule
  • SV-23902
SRRAUDIT User datasets provide the capability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to their datasets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26020r1141640_chk

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(SRRUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZSRR0002). Verify that access to the SRRAUDIT User datasets is properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset rules for the datasets restrict READ and/or greater access to systems programming personnel, security personnel, and auditors. 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: F-26008r1144089_fix

The ISSO will ensure that READ, UPDATE, and ALTER access to program product user datasets is limited to systems programmers, security personnel, and auditors, and all WRITE and/or greater access is logged. The installing systems programmer will identify and document the product user datasets 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. The systems programmer will identify if any additional groups have UPDATE access for specific datasets, and once documented will work with the ISSO to ensure that they are properly restricted to the ACP (Access Control Program) active on the system. Dataset prefix to be protected will be: SYS3.SRRAUDIT If doing a full SRR review using the z/OS STIG Instruction, the following dataset prefix to be protected will be: SYS3.FSO The following commands are provided as a sample for implementing dataset controls: SET RULE $KEY(S3S) $PREFIX(SYS3) SRRAUDIT.- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) SRRAUDIT.- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) SRRAUDIT.- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor) $KEY(S3F) $PREFIX(SYS3) FSO- UID(syspaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT SYSPROG) FSO- UID(secaaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Security) FSO- UID(audtaudt) R(A) W(L) A(L) E(A) DATA(DEFAULT Auditor)