CA Auditor User datasets are not properly protected.

CA Auditor User datasets have the ability to use privileged functions and/or have access to sensitive data. Failure to properly restrict access to these datasets could result in violating the integrity of the base product, which could result in compromising the operating system or sensitive data.

Refer to the following report produced by the dataset and Resource Data Collection:

- SENSITVE.RPT(ADTUSER).

Automated Analysis Refer to the following report produced by the dataset and Resource Data Collection:

- PDI(ZADT0002).

Verify that the accesses to the CA Auditor User datasets are properly restricted. If the following guidance is true, this is not a finding.

The ACF2 dataset rules for the datasets restrict WRITE and/or greater access to systems programming personnel, security personnel, and auditors.

The ISSO will ensure that WRITE and/or greater access to CA Auditor User datasets is limited to systems programmers, security personnel, and auditors.

The installing systems programmer will identify and document the product datasets, categorize them according to who will have WRITE and/or greater access, and if required, ensure that all WRITE and/or greater access is logged. The systems programmer will identify if any additional groups have WRITE and/or greater access for specific datasets, and once documented will work with the ISSO to ensure that they are properly restricted to the ACP (Access Control Program) active on the system.

Datasets to be protected will be: dataasets SYS3.EXAMINE

The following commands are provided as a sample for implementing dataset controls:

$KEY(SYS3) EXAMINE.- UID(<syspaudt>) R(A) W(A) A(A) E(A) EXAMINE.- UID(<audtaudt>) R(A) W(A) A(A) E(A) EXAMINE.- UID(<secaaudt>) R(A) W(A) A(A) E(A)