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 name is not properly identified/defined to the system ACP.

DISA Rule

SV-224413r1144812_rule

Vulnerability Number

V-224413

Group Title

SRG-OS-000104

Rule Version

ZCTOR030

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 properly Identified/defined to the System ACP.

If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

A sample is provided here:

au CONTROLO name('stc, BMC CONTROL-O') owner(stc) dfltgrp(stc) nopass

Check Contents

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

- RACFCMDS.RPT(LISTUSER).

Verify that the userid(s) for the BMC CONTROL-O started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Vulnerability Number

V-224413

Documentable

False

Rule Version

ZCTOR030

Severity Override Guidance

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

- RACFCMDS.RPT(LISTUSER).

Verify that the userid(s) for the BMC CONTROL-O started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED

Check Content Reference

M

Target Key

4138