It is important to consider the security files and how they are defined to and used by the ESM. Audit the security data sets in use and monitor this usage over time to track deviations.
For example, a systems programmer uses the “A” set of security files with the ESM. During a routine audit it is found that the “B” set are being used. If the change is legitimate, there should be auditable change control records. If the change is improper an audit of the security file contents might find not find any abnormalities. Without an audit to check on the legitimacy of the actual security files in use this situation might not be caught.
This function displays the appropriate security files for the ESM. For CA ACF2, this includes the primary and alternate cluster/backup data sets. For CA Top Secret, this includes the SECFILE and audit tracking file. For RACF, this includes the primary data sets and any backup data sets allocated.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |