From z/OS BMC CONTROL-M for ACF2 STIG
Part of ZB000003
Associated with IA controls: ECCD-2, ECAR-3, ECAR-2, ECCD-1, ECAR-1, DCSL-1
BMC CONTROL-M User/Application JCL 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 the integrity of the base product which could result in compromising the operating system or sensitive data.
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMJCL) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTM0003) Verify that the accesses to the BMC CONTROL-M User/Application JCL data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 data set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. ___ The ACF2 data set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. ___ The ACF2 data set access authorizations restrict UPDATE access to the Production Control and Scheduling personnel (both domain level and Application level) and BMC STCs and/or batch users. Access will be based on a documented need to know requirement. Application (external users) will not have access to internal/site data sets.
The IAO will ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL data sets are limited to System Programmers and/or BMC administrators only. UPDATE access can be given to the production control and scheduling personnel (both domain level and Application level) and BMC STCs and/or batch users. READ access can be given to auditors, automated batch user(s), BMC users, and operations. Access will be based on a documented need to know requirement. Application (external users) will not have access to internal/site data sets.
The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system.
(Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual data sets and/or prefixes are determined when the product is actually installed on a system through the product’s installation guide and can be site specific.)
Data sets to be protected will be:
The following commands are provided as a sample for implementing data set controls:
Lavender hyperlinks in small type off to the right (of CSS
id, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header
Powered by sagemincer