Select any two versions of this STIG to compare the individual requirements
Select any old version/release of this STIG to view the previous requirements
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTRRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTR0000) Verify that the accesses to the BMC CONTROL-M/Restart installation data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restrict READ access to auditors, BMC users, and BMC STCs and/or batch users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The RACF data set access authorizations specify that all (i.e., failures and successes) WRITE and/or greater access are logged. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.
The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-M/Restart installation data sets are limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, 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 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. The installing systems programmer will identify if any additional groups have update and/or alter access for specific 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 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: SYS2.IOA.*.CTRO. The following commands are provided as a sample for implementing data set controls: ad 'SYS2.IOA.*.CTRO.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: BMC CONTROL-M/Restart') pe 'SYS2.IOA.*.CTRO.**' id(<syspaudt>) acc(a) pe 'SYS2.IOA.*.CTRO.**' id(<audtaudt> <bmcuser>) acc(r) pe 'SYS2.IOA.*.CTRO.**' id(CONTROLR) acc(r) setr generic(dataset) refresh
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTRUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTR0002) Verify that the accesses to the BMC CONTROL-M/Restart Archived Sysout data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The RACF data set access authorizations restrict READ access to auditors and BMC users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to Production Control Scheduling personnel, scheduled batch user(s), systems programming personnel, and the BMC STCs and/or batch users. ___ The RACF data set access authorizations specify UACC(NONE) and NOWARNING.
Ensure that WRITE and/or greater access to BMC CONTROL-M/Restart Archived Sysout data sets are 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 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. The installing Systems Programmer will identify if any additional groups have update and/or alter 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. (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: CTRSYS. The following commands are provided as a sample for implementing data set controls: ad 'CTRSYS.**' uacc(none) owner(CTRSYS) - data('BMC CONTROL-M/Restart Archived Sysout') pe 'CTRSYS.**' id(CONTROLM CONTDAY) acc(a) pe 'CTRSYS.**' id(<syspaudt> <autoaudt> <pcspaudt>) acc(a) pe 'CTRSYS.**' id(<audtaudt>) acc(r) pe 'CTRSYS.**' id(<bmcuser>) acc(r) setr generic(dataset) refresh