BMC Mainview for z/OS Started Task name is not properly identified and/or defined to the system ACP.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224426 | SRG-OS-000104 | ZMVZR030 | SV-224426r1144923_rule | 2025-09-27 | 7 |
| Description |
|---|
| BMC Mainview for z/OS 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. |
| ℹ️ Check |
|---|
| Refer to the following report produced by the RACF Data Collection: - RACFCMDS.RPT(LISTUSER). Verify that the userid(s) for the BMC Mainview for z/OS started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED |
| ✔️ Fix |
|---|
| The BMC Mainview for z/OS system programmer and the ISSO will ensure that a product's Started Task(s) is properly identified and/or 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 MV$CAS name('CAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass au MV$PAS name('PAS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass au MV$MVS name('MVS, BMC Mainview for z/OS') owner(stc) dfltgrp(stc) nopass |