The Triora Group

We’re often asked about the different ways of auditing to help ensure security for an E-Business Suite environment. Here’s a quick summary of some of your options:

Operating System Auditing
Many types of auditing are available, especially if “sudo” is utilized. “sudo” should be utilized for ALL accounts, though we find that it often is not in our clients’ environments

Database Auditing

• Setting different “audit_trail” levels in the database initialization parameters - the more detail you audit, the slower the performance of the server. You have to really watch the audit tables’ growth - this is normally NOT set in an E-Business Suite environment
• Auditing of specific tables (or columns with Database Vault) by database id - this is used by most Apps DBAs as it has limited performance impact. To use this type of auditing, the timed_statistics setting in the database init.ora file may need to be set to true depending on the feature to be utilized

Applications Auditing

• Automatic current record audit information is the standard provided by the Applications, however, NO historical auditing is provided
• Auditing enabled via the System Administrator responsibility for specific tables captures Applications users and changes but usually is limited to select payroll and fnd tables. The audit tables will grow and auditing usually needs to be disabled for all types of upgrades to avoid performance issues
• Auditing enabled via the System Administrator responsibility at certain levels - user, application, responsibility, form - should ALWAYS be set to form for the most granular information when the Systen Administrator reviews users in the applications. Setting this option does NOT impact performance

If you enjoyed this post, make sure you subscribe to my RSS feed!