BMC CONTROL-M User/Application JCL datasets must be properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224117	SRG-OS-000018	ZCTMA003	SV-224117r1141459_rule	2025-09-26	7

Description
BMC CONTROL-M User/Application JCL 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(CTMJCL). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL datasets are limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. The ACF2 dataset access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. The ACF2 dataset 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. Accesses must be reviewed and approved by the ISSO based on a documented need to perform job duties. Application (external users) will not have access to internal/site datasets. Note: Update access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. Update access of the site's (LPAR Level) IA (Security) administrative batch processing JCL and Procedures must be limited to only the LPAR LEVEL ISSO/ISSM Team. It is recommended that multiple datasets be created, one of which contains JCL and Procedures that are considered restricted, and this dataset be authorized to users with justification to maintain and run these restricted JCL and Procedures.

ℹ️ Check

Refer to the following report produced by the dataset and Resource Data Collection: - SENSITVE.RPT(CTMJCL). Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection: - PDI(ZCTM0003). Verify that the accesses to the BMC CONTROL-M User/Application JCL datasets are limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. The ACF2 dataset access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. The ACF2 dataset access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. The ACF2 dataset 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. Accesses must be reviewed and approved by the ISSO based on a documented need to perform job duties. Application (external users) will not have access to internal/site datasets. Note: Update access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. Update access of the site's (LPAR Level) IA (Security) administrative batch processing JCL and Procedures must be limited to only the LPAR LEVEL ISSO/ISSM Team. It is recommended that multiple datasets be created, one of which contains JCL and Procedures that are considered restricted, and this dataset be authorized to users with justification to maintain and run these restricted JCL and Procedures.

✔️ Fix
Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL datasets is limited to systems 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 datasets. 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: IOA The following commands are provided as a sample for implementing dataset controls: $KEY(IOA) - UID(<bmcadmin>) R(A) W(A) A(A) E(A) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(<tstcaudt>) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) E(A) - UID(CONTROLM) R(A) W(A) E(A) - UID(<dpcsaudt>) R(A) W(A) E(A) - UID(<pcspaudt>) R(A) W(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<autoaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<operaudt>) R(A) E(A)

✔️ Fix

Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL datasets is limited to systems 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 datasets. 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: IOA The following commands are provided as a sample for implementing dataset controls: $KEY(IOA) - UID(<bmcadmin>) R(A) W(A) A(A) E(A) - UID(<syspaudt>) R(A) W(A) A(A) E(A) - UID(<tstcaudt>) R(A) W(A) A(A) E(A) - UID(CONTDAY) R(A) W(A) E(A) - UID(CONTROLM) R(A) W(A) E(A) - UID(<dpcsaudt>) R(A) W(A) E(A) - UID(<pcspaudt>) R(A) W(A) E(A) - UID(<audtaudt>) R(A) E(A) - UID(<autoaudt>) R(A) E(A) - UID(<bmcuser>) R(A) E(A) - UID(<operaudt>) R(A) E(A)