The amount of information available in the audit journal is impressive, but the AJ also is one of the system's best-kept secrets.
The following is taken from the white paper "Ways to Use the IBM i Audit Journal," available for download free from the MC White Paper Center.
One of my favorite integrated features of IBM i (iSeries) is auditing. The system can be configured to audit security-relevant actions of every profile on the system or just a handful. Or it can be configured to audit the use of objects.
The amount of information available in the audit journal is really quite amazing. Unfortunately, it's one of the system's best-kept secrets! Even when people are aware of the audit journal, they often have no idea of what type of information is available. They assume—incorrectly—that it's strictly information needed by auditors. Unbeknownst to many system administrators is the vast information in the audit journal that they could use on a daily basis. Even more of a mystery is how one "harvests" or retrieves information out of the audit journal in a readable format.
SkyView Audit Journal Reporter is an i5/OS and IBM i product that provides pre-defined audit reports on the security events recorded in the i5/OS audit journal. Simply put, SkyView Audit Journal Reporter (or AJR as it's fondly referred to) was created to "de-mystify" the audit journal and make the information in it easily accessible through its pre-defined reports. As your security and compliance experts, we've examined the audit journal entries, determined what information is needed, and formatted the reports so you don't have to have knowledge of the intricacies of the i5/OS audit journal.
You just have to decide which reports to run and what profiles or objects to run them against. The following are some of the "Ways to Use SkyView Audit Journal Reporter":
- Monitor for invalid sign-on attempts.
- Move to security level 40 (or 50) from level 30.
- Determine who or what process has caused something within the SkyView Partners Policy Minder product to become non-compliant.
- Compare the programs created or re-compiled into a production library with change management tickets.
- Determine who or what process deleted an object.
- List all of the actions taken by a particular user.
- Discover if someone has tried to access critical files (such as files containing private or confidential data) without authority.
- Audit the use of an object by users outside "normal" processes.
- Report on who changes system values.
- Monitor the use of particular commands.
- Find out more details when a user receives a "Not authorized to object xxx…" message.
- Discover if someone is trying to sign on with IBM profiles QSECOFR, QPGMR, QSYSOPR, QUSER, QSRV, or QSRVBAS.
- Find out when the QSECOFR password is changed.
- Monitor the auditing values for critical or sensitive objects.
- Detect when critical job descriptions and subsystem descriptions have been changed.
Want to learn more? For Carol's full comments and a description of each of the above items, download the white paper Ways to Use the IBM i Audit Journal, available for free from the MC White Paper Center.
as/400, os/400, iseries, system i, i5/os, ibm i, power systems, 6.1, 7.1, V7,
LATEST COMMENTS
MC Press Online