BMC CONTROL-O Started Task name is not properly identified/defined to the system ACP.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224413 | ZCTOR030 | SV-224413r1144812_rule | CCI-000764 | medium |
| Description | ||||
| BMC CONTROL-O requires a started task that will be restricted to certain resources, data sets, 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. | ||||
| STIG | Date | |||
| z/OS BMC CONTROL-O for RACF Security Technical Implementation Guide | 2025-09-27 | |||
Details
Check Text (C-224413r1144812_chk)
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
Fix Text (F-26078r1144811_fix)
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