z/OS HCD for RACF STIG Version Comparison

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

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

IBM Hardware Configuration Definition (HCD) User data sets are not properly protected.

Check Content

a) a) Refer Refer to the following report produced by the Data Set and Resource Data Collection: - Collection: - SENSITVE.RPT(HCDUSER) Automated SENSITVE.RPT(HCDUSER) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZHCD0002) b) Verify Collection: - PDI(ZHCD0002) b) Verify that the access to the IBM Hardware Configuration Definition (HCD) install data sets is properly restricted. The data sets to be protected are the production and working IODF data sets as well as the activity log for the IODF data sets. Note: Currently sets. Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. ___ The SYS3.IODF*.**. ___ The RACF data set rules for the data sets does not restrict UPDATE and/or ALTER access to systems programming personnel. ___ The personnel. ___ The RACF data set rules for the data sets does not restrict READ access to automated operations users and operations personnel. ___ The personnel. ___ The RACF data set rules for the datasets does not specify that all (i.e., failures and successes) UPDATE and/or ALTER access will be logged. c) If logged. c) If all of the above are untrue, there is NO FINDING. d) If no finding. d) If any of the above is true, this is a FINDING. finding.

Discussion

IBM Hardware Configuration Definition (HCD) product has the capability to use privileged functions and/or to have access to sensitive data. Failure to properly restrict access to their 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 alter access to program product user data sets is limited to System systems Programmers programmers and all update and allocate access is logged. Ensure that read access is limited to auditors, Operations personnel, and Automated Operations users. The installing System systems Programmer programmer will identify and document the product user 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 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 Program) ) active on the system. Data sets to be protected will be: The production IODF data sets. (i.e. (i.e., hhhhhhhh.IODFnn) The working IODF data sets. (i.e. (i.e., hhhhhhhh.IODFnn.) The activity log for the IODF data sets. (i.e. (i.e., hhhhhhhh.IODFnn.ACTLOG) Note: Currently hhhhhhhh.IODFnn.ACTLOG) Note: Currently on most CSD systems the prefix for these data sets is SYS3.IODF*.**. The following commands are provided as a sample for implementing dataset controls: ad 'sys3.iodf*.**' uacc(none) owner(sys3) - audit(success(update) failures(read)) - data('Vendor DS Profile: IODF for HCD’) pe HCD') pe 'sys3.iodf*.**' id(syspaudt tstcaudt) acc(a) pe 'sys3.iodf*.**' id(audtaudt autoaudt operaudt) acc(r)