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

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224400	SRG-OS-000018	ZCTMR003	SV-224400r1145225_rule	2025-09-27	7

Description
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.

ℹ️ Check
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 limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. The RACF data set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. The RACF data set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. The RACF 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. 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 data sets. Note: WRITE and/or greater access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. WRITE and/or greater 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 data sets be created, one of which contains JCL and Procedures that are considered restricted, and this data set be authorized to users with justification to maintain and run these restricted JCL and Procedures. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

ℹ️ Check

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 limited to only those who require access to perform their job duties. If the following guidance is true, this is not a finding. The RACF data set access authorizations restrict READ access to auditors, automated batch user(s), BMC user(s), and operations. The RACF data set access authorizations restrict WRITE and/or greater access to BMC CONTROL-M administrators and systems programming personnel. The RACF 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. 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 data sets. Note: WRITE and/or greater access of the site's DASD Administrator Batch Processing JCL and Procedures must be limited to only the LPAR level DASD Administrators. WRITE and/or greater 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 data sets be created, one of which contains JCL and Procedures that are considered restricted, and this data set be authorized to users with justification to maintain and run these restricted JCL and Procedures. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.

✔️ Fix
Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL data sets are limited to BMC CONTROL-M administrators only. Update access can be given to the Production Control and Scheduling personnel and/or BMC CONTROL-M's STC(s) and/or BMC CONTROL-M's batch user(s). READ access can be given to auditors and automated batch user(s). The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required 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 data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: IOA. The following commands are provided as a sample for implementing data set controls: ad 'IOA.' uacc(none) owner(IOA) - data('ControlM User Datasets') pe 'IOA.' id(<syspaudt>) acc(a) pe 'IOA.' id(<audtaudt> <autoaudt>) acc(r) pe 'IOA.' id(<bmcuser> <bmcbatch> <operaudt> <pcspaudt>) acc(r) pe 'IOA.' id(CONTROLM CONTDAY) acc(r) setr generic(dataset) refresh

✔️ Fix

Ensure that WRITE and/or greater access to BMC CONTROL-M User/Application JCL data sets are limited to BMC CONTROL-M administrators only. Update access can be given to the Production Control and Scheduling personnel and/or BMC CONTROL-M's STC(s) and/or BMC CONTROL-M's batch user(s). READ access can be given to auditors and automated batch user(s). The installing systems programmer will identify and document the product data sets and categorize them according to who will have WRITE and/or greater access and if required 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 data sets, and once documented will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: IOA.** The following commands are provided as a sample for implementing data set controls: ad 'IOA.**' uacc(none) owner(IOA) - data('ControlM User Datasets') pe 'IOA.**' id(<syspaudt>) acc(a) pe 'IOA.**' id(<audtaudt> <autoaudt>) acc(r) pe 'IOA.**' id(<bmcuser> <bmcbatch> <operaudt> <pcspaudt>) acc(r) pe 'IOA.**' id(CONTROLM CONTDAY) acc(r) setr generic(dataset) refresh