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-224338

CAT II (Medium)

ROSCOE resources must be properly defined and protected.

Rule ID

SV-224338r1141629_rule

STIG

z/OS ROSCOE for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000213CCI-002234

Discussion

ROSCOE can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product resources could result in the compromise of the operating system environment, and compromise the confidentiality and integrity of customer data. Many utilities assign resource controls that can be granted to systems programmers only in greater than read authority. Resources are also granted to certain nonsystems personnel with read only authority.

Check Content

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

- SENSITVE.RPT(ZROS0020).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.

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

- PDI(ZROS0020).

Verify all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in the CA ROSCOE Resources table in the z/OS STIG Addendum.

Note: Wherever an access or user group is missing, use the Site Security Plan to determine access and/or user group. 

If the following guidance is true, this is not a finding.

The ACF2 resources are defined with a default access of PREVENT.

The ACF2 resource access authorizations restrict access to the appropriate personnel.

The ACF2 resource logging is correctly specified.

Fix Text

The ISSO will work with the systems programmer to verify that the following are properly specified in the Access Control Program (ACP).

(Note: The resource type, resources, and/or resource prefixes identified below are examples of a possible installation. The actual resource type, resources, and/or resource prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.)

Ensure that all ROSCOE resources and/or generic equivalent are properly protected according to the requirements specified in CA ROSCOE Resources table in the z/OS STIG Addendum.

Use CA ROSCOE Resources table in the z/OS STIG Addendum. This table lists the resources, access requirements, and logging requirements for ROSCOE ensure the following guidelines are followed:

The ACF2 resources are defined with a default access of PREVENT.

The ACF2 resource access authorizations restrict access to the appropriate personnel.

The ACF2 resource logging is correctly specified.

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

$KEY(rosid) TYPE(ROS)
ROSCMD.ETSO UID(*) SEVICE(READ)
ROSCMD.MONITOR.- UID(syspaudt) ALLOW
ROSCMD.MONITOR.AMS UID(syspaudt) ALLOW
ROSCMD.MONITOR.AMS UID(*) SEVICE(READ)
ROSCMD.- UID(syspaudt) ALLOW
- UID(*) PREVENT