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

V-224245

CAT II (Medium)

BMC IOA STC datasets must be properly protected.

Rule ID

SV-224245r1141529_rule

STIG

z/OS BMC IOA for ACF2 Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-001499

Discussion

BMC IOA STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these 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(IOASTC).

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

- PDI(ZIOA0001).

Verify that the accesses to the BMC IOA STC datasets are properly restricted. If the following guidance is true, this is not a finding.

The ACF2 dataset access authorizations restrict READ access to auditors and BMC users

The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel.

The ACF2 dataset access authorizations restrict UPDATE access to the BMC STCs, batch users, and BMC administrators.

Fix Text

Ensure that WRITE and/or greater access to BMC IOA STC datasets is limited to systems programmers only. UPDATE access can be given to BMC STCs, batch users, and BMC administrators. READ access can be given to auditors and BMC users.

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 WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system.

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

Datasets to be protected will be: 
SYS3.IOA.*.IOAO

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

$KEY(SYS3)
IOA.-.IOAO.- UID(<syspaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAO.- UID(<tstcaudt>) R(A) W(A) A(A) E(A)
IOA.-.IOAO.- UID(BMC STCs) R(A) W(A) E(A)
IOA.-.IOAO.- UID(<bmcadmin>)R(A) W(A) E(A)
IOA.-.IOAO.- UID(<audtaudt>)R(A) E(A)   
IOA.-.IOAO.- UID(<bmcuser>) R(A) E(A)