STIGQter: STIG Summary: z/OS BMC CONTROL-O for RACF Security Technical Implementation Guide Version: 7 Release: 2 Benchmark Date: 01 Oct 2025:

BMC CONTROL-O Started task(s) must be properly defined to the STARTED resource class for RACF.

DISA Rule

SV-224414r1144815_rule

Vulnerability Number

V-224414

Group Title

SRG-OS-000104

Rule Version

ZCTOR032

Severity

CAT II

CCI(s)

• CCI-000764 - Uniquely identify and authenticate organizational users and associate that unique identification with processes acting on behalf of those users.

Weight

10

Fix Recommendation

The BMC CONTROL-O system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP.

A unique userid must be assigned for the BMC CONTROL-O started task(s) thru a corresponding STARTED class entry.

The following sample set of commands is shown here as a guideline:

rdef started CONTROLO.** uacc(none) owner(admin) audit(all(read)) stdata(user(CONTROLO) group(stc))

setr racl(started) ref

Check Contents

Refer to the following report produced by the RACF Data Collection:

- DSMON.RPT(RACSPT).

Automated Analysis
Refer to the following report produced by the RACF Data Collection:

- PDI(ZCTO0032).

Verify that the BMC CONTROL-O started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Vulnerability Number

V-224414

Documentable

False

Rule Version

ZCTOR032

Severity Override Guidance

Refer to the following report produced by the RACF Data Collection:

- DSMON.RPT(RACSPT).

Automated Analysis
Refer to the following report produced by the RACF Data Collection:

- PDI(ZCTO0032).

Verify that the BMC CONTROL-O started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

Check Content Reference

M

Target Key

4138