STIGViewer Support

SRRAUDIT User datasets are not properly protected.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-224343ZSRRA002SV-224343r1144089_ruleCCI-001499medium
Description
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.
STIGDate
z/OS SRRAUDIT for ACF2 Security Technical Implementation Guide2025-09-25

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CHG-04.5Library Privileges
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (56) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(7)Role-based Access Control
1.00
AC-4Information Flow Enforcement
1.00
AC-6(10)Prohibit Non-privileged Users from Executing Privileged Functions
1.00

+46 more (top 10 by confidence shown)

CCI1 mapping

Details

Check Text (C-224343r1144089_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 Text (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)