The ISSO will ensure that WRITE and/or greater access to BMC CONTROL-D installation datasets is limited to systems programmers only, and all WRITE and/or greater access is logged. READ access can be given to auditors, BMC users, security personnel (domain level and decentralized), 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 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:
SYS2.IOA.*.CTDI
The following commands are provided as a sample for implementing dataset controls:
$KEY(SYS2)
IOA.-.CTDI.- UID(<syspaudt>) R(A) W(L) A(L) E(A)
IOA.-.CTDI.- UID(<audtaudt>) R(A) E(A)
IOA.-.CTDI.- UID(<bmcuser>) R(A) E(A)
IOA.-.CTDI.- UID(<secaaudt>) R(A) E(A)
IOA.-.CTDI.- UID(<secdaudt>) R(A) E(A)
IOA.-.CTDI.- UID(CONTROLD) R(A) E(A)