BMC CONTROL-M/Restart Archived Sysout datasets must be properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224122	SRG-OS-000080	ZCTRA002	SV-224122r1141494_rule	2025-09-23	7

Description
BMC CONTROL-M/Restart Archived Sysout datasets 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.

ℹ️ Check
Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTRUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTR0002). Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout 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 and BMC Users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to production control and scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users.

ℹ️ Check

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTRUSER). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTR0002). Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout 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 and BMC Users. The ACF2 dataset access authorizations restrict WRITE and/or greater access to production control and scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users.

✔️ Fix
Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout datasets is limited to production control scheduling personnel, scheduled batch users, systems programmers, and the BMC STCs and/or batch users only. READ access can be given to auditors and BMC users. 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 Access Control Program (ACP) 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: CTRSYS The following commands are provided as a sample for implementing dataset controls: $KEY(CTRSYS) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(CONTROLM) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) A(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<autoaudt>) R(A) W(A) A(A) E(A) - UID(<pcspaudt>) R(A) W(A) A(A) E(A)

✔️ Fix

Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout datasets is limited to production control scheduling personnel, scheduled batch users, systems programmers, and the BMC STCs and/or batch users only. READ access can be given to auditors and BMC users. 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 Access Control Program (ACP) 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: CTRSYS The following commands are provided as a sample for implementing dataset controls: $KEY(CTRSYS) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(CONTROLM) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) A(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<autoaudt>) R(A) W(A) A(A) E(A) - UID(<pcspaudt>) R(A) W(A) A(A) E(A)