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 ROSCOE for ACF2 Security Technical Implementation Guide

V-224336

CAT II (Medium)

ROSCOE Install datasets are not properly protected.

Rule ID

SV-224336r1141623_rule

STIG

z/OS ROSCOE for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499CCI-002234

Discussion

ROSCOE Install 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(ROSRPT).

Automated Analysis
Refer to the following report produced by the dataset and Resource Data Collection:

- PDI(ZROS0000).

Verify that access to the ROSCOE Install datasets is properly restricted. If the following guidance is true, this is not a finding.
 
The ACF2 dataset rules for the datasets 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 Text

The ISSO will ensure that WRITE and/or greater access to program product datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. Security personnel and auditors should have READ access.

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 access is logged. The installing systems programmer will identify if any additional groups have UPDATE 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.

Datasets to be protected will be: 
SYS2.ROSCOE
SYS2A.ROSCOE
SYS3.ROSCOE 
SYS3A.ROSCOE

The following commands are provided as a sample for implementing dataset controls: 

$KEY(SYS2)
ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A)
ROSCOE.- UID(secaaudt) R(A)  E(A)
ROSCOE.- UID(audtaudt) R(A)  E(A)

$KEY(SYS2A)
ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A)
ROSCOE.- UID(secaaudt) R(A)  E(A)
ROSCOE.- UID(audtaudt) R(A)  E(A)

$KEY(SYS3)
ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A)
ROSCOE.- UID(secaaudt) R(A)  E(A)
ROSCOE.- UID(audtaudt) R(A)  E(A)

$KEY(SYS3A)
ROSCOE.- UID(syspaudt) R(A) W(L) A(L) E(A)
ROSCOE.- UID(secaaudt) R(A)  E(A)
ROSCOE.- UID(audtaudt) R(A)  E(A)