STIGQter: STIG Summary: z/OS BMC CONTROL-O for ACF2 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-224129r1144181_rule

Vulnerability Number

V-224129

Group Title

SRG-OS-000104

Rule Version

ZCTOA030

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 systems 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.

Example:

SET LID
CHANGE CONTROLO STC MUSASS NO-SMC

Check Contents

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

- ACF2CMDS.RPT(ATTSTC).

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

STC
MUSASS
NO-SMC

Vulnerability Number

V-224129

Documentable

False

Rule Version

ZCTOA030

Severity Override Guidance

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

- ACF2CMDS.RPT(ATTSTC).

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

STC
MUSASS
NO-SMC

Check Content Reference

M

Target Key

4106