z/OS CA MIM for RACF STIG Version Comparison

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

Check ZMIMR001 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

CA MIM Resource Sharing STC data sets will be properly protected.

Check Content

Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(MIMSTC) Automated SENSITVE.RPT(MIMSTC) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZMIM0001) Verify Collection: - PDI(ZMIM0001) Verify that the accesses to the CA MIM Resource Sharing STC data sets are properly restricted. If the following guidance is true, this is not a finding. ___ The finding. ___ The RACF data set access authorizations restrict READ access to auditors and authorized users. ___ The users. ___ The RACF data set access authorizations restrict WRITE and/or greater access to systems programming personnel. ___ The personnel. ___ The RACF data set access authorizations restrict WRITE and/or greater access to the CA MIM Resource Sharing’s Sharing's STC(s) and/or batch user(s). ___ The user(s). ___ The RACF data set access authorizations for the data sets specify UACC(NONE) and NOWARNING.

Discussion

CA MIM Resource Sharing 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 WRITE and/or greater access to CA MIM Resource Sharing STC data sets is limited to System systems Programmers programmers and/or CA MIM Resource Sharing’s Sharing'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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. He The installing systems programmer will identify if any additional groups have WRITE and/or greater 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. (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 product's installation guide and can be site specific.) Data sets to be protected will be: SYS3.MIMGR. (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.MIMGR.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA MIM Resource Sharing') pe 'SYS3.MIMGR.**' id(<syspaudt> <tstcaudt> CA MIM STCs) acc(a) pe 'SYS3.MIMGR.**' id(<audtaudt> authorized users) acc(r) setr generic(dataset) refresh