z/OS BMC MAINVIEW for z/OS for RACF STIG Version Comparison

There are 8 differences between versions v6 r8 (Nov. 23, 2022) (the "left" version) and v7 r2 (Oct. 1, 2025) (the "right" version).

Check ZMVZR000 was changed between these two versions. Green, underlined text was added, red, struck-out text was removed.

The regular view of the left check and right check may be easier to read.

Title

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

Check Content

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

Discussion

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 product, which could result in compromising the operating system or sensitive data.

Fix

The IAO ISSO will ensure that update and alter WRITE and/or greater access to BMC MAINVIEW for z/OS installation data sets is limited to System system Programmers programmers only, and all update and alter WRITE and/or greater access is logged. READ Read access can be given to all authorized users. The installing Systems systems Programmer programmer will identify and document the product data sets and categorize them according to who will have update and alter WRITE and/or greater access and if required that all update and alter WRITE and/or greater access is logged. He The installing systems programmer will identify if any additional groups have update WRITE and/or alter greater access for specific data sets, and once documented documented, he will work with the IAO ISSO to ensure see that they are properly restricted to the ACP (Access Access Control Program) Program (ACP) 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(<syspaudt> <tstcaudt>) acc(a) pe 'SYS2.BMCVIEW.**' id(<audtaudt> 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(<syspaudt> <tstcaudt>) acc(a) pe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r) pe 'SYS3.BMCVIEW.**' id(MAINVIEW STCs) setr generic(dataset) refresh