z/OS BMC CONTROL-M for ACF2 STIG Version Comparison

There are 10 differences between versions v6 r10 (Nov. 23, 2022) (the "left" version) and v7 r2 (Oct. 1, 2025) (the "right" version).

Check ZCTMA000 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

BMC CONTROL-M installation datasets data sets will be properly protected.

Check Content

Refer to the following report produced by the dataset Data Set and Resource Data Collection: - SENSITVE.RPT(CTMRPT) Automated SENSITVE.RPT(CTMRPT). Automated Analysis Refer to the following report produced by the dataset Data Set and Resource Data Collection: - PDI(ZCTM0000) Verify PDI(ZCTM0000). Verify that the accesses to the BMC CONTROL-M installation datasets data sets are properly restricted. If the following guidance is true, this is not a finding. ___ finding. The The ACF2 dataset data set access authorizations restrict READ access to auditors, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), and BMC STCs and/or batch users. The users. ___ The ACF2 dataset data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ personnel. The The ACF2 dataset data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are is logged.

Discussion

BMC CONTROL-M installation datasets data sets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets data sets could result in violating the integrity of the base product which could result in compromising the operating system or sensitive data.

Fix

The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M installation datasets is data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, automated operations, BMC users, operations, production control and scheduling personnel (domain level and decentralized), and BMC STCs and/or batch users. All failures and successful WRITE and/or greater accesses are logged. The installing systems programmer will identify and document the product datasets, data sets and categorize them according to who will have update and alter WRITE and/or greater access access, and if required required, ensure that all update and allocate WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have update WRITE and/or alter greater access for specific datasets, data sets, 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 data sets and/or dataset data set prefixes identified below are examples of a possible installation. The actual datasets 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 specific.) Datasets sets to be protected will be: SYS2.IOA.*.CTMI. The be: SYS2.IOA.*.CTMI The following commands are provided as a sample for implementing dataset data set controls: $KEY(SYS2) IOA.-.CTMI.- UID(<syspaudt>) R(A) W(L) A(L) E(A) IOA.-.CTMI.- UID(<audtaudt>) R(A) E(A) IOA.-.CTMI.- UID(<autoaudt>) R(A) E(A) IOA.-.CTMI.- UID(<bmcuser>) R(A) E(A) IOA.-.CTMI.- UID(<dpcsaudt>) R(A) E(A) IOA.-.CTMI.- UID(<operaudt>) R(A) E(A) IOA.-.CTMI.- UID(<pcspaudt>) R(A) E(A) IOA.-.CTMI.- UID(CONTROLM) R(A) E(A)