← Back to z/OS CA Common Services for RACF Security Technical Implementation Guide

V-224435

CAT II (Medium)

CA Common Services Started task will be properly defined to the STARTED resource class for RACF.

Rule ID

SV-224435r1144695_rule

STIG

z/OS CA Common Services for RACF Security Technical Implementation Guide

Version

V7R2

CCIs

CCI-000764

Discussion

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.

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(ZCCS0032).

If the CA Common Services 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 Common Services Started Task(s) is properly identified and/or defined to the System ACP. 

A unique userid must be assigned for the CA Common Services started task(s) thru a corresponding STARTED class entry.

The following commands are provided as a sample for defining Started Task(s):

rdef started CAS9.** uacc(none) owner(admin) audit(all(read)) -
	stdata(user(CAS9) group(stc))
setr racl(started) ref