V7R1 changes
z/OS IBM Health Checker for TSS STIG V7R1 (2025-07-02) replaced V6R3 (2022-11-23): 3 checks updated. It has 3 checks, against 3 in V6R3.
V7R1 checklistV6R3 checklist Compare V6R3 and V7R1 in STIG Compare
- 0 added
- 0 removed
- 3 updated
Updated fields: Check text 3Fix text 2Title 1Discussion 1
Updated in V7R1 (3)
V-224738CAT IIIBM Health Checker STC 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(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 TSS data set rules for the data sets restricts READ access to auditors.
___ The TSS data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel.
___ The TSS 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).
V-224739CAT IIIBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).Title, Check text, Fix text
Title
IBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(@ACIDS)
Verify that the ACID(s) for the IBM Health Checker started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.
FACILITY(STC, BATCH)
PASSWORD(xxxxxxxx,0)
SOURCE(INTRDR)
NOSUSPEND
Fix text
The IAOISSO working with the systems programmer will ensure the IBM Health Checker 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 the 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):
TSS CREATE(HZSPROD) TYPE(USER) -
NAME('STC, IBM Health Checker') DEPT(xxxx) -
FAC(STC,BATCH) PASS(xxxxxxxx,0) -
SOURCE(INTRDR) NOSUSPEND
V-224740CAT IIIBM Health Checker Started task will be properly defined to the Started Task Table for Top Secret.Check text, Fix text, Discussion
Check text
Refer to the following report produced by the TSS Data Collection:
- TSSCMDS.RPT(#STC)
Automated Analysis
Refer to the following report produced by the TSS Data Collection:
- PDI(ZHCK0032)
If the IBM Health Checker started task(s) is (are) defined in the TSS STC record, this is not a finding.
Fix text
The IAOISSO working with the systems programmer will ensure the IBM Health Checker Started Task(s) is properly identified and/or defined to the System ACP.
A unique ACID must be assigned for the IBM Health Checker started task(s) thru a corresponding STC table entry.
The following commands are provided as a sample for defining Started Task(s):
TSS ADD(STC) PROCNAME(HZSPROC) ACID(HZSPROC)
Discussion
Access to product resources should 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 V7R1 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.