BMC MAINVIEW for z/OS installation data sets are not properly protected.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-16932	ZMVZR000	SV-33836r1_rule	DCSL-1 ECAR-1 ECAR-2 ECCD-1 ECCD-2	Medium

Description
BMC MAINVIEW for z/OS installation 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.

STIG	Date
z/OS BMC MAINVIEW for z/OS for RACF STIG	2015-01-16

Details

Check Text ( C-4636r1_chk )
Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(MVZRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMVZ0000) Verify that the accesses to the BMC MAINVIEW for z/OS installation data sets are properly restricted. ___ The RACF data set rules for the data sets restricts READ access to all authorized users. ___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. ___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

Check Text ( C-4636r1_chk )

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

- SENSITVE.RPT(MVZRPT)

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

- PDI(ZMVZ0000)

Verify that the accesses to the BMC MAINVIEW for z/OS installation data sets are properly restricted.

___ The RACF data set rules for the data sets restricts READ access to all authorized users.

___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel.

___ The RACF data set rules for the data sets specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

Fix Text (F-326r1_fix)
The IAO will ensure that update and alter access to BMC MAINVIEW for z/OS installation data sets is limited to System Programmers only, and all update and alter access is logged. Read access can be given to all authorized 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 alter 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. Data sets to be protected will be: SYS2.BMCVIEW. SYS3.BMCVIEW. (data sets that are not altered by product STCs, can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS2.BMCVIEW.' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('BMC MAINVIEW for z/OS Install DS') pe 'SYS2.BMCVIEW.' id( ) acc(a) pe 'SYS2.BMCVIEW.' id( authorized users) acc(r) pe 'SYS2.BMCVIEW.' id(MAINVIEW STCs) ad 'SYS3.BMCVIEW.' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('BMC MAINVIEW for z/OS Install DS') pe 'SYS3.BMCVIEW.' id( ) acc(a) pe 'SYS3.BMCVIEW.' id( authorized users) acc(r) pe 'SYS3.BMCVIEW.' id(MAINVIEW STCs) setr generic(dataset) refresh

Fix Text (F-326r1_fix)

The IAO will ensure that update and alter access to BMC MAINVIEW for z/OS installation data sets is limited to System Programmers only, and all update and alter access is logged. Read access can be given to all authorized 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 alter 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.

Data sets to be protected will be:
SYS2.BMCVIEW.**
SYS3.BMCVIEW.** (data sets that are not altered by product STCs, can be more specific)

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

ad 'SYS2.BMCVIEW.**' uacc(none) owner(sys2) -
audit(success(update) failures(read)) -
data('BMC MAINVIEW for z/OS Install DS')
pe 'SYS2.BMCVIEW.**' id( ) acc(a)
pe 'SYS2.BMCVIEW.**' id( authorized users) acc(r)
pe 'SYS2.BMCVIEW.**' id(MAINVIEW STCs)

ad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) -
audit(success(update) failures(read)) -
data('BMC MAINVIEW for z/OS Install DS')
pe 'SYS3.BMCVIEW.**' id( ) acc(a)
pe 'SYS3.BMCVIEW.**' id( authorized users) acc(r)
pe 'SYS3.BMCVIEW.**' id(MAINVIEW STCs)

setr generic(dataset) refresh