V7R2 changes
z/OS CA Common Services for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 3 checks updated. It has 3 checks, against 3 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 3 updated
Updated fields: Check text 3Discussion 2
Updated in V7R2 (3)
V-224433CAT IICA Common Services installation data sets will be properly protected.Check text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(CCSRPT).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZCCS0000).
Verify that the accesses to the CA Common Services installation data sets are properly restricted. If the following guidance is true, this is not a finding.
___ The RACF data set rules for the data sets restricts READ access to all authorized users.
___ The RACF data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.
___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
V-224434CAT IICA Common Services Started Task name will be properly identified and/or defined to the system ACP.Check text, Discussion
Check text
Refer to the following report produced by the RACF Data Collection: - 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
Discussion
CA Common Services requires a started task that will be restricted to certain resources, datasetsdata sets, and other system functions. ByDefining 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.
V-224435CAT IICA Common Services Started task will be properly defined to the STARTED resource class for RACF.Check text, Discussion
Check text
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.
Discussion
Access to product resources shouldmust 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.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V7R2 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.