CA Auditor User data sets are not properly protected.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-224431	SRG-OS-000259	ZADTR002	SV-224431r1145197_rule	2025-09-27	7

Description
CA Auditor User 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(ADTUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0002). Verify that the accesses to the CA Auditor User 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 restricts WRITE and/or greater access to systems programming personnel, security personnel and auditors.

ℹ️ Check

Refer to the following report produced by the Data Set and Resource Data Collection: - SENSITVE.RPT(ADTUSER). Automated Analysis Refer to the following report produced by the Data Set and Resource Data Collection: - PDI(ZADT0002). Verify that the accesses to the CA Auditor User 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 restricts WRITE and/or greater access to systems programming personnel, security personnel and auditors.

✔️ Fix
The ISSO will ensure that WRITE and/or greater access to CA Auditor User data sets are limited to System Programmers, security personnel and auditors. 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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.EXAMINE The following commands are provided as a sample for implementing data set controls: ad 'SYS3.EXAMINE.' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA Auditor') pe 'SYS3.EXAMINE.' id(<syspaudt>) acc(a) pe 'SYS3.EXAMINE.**' id(<audtaudt> <secaaudt>) acc(A) setr generic(dataset) refresh

✔️ Fix

The ISSO will ensure that WRITE and/or greater access to CA Auditor User data sets are limited to System Programmers, security personnel and auditors. 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. He will identify if any additional groups have WRITE and/or greater access for specific data sets, and once documented he will work with the ISSO to see that they are properly restricted to the ACP (Access Control Program) active on the system. Data sets to be protected will be: SYS3.EXAMINE The following commands are provided as a sample for implementing data set controls: ad 'SYS3.EXAMINE.**' uacc(none) owner(sys3) - audit(failures(read)) - data('Vendor DS Profile: CA Auditor') pe 'SYS3.EXAMINE.**' id(<syspaudt>) acc(a) pe 'SYS3.EXAMINE.**' id(<audtaudt> <secaaudt>) acc(A) setr generic(dataset) refresh