STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS SRRAUDIT for ACF2 Security Technical Implementation Guide

V-224343

CAT II (Medium)

SRRAUDIT User datasets are not properly protected.

Rule ID

SV-224343r1144089_rule

STIG

z/OS SRRAUDIT for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499

Discussion

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.

Check Content

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 Text

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)