Rule ID
SV-224116r1141456_rule
Version
V7R2
CCIs
BMC CONTROL-M User datasets, Repository, have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets 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 dataset and Resource Data Collection: - SENSITVE.RPT(CTMUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTM0002). Verify that the accesses to the BMC CONTROL-M User datasets are properly restricted. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors. The ACF2 dataset access authorizations restrict WRITE and/or greater access to systems programming personnel. The ACF2 dataset access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. The ACF2 access authorizations restrict UPDATE access to the BMC Users, operations, and production control and scheduling personnel (both domain level and application level).
The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M User datasets is limited to systems programmers and/or BMC STCs and/or batch users only. UPDATE access can be given to the BMC Users, operations, and production control and scheduling personnel (both domain level and application level). READ access can be given to auditors. The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure they are properly restricted to the ACP (Access Control Program) active on the system. (Note: The datasets and/or dataset prefixes identified below are examples of a possible installation. The actual datasets and/or prefixes are determined when the product is installed on a system through the product's installation guide and can be site specific.) Datasets to be protected will be: SYS3.IOA.*.CTMC The following commands are provided as a sample for implementing dataset controls: $KEY(SYS3) IOA.-.CTMC.- UID(<syspaudt>) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTMC.- UID(<bmcuser>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<operaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<pcspaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<dpcsaudt>) R(A) W(A) E(A) IOA.-.CTMC.- UID(<audtaudt>) R(A) E(A)