V7R1 changes
z/OS IBM Health Checker for RACF STIG V7R1 (2025-07-02) replaced V6R3 (2022-11-23): 1 check updated. It has 3 checks, against 3 in V6R3.
V7R1 checklistV6R3 checklist Compare V6R3 and V7R1 in STIG Compare
- 0 added
- 0 removed
- 1 updated
Updated fields: Check text 1Fix text 1
Updated in V7R1 (1)
V-224501CAT IIIBM Health Checker STC data sets will be properly protected.Check text, Fix text
Check text
Refer to the following report produced by the Data Set and Resource Data Collection:
- SENSITVE.RPT(HCKSTC)
Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:
- PDI(ZHCK0001)
Verify that the accesses to the IBM Health Checker STC 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.
___ The RACF data set rules for the data sets restricts UPDATE access to domain level security administrators.
___ 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 restricts WRITE and/or greater access to the IBM Health Checker's STC(s) and/or batch user(s).
___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
Fix text
The ISSO will ensure that WRITE and/or greater access to IBM Health Checker STC data sets is limited to systems programmers and/or Quest NC-Pass's STC(s) and/or batch user(s) only. READ access can be given to auditors.
The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required 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 sets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program (ACP) active on the system. The dataset to be protected can be found in the HZSPROC STC member in HZSPDATA DD statement.
Data sets to be protected will be:
SYS3.*.HZSPDATA
The following commands are provided as a sample for implementing data set controls:
AD 'sys3.mmd.hzspdata.**' UACC(NONE) OWNER(SYS3) AUDIT(FAILURES(READ))
PE ' sys3.mmd.hzspdata.**' ID(syspaudt) ACC(A)
PE ' sys3.mmd.hzspdata.**' ID(Health Checker STCs) ACC(A)
PE ' sys3.mmd.hzspdata.**' ID(audtaudt) ACC(R)
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 V7R1 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.