V7R2 changes
z/OS HCD for RACF STIG V7R2 (2025-10-01) replaced V7R1 (2025-04-02): 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 3Fix text 3
Updated in V7R2 (3)
V-224489CAT IIIBM Hardware Configuration Definition (HCD) install data sets are not properly protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(HCDRPT).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZHCD0000).
Verify that access to the IBM HCD install 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 auditors, automated operations, operators, and systems programming personnel.
The RACF data set rules for the data sets restricts UPDATEWRITE and/or ALTERgreater access to systems programming personnel.
The RACF data set rules for the data sets specifies that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access are logged.
The RACF data set access authorizations specify UACC(NONE) and NOWARNING.
Fix text
The ISSO will ensure that updateWRITE and/or allocategreater access to IBM HCD install data sets is limited to system programmers only, and all updateWRITE and/or altergreater access is logged. Auditors, automated operations, and operators should have READ access.
The installing systems programmer will identify and document the product data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The systems programmer will identify if any additional groups have updateWRITE and/or altergreater access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system.
Data sets to be protected will be:
SYS1.SCBD*
The following commands are provided as a sample for implementing datasetdata set controls:
ad 'SYS1.SCBD*.**' uacc(none) owner(sys1) -
audit(success(update) failures(read)) -
data('Vendor DS Profile: hcd')
pe 'SYS1.SCBD*.**' id(syspaudt tstcaudt) acc(a)
pe 'SYS1.SCBD*.**' id(audtaudt autoaudt operaudt) acc(r)
setr generic(dataset) refresh
V-224490CAT IIIBM Hardware Configuration Definition (HCD) User data sets are not properly protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(HCDUSER).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZHCD0002).
Verify that the access to the IBM HCD install data sets is properly restricted. The data sets to be protected are the production and working IODF data sets as well as the activity log for the IODF data sets. If the following guidance is true, this is not a finding.
Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**.
The RACF data set rules for the data sets does not restrict UPDATEWRITE and/or ALTERgreater access to systems programming personnel.
The RACF data set rules for the data sets does not restrict READ access to automated operations users and operations personnel.
The RACF data set rules for the datasetsdata doessets not specify that all (i.e., failures and successes) UPDATEWRITE and/or ALTERgreater access will be logged.
IfThe allRACF ofdata theset aboveaccess areauthorizations untrue,specify thereUACC(NONE) isand no findingNOWARNING.
If any of the above is true, this is a finding.
Fix text
The ISSO will ensure that update,WRITE and/or altergreater access to program product user data sets is limited to systems programmers and all updateWRITE and/or allocategreater access is logged. Ensure that readREAD access is limited to auditors, Operations personnel, and Automated Operations users.
The installing systems programmer will identify and document the product user data sets and categorize them according to who will have updateWRITE and/or altergreater access and if required that all updateWRITE and/or allocategreater access is logged. The installing systems programmer will identify if any additional groups have updateUPDATE access for specific data sets, and once documented, will work with the ISSO to ensure they are properly restricted to the Access Control Program (ACP) active on the system.
Data sets to be protected will be:
The production IODF data sets. (i.e., hhhhhhhh.IODFnn)
The working IODF data sets. (i.e., hhhhhhhh.IODFnn.)
The activity log for the IODF data sets. (i.e., hhhhhhhh.IODFnn.ACTLOG)
Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**.
The following commands are provided as a sample for implementing datasetdata set controls:
ad 'sys3.iodf*.**' uacc(none) owner(sys3) -
audit(success(update) failures(read)) -
data('Vendor DS Profile: IODF for HCD')
pe 'sys3.iodf*.**' id(syspaudt tstcaudt) acc(a)
pe 'sys3.iodf*.**' id(audtaudt autoaudt operaudt) acc(r)
V-224491CAT IIIBM Hardware Configuration Definition (HCD) resources are not properly defined and protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(FACILITY).
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZHCD0020).
Review the following items for the IBM HCD resources in the FACILITY resource class:
1. If the following guidance is true, this is not a finding.
The RACF rules for the CBD resource specify a default access of NONE.
2. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources restrict access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.
3. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.
4. All RACF rules are defined with UACC(NONE).
If any item above is untrue, this is a finding.
If all items above are true, this is not a finding.
Fix text
The systems programmer will work with the ISSO to verify that the following are properly specified in the Access Control Program (ACP).
1. The RACF rules for the CBD resource specify a default access of NONE.
2. There are no RACF rules that allow access to the CBD resource.
Example:
rdef facility cbd.** uacc(none) owner(admin) audit(failure(read)) -
data('added per PDI ZHCD0020')
3. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming and operations personnel as well as possibly any automated operations batch users with access of READ.
4. The RACF rules for the CBD.CPC.IOCDS and CBD.CPC.IPLPARM resources are restricted access to systems programming with access of UPDATE and logged.
5. All RACF rules are defined with UACC(NONE).
Example:
rdef facility cbd.cpc.iocds.** uacc(none) owner(admin) -
audit(success(update) failures(read)) -
data('added per PDI ZHCD0020')
rdef facility cbd.cpc.iplparm.** uacc(none) owner(admin) -
audit(success(update) failures(read)) -
data('added per PDI ZHCD0020')
pe cbd.cpc.iocds.** cl(facility) id(syspaudt) acc(u)
pe cbd.cpc.iocds.** cl(facility) id(operaudt) acc(r)
pe cbd.cpc.iocds.** cl(facility) id(autoaudt) acc(r)
pe cbd.cpc.iplparm.** cl(facility) id(syspaudt) acc(u)
pe cbd.cpc.iplparm.** cl(facility) id(operaudt) acc(r)
pe cbd.cpc.iplparm.** cl(facility) id(autoaudt) acc(r)
setr racl(facility) ref
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.