z/OS CA Common Services for RACF STIG Version Comparison
z/OS CA Common Services for RACF Security Technical Implementation Guide
There are 2 differences between versions v6 r2 (Jan. 20, 2015) (the "left" version) and v6 r3 (Nov. 23, 2022) (the "right" version).
Check ZCCSR030 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.
CA Common Services Started Task name will be properly identified and/or defined to the system ACP.
Refer to the following report produced by the RACF Data Collection: - Collection: - RACFCMDS.RPT(LISTUSER) Verify RACFCMDS.RPT(LISTUSER) Verify that the userid(s) for the CA Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding. PROTECTED
CA Common Services requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
The IAO 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. If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes. Most installation manuals will indicate how a Started Task is identified and any additional attributes that must be specified. The following commands are provided as a sample for defining Started Task(s): au CAS9 name('STC, CAS9') owner(stc) dfltgrp(stc) nopass – data('CCS - data('CCS stc')