STIGUI
V-224129CAT II — Medium severitySV-224129r1144181_rule

BMC CONTROL-O Started Task name is not properly identified / defined to the system ACP.

Rule version ZCTOA030 · STIG v7 · 2025-09-27

Discussion

BMC CONTROL-O requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as a userid to the system ACP allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities could compromise the operating system environment, ACP, and customer data.

Check

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

Fix

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

Identifiers

Group ID
V-224129
Group title
SRG-OS-000104
Rule ID
SV-224129r1144181_rule
Check ID
C-25802r1144180_chk
Fix ID
F-25790r1141487_fix