STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to z/OS IBM Health Checker for ACF2 Security Technical Implementation Guide

V-224315

CAT II (Medium)

IBM Health Checker Started Task name will be properly identified and/or defined to the system Access Control Program (ACP).

Rule ID

SV-224315r1116147_rule

STIG

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

Version

V7R1

CCIs

CCI-000764

Discussion

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.

Check Content

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 Text

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