BMC CONTROL-M STC 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.
Refer to the following report produced by the Data Set and Resource Data Collection:
Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection:
Verify that the accesses to the BMC CONTROL-M STC data sets are properly restricted. If the following guidance is true, this is not a finding.
___ The RACF data set access authorizations restricts READ access to auditors and BMC users.
___ The RACF data set access authorizations restricts WRITE and/or greater access to systems programming personnel.
___ The RACF data set access authorizations restricts UPDATE access to the BMC STCs and/or batch users.
___ The RACF data set access authorizations restricts UPDATE access to scheduled batch jobs, operations, and production control and scheduling personnel.
___ The RACF data set rules for the data sets specify UACC(NONE) and NOWARNING.
Fix Text (F-3254r6_fix)
The IAO will ensure that WRITE and/or greater access to BMC CONTROL-M STC data sets are limited to System Programmers only. UPDATE access can be given to scheduled batch jobs, operations, and production control and scheduling personnel, BMC STCs and/or batch users. READ access can be given to auditors and/or BMC users.
The installing Systems Programmer will identify and document the product data sets and categorize them according to who will have update and alter access and if required that all update and allocate access is logged. He will identify if any additional groups have update and/or alter access for specific data sets, and once documented he will work with the IAO to see that they are properly restricted to the ACP (Access Control Program) active on the system.
(Note: The data sets and/or data set prefixes identified below are examples of a possible installation. The actual 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 sets to be protected will be: SYS3.IOA.*.CTMO.
The following commands are provided as a sample for implementing data set controls:
ad 'SYS3.IOA.*.CTMO.**' uacc(none) owner(sys3) - audit(failures(read)) - data('BMC ControlM Started Task DS') pe 'SYS3.IOA.*.CTMO.**' id() acc(a) pe 'SYS3.IOA.*.CTMO.**' id(CONTROLM CONTDAY ) acc(u) pe 'SYS3.IOA.*.CTMO.**' id() acc(r)