z/OS CA MIM for RACF Security Technical Implementation Guide
Overview
| Version | Date | Finding Count (6) | Downloads | ||
| 7 | 2025-02-24 | CAT I (High): 0 | CAT II (Medium): 6 | 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. |
Findings - MAC III - Administrative Public
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224438 | CA MIM Resource Sharing external security options must be specified properly. | CA MIM Resource Sharing offers external security interfaces that are controlled by parameters specified in the MIMINIT member in the MIMPARMS DD state... | |
| V-224439 | CA MIM Resource Sharing installation data sets will be properly protected. | CA MIM Resource Sharing installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly ... | |
| V-224440 | CA MIM Resource Sharing STC data sets will be properly protected. | CA MIM Resource Sharing STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict ... | |
| V-224441 | CA MIM Resource Sharing resources will be properly defined and protected. | CA MIM Resource Sharing can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access t... | |
| V-224442 | CA MIM Resource Sharing Started Task name will be properly identified and/or defined to the system ACP. | CA MIM Resource Sharing requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the sta... | |
| V-224443 | CA MIM Resource Sharing 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 ... |