z/OS BMC CONTROL-O for RACF Security Technical Implementation Guide
Overview
| Version | Date | Finding Count (8) | Downloads | ||
| 7 | 2025-02-24 | CAT I (High): 0 | CAT II (Medium): 8 | 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 II - Mission Support Classified
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224407 | BMC CONTROL-O configuration/parameter values are not specified properly. | BMC CONTROL-O configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly spec... | |
| V-224408 | BMC CONTROL-O configuration/parameter values are not specified properly. | BMC CONTROL-O configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly spec... | |
| V-224409 | BMC CONTROL-O security exits are not installed or configured properly. | The BMC CONTROL-O security exits enable access authorization checking to BMC CONTROL-O commands, features, and online functionality. If these exit(s) ... | |
| V-224410 | BMC CONTROL-O installation data sets will be properly protected. | BMC CONTROL-O installation data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict a... | |
| V-224411 | BMC CONTROL-O STC data sets must be properly protected. | BMC CONTROL-O STC data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to... | |
| V-224412 | BMC CONTROL-O resources must be properly defined and protected. | BMC CONTROL-O can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product ... | |
| V-224413 | BMC CONTROL-O Started Task name is not properly identified / defined to the system ACP. | BMC CONTROL-O requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task ... | |
| V-224414 | BMC CONTROL-O Started task(s) must 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 ... |