← Back to z/OS IBM Health Checker for RACF Security Technical Implementation Guide

V-224503

CAT II (Medium)

IBM Health Checker Started task will be properly defined to the STARTED resource class for RACF.

Rule ID

SV-224503r868419_rule

STIG

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

Version

V6R3

CCIs

SV-43187

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.

Check Content

Refer to the following report produced by the RACF Data Collection:

- DSMON.RPT(RACSPT)

Automated Analysis
Refer to the following report produced by the RACF Data Collection:

- PDI(ZHCK0032)

If the IBM Health Checker started task(s) is (are) defined to the STARTED resource class profile and/or ICHRIN03 table entry, this is not a finding.

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. 

A unique userid must be assigned for the IBM Health Checker started task(s) thru a corresponding STARTED class entry.

The following commands are provided as a sample for defining Started Task(s):

rdef started HZSPROC.** uacc(none) owner(admin) audit(all(read)) -
	stdata(user(HXSPROC) group(stc))
setr racl(started) ref