DoD Compliance · STIG

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

V7R1 · · 11 months ago · Released 02 Jul 2025 · 2 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 ✎ 2

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 2

V-224314 Medium checkfix IBM Health Checker STC data sets will be properly protected.
V-224315 Medium checkfix IBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).

Sort by

Expand all

IBM Health Checker STC data sets will be properly protected.

CM-5 - Medium - CCI-001499 - V-224314 - SV-224314r1116144_rule

RMF Control

CM-5

Severity

CCI

CCI-001499

Version

ZHCKA001

Vuln IDs

V-224314
V-17067

Rule IDs

SV-224314r1116144_rule
SV-43171

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-25991r1116142_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 ACF2 data set rules for the data sets restricts READ access to auditors. The ACF2 data set rules for the data sets restricts WRITE and/or greater access to systems programming personnel. The ACF2 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-25979r1116143_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 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: $KEY(S3A) $PREFIX(SYS3) MVA.HZSPDATA UID(syspaudt) R(A) W(A) A(A) E(A) MVA.HZSPDATA UID(Health Checker STCs) R(A) W(A) A(A) E(A) MVA.HZSPDATA UID(audtaudt) R(A) E(A)

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-224315 - SV-224315r1116147_rule

RMF Control

IA-2

Severity

CCI

CCI-000764

Version

ZHCKA030

Vuln IDs

V-224315
V-17452

Rule IDs

SV-224315r1116147_rule
SV-43181

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-25992r1116145_chk

Refer to the following report produced by the ACF2 Data Collection: - ACF2CMDS.RPT(ATTSTC) Verify the logonid(s) for the IBM Health Checker started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding: STC

Fix: F-25980r1116146_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): SET LID insert HZSPROC stc name('STC, IBM Health Checker')