BMC CONTROL-O Started Task name is not properly identified / defined to the system ACP.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224413 | SRG-OS-000104 | ZCTOR030 | SV-224413r958482_rule | 2025-02-24 | 7 |
| Description |
|---|
| BMC CONTROL-O requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data. |
| ℹ️ Check |
|---|
| Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER) The BMC CONTROL-O started task(s) and/or batch job userid(s) is defined and is assigned the RACF PROTECTED attribute. |
| ✔️ Fix |
|---|
| The BMC CONTROL-O system programmer and the IAO 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 |