Title

CA 1 Tape Management Started task will be properly defined to the STARTED resource class for RACF. (Cat II impact)

Discussion

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.

Check Content

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

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

Additional Identifiers

Rule ID: SV-224456r958482_rule

Vulnerability ID: V-224456

Group Title: SRG-OS-000104

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.