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

V-224301

CAT II (Medium)

IBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.

Rule ID

SV-224301r1141523_rule

STIG

z/OS HCD for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000213CCI-002234

Discussion

Program products can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to program product resources could result in the compromise of the operating system environment, and compromise the confidentiality 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 non-systems 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(FACILITY).
- ACF2CMDS.RPT(RESOURCE) - Alternate report.

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

- PDI(ZHCD0020).

Review the following items for the IBM Hardware Configuration Definition (HCD) resources in the FACILITY resource class, TYPE(FAC). If the following guidance is true, this is not a finding.

The ACF2 rules for the CBD resource specify a default access of NONE.

No ACF2 rules allow access to the CBD resource.

The ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.

The ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.

Fix Text

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

The ACF2 rules for the CBD resource specify a default access of NONE.

No ACF2 rules allow access to the CBD resource.

Example:

SET R(FAC)
$KEY(CBD) TYPE(FAC)
 - UID(*) PREVENT DATA(SRR FINDING FOR HCD)

The ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.

The ACF2 rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.

Example:

SET R(FAC)
$KEY(CBD) TYPE(FAC)
CPC.IOCDS.- UID(syspaudt) SERVICE(READ,UPDATE) LOG
CPC.IOCDS.- UID(operaudt) SERVICE(READ) ALLOW
CPC.IOCDS.- UID(autoaudt) SERVICE(READ) ALLOW
CPC.IPLPARM.- UID(syspaudt) SERVICE(READ,UPDATE) LOG
CPC.IPLPARM.- UID(operaudt) SERVICE(READ) ALLOW
CPC.IPLPARM.- UID(autoaudt) SERVICE(READ) ALLOW