BMC CONTROL-D Started task(s) must be properly defined to the STARTED resource class for RACF.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224395 | ZCTDR032 | SV-224395r1144768_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 CONTROL-D for RACF Security Technical Implementation Guide | 2025-09-27 | |||
Details
Check Text (C-224395r1144768_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(ZCTD0032).
Verify that the BMC CONTROL-D started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is a finding.
Fix Text (F-26060r1144767_fix)
The BMC CONTROL-D 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 CONTROL-D started task(s) thru a corresponding STARTED class entry.
The following sample set of commands is shown here as a guideline:
rdef started CONTROLD.** uacc(none) owner(admin) audit(all(read)) stdata(user(CONTROLD) group(stc))
setr racl(started) ref