Auditing the security officer’s actions

You can keep a record of all actions performed by users with *ALLOBJ and *SECADM special authority for tracking purpose.

To do this, you can use the action auditing value in the user profile:
  1. For each user with *ALLOBJ and *SECADM special authority, use the CHGUSRAUD command to set the AUDLVL to have all values that are not included in the QAUDLVL or QAUDLVL2 system values on your system. For example, if the QAUDLVL system value is set to *AUTFAIL, *PGMFAIL, *PRTDTA, and *SECURITY, use this command to set the AUDLVL for a security officer user profile:
              AUDLVL(*CMD *CREATE *DELETE +
                     *OBJMGT *OFCSRV *PGMADP +
                     *SAVRST *SERVICE, +
                     *SPLFDTA *SYSMGT)
    Action auditing shows all the possible values for action auditing.
  2. Remove the *AUDIT special authority from user profiles with *ALLOBJ and *SECADM special authority. This prevents these users from changing the auditing characteristics of their own profiles.

    You cannot remove special authorities from the QSECOFR profile. Therefore, you cannot prevent a user signed on as QSECOFR from changing the auditing characteristics of that profile. However, if a user signed on as QSECOFR uses the CHGUSRAUD command to change auditing characteristics, an AD entry type is written to the audit journal.

    It is recommended that security officers (users with *ALLOBJ or *SECADM special authority) use their own profiles for better auditing. The password for the QSECOFR profile should not be distributed.

  3. Make sure the QAUDCTL system value includes *AUDLVL.
  4. Use the DSPJRN command to review the entries in the audit journal using the techniques described in Analyzing audit journal entries with query or a program.