CA Auditor installation data sets are not properly protected.

From z/OS CA Auditor for RACF STIG

Part of ZB000000

Associated with IA controls: ECCD-2, ECAR-2, ECCD-1, ECAR-1, DCSL-1

SV-31919r1_rule CA Auditor installation data sets are not properly protected.

Vulnerability 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.

Check content

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

Fix text

The IAO will ensure that update and alter access to CA Auditor installation data sets are limited to System Programmers only, and all update and ater access is logged. Read access can be given to auditors, security administrators, and/or CA Auditor’s STCs and batch users. The installing Systems 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 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 to 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() acc(a) pe 'SYS2.EXAMINE.**' id( 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() acc(a) pe 'SYS2A.EXAMINE.**' id( EXAMMON) acc(r) setr generic(dataset) refresh

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer