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

From z/OS CA Common Services for RACF STIG

Associated with IA controls: ECCD-2, ECCD-1

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

Vulnerability 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(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 IAO 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

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.