IBM Health Checker Started task will be properly defined to the STARTED resource class for RACF.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-224503 | SRG-OS-000104 | ZHCKR032 | SV-224503r868419_rule | 2022-10-10 | 6 |
| 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. |
| ℹ️ Check |
|---|
| 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 |
|---|
| 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 |