z/OS CA Auditor 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 ZADTR000 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 Auditor 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(ADTRPT) Automated SENSITVE.RPT(ADTRPT) Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0000) Verify Collection: - PDI(ZADT0000) Verify that the accesses to the CA Auditor installation data sets are properly restricted. ___ The restricted. ___ The RACF data set rules for the data sets restricts READ access to auditors, security administrators, and/or CA Auditor’s Auditor's STCs and batch 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 specify that all (i.e., failures and successes) UPDATE and/or ALTER access are logged.

Discussion

CA Auditor 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.

Fix

The IAO ISSO will ensure that update and alter access to CA Auditor installation data sets are limited to System systems Programmers programmers only, and all update and ater alter access is logged. Read access can be given to auditors, security administrators, and/or CA Auditor’s Auditor's STCs and batch 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 alter 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: SYS2.EXAMINE SYS2A.EXAMINE The following commands are provided as a sample for implementing data set controls: ad 'SYS2.EXAMINE.**' uacc(none) owner(sys2) - audit(success(update) failures(read)) - data('Vendor DS Profile: CA Auditor/Examine') pe 'SYS2.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS2.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r) ad 'SYS2A.EXAMINE.**' uacc(none) owner(sys2a) - audit(success(update) failures(read)) - data('Vendor DS Profile: CA Auditor/Examine') pe 'SYS2A.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS2A.EXAMINE.**' id(<audtaudt> <secaaudt> EXAMMON) acc(r) setr generic(dataset) refresh