Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
z/OS IBM Health Checker for RACF Security Technical Implementation Guide
Overview
| Version | Date | Finding Count (3) | ||
|---|---|---|---|---|
| 6 | 2022-10-10 | CAT I (High): 0 | CAT II (Med): 3 | CAT III (Low): 0 |
| STIG Description |
|---|
| 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. |
Available Profiles
Findings (MAC III - Administrative Sensitive)
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224502 | Medium | IBM Health Checker Started Task name will be properly identified and/or defined to the system ACP. | 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... |
| V-224503 | Medium | IBM Health Checker Started task will be properly defined to the STARTED resource class for RACF. | 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... |
| V-224501 | Medium | IBM Health Checker STC data sets will be properly protected. | 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... |