BMC Mainview for z/OS Started Task name must be properly identified and/or defined to the system ACP.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224253 | ZMVZA030 | SV-224253r958482_rule | CCI-000764 | medium |
| Description | ||||
| BMC Mainview for z/OS 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. | ||||
| STIG | Date | |||
| z/OS BMC MAINVIEW for z/OS for ACF2 Security Technical Implementation Guide | 2025-02-24 | |||
Details
Check Text (C-224253r958482_chk)
Refer to the following report produced by the ACF2 Data Collection:
- ACF2CMDS.RPT(ATTSTC)
Insure that the logonids(s) for the BMC Mainview for z/OS started task(s) includes the following:
STC
NO-SMC
Fix Text (F-25914r518969_fix)
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.
Example:
SET LID
INSERT MV$CAS STC NO-SMC
INSERT MV$PAS STC NO-SMC
INSERT MV$MVS STC NO-SMC