Rule ID
SV-224391r1145215_rule
Version
V7R2
CCIs
BMC CONTROL-D 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: - SENSITVE.RPT(CTDSTC). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0001). Verify that the accesses to the BMC CONTROL-D STC 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 CONTROL-D end users. The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. The RACF data set access authorizations restrict WRITE and/or greater access to BMC STCs and/or batch users. The RACF data set access authorizations restrict UPDATE access to centralized and decentralized security personnel. The RACF data set access authorizations specify UACC(NONE) and NOWARNING.
The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D STC data sets are limited to systems programmers and BMC STCs and/or batch users. UPDATE access can be given to centralized and decentralized security personnel. 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 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 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:
SYS3.IOA.*.CTDO.
The following commands are provided as a sample for implementing data set controls:
ad 'SYS3.IOA.*.CTDO.**' uacc(none) owner(sys3) -
audit(failures(read)) -
data('BMC CONTROL-D STC DS')
pe 'SYS3.IOA.*.CTDO.**' id(syspaudt tstcaudt) acc(a)
pe 'SYS3.IOA.*.CTDO.**' id(BMC STCs) acc(a)
pe 'SYS3.IOA.*.CTDO.**' id(secaaudt secdaudt) acc(u)
pe 'SYS3.IOA.*.CTDO.**' id(bmcuser audtaudt) acc(r)
setr generic(dataset) refresh