CA Auditor installation data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224430	SRG-OS-000080	ZADTR000	SV-224430r1145195_rule	2025-09-27	7

Description
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
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. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

ℹ️ Check

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. If the following guidance is true, this is not a finding. The RACF data set rules for the data sets restrict READ access to auditors, security administrators, and/or CA Auditor's STCs and batch users. The RACF data set rules for the data sets restrict WRITE and/or greater access to systems programming personnel. The RACF data set rules for the data sets specify that all (i.e., failures and successes) WRITE and/or greater access are logged.

✔️ Fix
The ISSO will ensure that WRITE and/or greater access to CA Auditor installation data sets are limited to systems programmers only, and all WRITE and/or greater 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure 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

✔️ Fix

The ISSO will ensure that WRITE and/or greater access to CA Auditor installation data sets are limited to systems programmers only, and all WRITE and/or greater 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 WRITE and/or greater access and if required that all WRITE and/or greater access is logged. The installing systems programmer will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented will work with the ISSO to ensure 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