Audit Journal Monitor

Reasons to buy

Analyze and monitor changes made to user profiles - this could be a change made to a user's special authority, user class or limited capabilities. You might want to know if someone changed their authority to *SECADM for example.

Quickly detect when invalid attempts are made to sign on - especially if this happens to be QSECOFR.

Changes to system values can be tracked and traced as these can have significant impact on areas of security and system performance.

Be informed when sensitive objects (such as the Payroll file) are created, deleted, restored, moved, renamed or the ownership to that object or access rights are changed.

Authority failures can be detected and brought to someone's immediate attention. For example, a user might be attempting to access an object to which they are not authorized, such as the Supplier master file.

Keep your Auditors happy by monitoring for programs that are changed to adopt authority - keep all those "back doors" closed.

Monitor and log when spooled files are read, created, deleted, held, released or the security attributes are changed.

Keep an eye on user profile swapping and be kept informed about what is happening on your system.

Know when users connect and disconnect through FTP.

Command string audit - monitor for when security related commands are executed or commands are issued by a specific user or job.

Actions regarding Jobs can be monitored - for example, when jobs are submitted, changed, ended, held etc.