CA 1 Tape Management Started task will be properly defined to the STARTED resource class for RACF.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224456 | ZCA1R032 | SV-224456r958482_rule | CCI-000764 | medium |
| Description | ||||
| Access to product resources should be restricted to only those individuals responsible for the application connectivity and who have a requirement to access these resources. Improper control of product resources could potentially compromise the operating system, ACP, and customer data. | ||||
| STIG | Date | |||
| z/OS CA 1 Tape Management for RACF Security Technical Implementation Guide | 2024-12-16 | |||
Details
Check Text (C-224456r958482_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(ZCA10032)
If the CA 1 Tape Management 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-26121r868315_fix)
The ISSO working with the systems programmer will ensure the CA 1 Tape Management Started Task(s) is properly identified and/or defined to the System ACP.
A unique userid must be assigned for the CA 1 Tape Management started task(s) thru a corresponding STARTED class entry.
The following commands are provided as a sample for defining Started Task(s):
rdef started TMSINIT.** uacc(none) owner(admin) audit(all(read)) -
stdata(user(TMSINIT) group(stc))
rdef started CTS.** uacc(none) owner(admin) audit(all(read)) -
stdata(user(CTS) group(stc))
setr racl(started) ref