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

There are 1 differences between versions v6 r7 (Jan. 20, 2015) (the "left" version) and v6 r8 (Nov. 23, 2022) (the "right" version).

Check ZMVZR001 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 STC 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(MVZSTC) Automated SENSITVE.RPT(MVZSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMVZ0001) Verify Collection: - PDI(ZMVZ0001) Verify that the accesses to the BMC MAINVIEW for z/OS STC data sets are properly restricted. ___ The restricted. ___ The RACF data set rules for the data sets restricts READ access to auditors and authorized users. ___ The users. ___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to systems programming personnel. ___ The personnel. ___ The RACF data set rules for the data sets restricts UPDATE and/or ALTER access to the BMC MAINVIEW for z/OS’s z/OS's STC(s) and/or batch user(s).

Discussion

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

Fix

The IAO ISSO will ensure that update and allocate access to BMC MAINVIEW for z/OS STC data sets is limited to System systems Programmers programmers and/or BMC MAINVIEW for z/OS’s z/OS's STC(s) and/or batch user(s) only. Read access can be given to auditors and 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 access and if required that all update and allocate access is logged. He The installing systems programmer 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 ISSO to ensure see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.BMCVIEW (data sets that are altered by the product’s product's STCs, this can be more specific) The following commands are provided as a sample for implementing data set controls: ad 'SYS3.BMCVIEW.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: BMC MAINVIEW for z/OS') pe 'SYS3.BMCVIEW.**' id(<syspaudt> <tstcaudt> MAINVIEW STCs) acc(a) pe 'SYS3.BMCVIEW.**' id(<audtaudt> authorized users) acc(r) setr generic(dataset) refresh