V7R2 changes
z/OS CA Common Services for ACF2 STIG V7R2 (2025-10-01) replaced V7R1 (2025-01-30): 2 checks updated. It has 2 checks, against 2 in V7R1.
V7R2 checklistV7R1 checklist Compare V7R1 and V7R2 in STIG Compare
- 0 added
- 0 removed
- 2 updated
Updated fields: Check text 2Fix text 2Discussion 2Title 1
Updated in V7R2 (2)
V-224268CAT IICA Common Services installation datasets will be properly protected.Title, Check text, Fix text, Discussion
Title
CA Common Services installation data sets will be properly protected.
Check text
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- SENSITVE.RPT(CCSRPT).
Automated Analysis
Refer to the following report produced by the Datadataset Set and Resource Data Collection:
- PDI(ZCCS0000).
Verify that the accesses to the CA Common Services installation datadatasets sets are properly restricted. If the following guidance is true, this is not a finding.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restricts READ access to all authorized users.
___ The ACF2 datadataset set rules for the datadatasets setsrestrict restricts WRITE and/or greater access to systems programming personnel.
___ The ACF2 datadataset set rules for the datadatasets sets specify that all (i.e., failures and successes) WRITE and/or greater access is logged.
Fix text
The ISSO will ensure that WRITE and/or greater access to CA Common Services installation datadatasets sets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to all authorized users.
The installing systems programmer will identify and document the product datadatasets, sets and categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data setsdatasets, and once documented will work with the ISSO to seeensure that they are properly restricted to the ACP (Access Control Program) active on the system.
DataDatasets sets to be protected may begin with:
SYS2.CCS.
SYS2A.CCS.
SYS3.CCS.
The following commands are provided as a sample for implementing datadataset set controls:
$KEY(S2C)
$PREFIX(SYS2)
CCS.- UID(syspaudt) R(A) W(L) A(L) E(A)
CCS.- UID(<tstcaudt>) R(A) W(L) A(L) E(A)
CCS.- UID(authorized users/*) R(A) E(A)
SET RULE
COMPILE 'ACF2.MVA.DSNRULES(S2C)' STORE
Discussion
CA Common Services installation datadatasets sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datadatasets sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
V-224269CAT IICA Common Services Started Task name will be properly identified and/or defined to the system ACP.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the ACF2 Data Collection:
- ACF2CMDS.RPT(ATTSTC).
Verify that the logonid(s) for the CA Common Services started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.
STC
Fix text
The IAOISSO 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):
SET LID
insert CAS9 stc name('STC, CAS9')
Discussion
CA Common Services requires a started task that will be restricted to certain resources, datasets, 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.
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.