BMC CONTROL-D user data sets must be properly protected.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-21592	ZCTDA002	SV-32162r3_rule		Medium

Description
BMC CONTROL-D User data sets, CDAM and Repository, 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.

STIG	Date
z/OS BMC CONTROL-D for ACF2 STIG	2018-09-20

Details

Check Text ( C-3320r7_chk )
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(CTMUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZCTD0002) Verify that the accesses to the BMC CONTROL-D User data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The ACF2 data set access authorizations restrict READ access to auditors. ___ The ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The ACF2 data set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users. ___ The ACF2 data set access authorizations restrict UPDATE access to centralized and decentralized security personnel, and/or CONTROL-D end users.

Check Text ( C-3320r7_chk )

Refer to the following report produced by the Data Set and Resource Data Collection:

- SENSITVE.RPT(CTMUSER)

Automated Analysis
Refer to the following report produced by the Data Set and Resource Data Collection:

- PDI(ZCTD0002)

Verify that the accesses to the BMC CONTROL-D User data sets are properly restricted. If the following guidance is true, this is not a finding.

___ The ACF2 data set access authorizations restrict READ access to auditors.

___ The ACF2 data set access authorizations restrict WRITE and/or greater access to systems programming personnel.

___ The ACF2 data set access authorizations restrict WRITE and/or greater access to the BMC STCs and/or batch users.

___ The ACF2 data set access authorizations restrict UPDATE access to centralized and decentralized security personnel, and/or CONTROL-D end users.

Fix Text (F-225r7_fix)
The IAO must ensure that WRITE and/or greater access to BMC CONTROL-D User data sets are limited to System Programmers and BMC STCs and/or batch users. Additionally, UPDATE access can be given to centralized and decentralized security personnel, and BMC users. The IAO can approve ALLOC access in circumstances where it is determined to be necessary and appropriate for systems operations to execute in a normal secure manner. READ access can be given to auditors. 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 must 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.*.CTDR. CTRUSR. CTDSRV. CTDJB1. The following commands are provided as a sample for implementing data set controls: $KEY(SYS3) IOA.-.CTDR.- UID(syspaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(tstcaudt) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(BMC STCs) R(A) W(A) A(A) E(A) IOA.-.CTDR.- UID(bmcuser) R(A) W(A) E(A) IOA.-.CTDR.- UID(secaaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(secdaudt) R(A) W(A) E(A) IOA.-.CTDR.- UID(audtaudt) R(A) E(A) $KEY(CTRUSR) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDSRV) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A) $KEY(CTDJB1) - UID(syspaudt) R(A) W(A) A(A) E(A) - UID(tstcaudt) R(A) W(A) A(A) E(A) - UID(BMC STCs) R(A) W(A) A(A) E(A) - UID(bmcuser) R(A) W(A) E(A) - UID(secaaudt) R(A) W(A) E(A) - UID(secdaudt) R(A) W(A) E(A) - UID(audtaudt) R(A) E(A)

Fix Text (F-225r7_fix)

The IAO must ensure that WRITE and/or greater access to BMC CONTROL-D User data sets are limited to System Programmers and BMC STCs and/or batch users. Additionally, UPDATE access can be given to centralized and decentralized security personnel, and BMC users. The IAO can approve ALLOC access in circumstances where it is determined to be necessary and appropriate for systems operations to execute in a normal secure manner. READ access can be given to auditors.

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 must 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.*.CTDR.
CTRUSR.
CTDSRV.
CTDJB1.

The following commands are provided as a sample for implementing data set controls:

$KEY(SYS3)
IOA.-.CTDR.- UID(syspaudt) R(A) W(A) A(A) E(A)
IOA.-.CTDR.- UID(tstcaudt) R(A) W(A) A(A) E(A)
IOA.-.CTDR.- UID(BMC STCs) R(A) W(A) A(A) E(A)
IOA.-.CTDR.- UID(bmcuser) R(A) W(A) E(A)
IOA.-.CTDR.- UID(secaaudt) R(A) W(A) E(A)
IOA.-.CTDR.- UID(secdaudt) R(A) W(A) E(A)
IOA.-.CTDR.- UID(audtaudt) R(A) E(A)

$KEY(CTRUSR)
- UID(syspaudt) R(A) W(A) A(A) E(A)
- UID(tstcaudt) R(A) W(A) A(A) E(A)
- UID(BMC STCs) R(A) W(A) A(A) E(A)
- UID(bmcuser) R(A) W(A) E(A)
- UID(secaaudt) R(A) W(A) E(A)
- UID(secdaudt) R(A) W(A) E(A)
- UID(audtaudt) R(A) E(A)

$KEY(CTDSRV)
- UID(syspaudt) R(A) W(A) A(A) E(A)
- UID(tstcaudt) R(A) W(A) A(A) E(A)
- UID(BMC STCs) R(A) W(A) A(A) E(A)
- UID(bmcuser) R(A) W(A) E(A)
- UID(secaaudt) R(A) W(A) E(A)
- UID(secdaudt) R(A) W(A) E(A)
- UID(audtaudt) R(A) E(A)

$KEY(CTDJB1)
- UID(syspaudt) R(A) W(A) A(A) E(A)
- UID(tstcaudt) R(A) W(A) A(A) E(A)
- UID(BMC STCs) R(A) W(A) A(A) E(A)
- UID(bmcuser) R(A) W(A) E(A)
- UID(secaaudt) R(A) W(A) E(A)
- UID(secdaudt) R(A) W(A) E(A)
- UID(audtaudt) R(A) E(A)