BMC Mainview for z/OS Started task(s) must be properly defined to the STARTED resource class for RACF.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224427 | ZMVZR032 | SV-224427r1144926_rule | CCI-000764 | medium |
| Description | ||||
| Access to product resources must be restricted to only individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could compromise the operating system, ACP, and customer data. | ||||
| STIG | Date | |||
| z/OS BMC MAINVIEW for z/OS for RACF Security Technical Implementation Guide | 2025-09-27 | |||
Details
Check Text (C-224427r1144926_chk)
Refer to the following report produced by the RACF Data Collection:
- DSMON.RPT(RACSPT).
Automated Analysis
Refer to the following report produced by the RACF Data Collection:
- PDI(ZMVZ0032).
Verify that the BMC Mainview for z/OS started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.
Fix Text (F-26092r1144925_fix)
The BMC Mainview system programmer and the ISSO will ensure that a product's started task(s) is (are) properly identified and/or defined to the System ACP.
A unique userid must be assigned for the BMC Mainview started task(s) thru a corresponding STARTED class entry.
The following sample set of commands is shown here as a guideline:
rdef started MV$CAS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$CAS) group(stc))
rdef started MV$MVS.** uacc(none) owner(admin) audit(all(read)) stdata(user(MV$MVS) group(stc))
setr racl(started) ref