Cyber · Trackr The Free Compliance Library
⌘K
DoD Compliance · STIG

z/OS IBM Health Checker for TSS Security Technical Implementation Guide

V7R1 · · · Released 02 Jul 2025 · 3 rules
Compare

Pick two releases to diff their requirements.

View

Open a previous version of this STIG.

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.
Digest of Updates vs. V6R3 · 23 Nov 2022 ✎ 3

Comparison against the immediately-prior release (V6R3). Rule matching uses the Group Vuln ID. Content-change detection compares the rule’s description, check, and fix text after stripping inline markup — cosmetic-only edits aren’t flagged.

Content changes 3

  • V-224738 Medium check IBM Health Checker STC data sets will be properly protected.
  • V-224739 Medium fix IBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).
  • V-224740 Medium fix IBM Health Checker Started task will be properly defined to the Started Task Table for Top Secret.
Sort by
b
IBM Health Checker STC data sets will be properly protected.
CM-5 - Medium - CCI-001499 - V-224738 - SV-224738r1116170_rule
RMF Control
CM-5
Severity
M
CCI
CCI-001499
Version
ZHCKT001
Vuln IDs
  • V-224738
  • V-17067
Rule IDs
  • SV-224738r1116170_rule
  • SV-43173
IBM Health Checker STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.
Checks: C-26429r1105861_chk

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).

Fix: F-26417r868698_fix

The ISSO will ensure that WRITE and/or greater access to IBM Health Checker STC data sets is limited to systems programmers and/or IBM Health Checker'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) 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: TSS ADD(SYS3) DSN(SYS3) TSS PERMIT(syspaudt) DSN(SYS3.MMG.HZSPDATA) ACCESS(ALL) TSS PERMIT(Health Checker STCs) DSN(SYS3.MMG.HZSPDATA) ACCESS(ALL) TSS PERMIT(audtaudt) DSN(SYS3.MMG.HZSPDATA) ACCESS(READ)

b
IBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).
IA-2 - Medium - CCI-000764 - V-224739 - SV-224739r1116173_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZHCKT030
Vuln IDs
  • V-224739
  • V-17452
Rule IDs
  • SV-224739r1116173_rule
  • SV-43183
IBM Health Checker requires a started task that will be restricted to certain resources, datasets and other system functions. By 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.
Checks: C-26430r1116171_chk

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: F-26418r1116172_fix

The ISSO 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

b
IBM Health Checker Started task will be properly defined to the Started Task Table for Top Secret.
IA-2 - Medium - CCI-000764 - V-224740 - SV-224740r1116176_rule
RMF Control
IA-2
Severity
M
CCI
CCI-000764
Version
ZHCKT032
Vuln IDs
  • V-224740
  • V-17454
Rule IDs
  • SV-224740r1116176_rule
  • SV-43188
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.
Checks: C-26431r1116174_chk

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: F-26419r1116175_fix

The ISSO 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)