IBM Health Checker Started task will be properly defined to the Started Task Table for Top Secret.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-224740 | ZHCKT032 | SV-224740r1116176_rule | CCI-000764 | medium |
| Description | ||||
| 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. | ||||
| STIG | Date | |||
| z/OS IBM Health Checker for TSS Security Technical Implementation Guide | 2025-06-24 | |||
Details
Check Text (C-224740r1116176_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 Text (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)