z/OS BMC CONTROL-M for ACF2 Security Technical Implementation Guide
Overview
| Version | Date | Finding Count (8) | Downloads | ||
| V7R2 | 2025-09-26 | 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 I - Mission Critical Sensitive
| Finding ID | Severity | Title | Description |
|---|---|---|---|
| V-224113 | BMC CONTROL-M security exits are not installed or configured properly. | The BMC CONTROL-M security exits enable access authorization checking to BMC CONTROL-M commands, features, and online functionality. If these exit(s) ... | |
| V-224114 | BMC CONTROL-M installation datasets will be properly protected. | BMC CONTROL-M installation datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict ac... | |
| V-224115 | BMC CONTROL-M STC datasets will be properly protected. | BMC CONTROL-M STC datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to t... | |
| V-224116 | BMC CONTROL-M User datasets will be properly protected. | BMC CONTROL-M User datasets, Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restri... | |
| V-224117 | BMC CONTROL-M User/Application JCL datasets must be properly protected. | BMC CONTROL-M User/Application JCL datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly res... | |
| V-224118 | BMC C0NTROL-M resources must be properly defined and protected. | BMC CONTROL-M can run with sensitive system privileges, and potentially can circumvent system controls. Failure to properly control access to product ... | |
| V-224119 | BMC CONTROL-M Started Task name is not properly identified/defined to the system ACP. | BMC CONTROL-M requires a started task that will be restricted to certain resources, datasets, and other system functions. Defining the started task as... | |
| V-224120 | BMC CONTROL-M configuration/parameter values must be specified properly. | BMC CONTROL-M configuration/parameters control the security and operational characteristics of products. If these parameter values are improperly spec... |