# Logging and Auditing Oracle Database Webinar

- URL: https://www.integrigy.com/security-resources/logging-and-auditing-oracle-database-webinar
- Published: 2015-01-21
- Type: Webinar
- Products: Oracle Database
- Focus areas: Auditing
- PDF: https://www.integrigy.com/sites/default/files/Integrigy%20Logging%20and%20Auditing%20Oracle%20Database.pdf

> Slides from an Integrigy webinar on the auditing and logging capabilities at different layers of Oracle Database, with recommendations for configuring them to capture critical security events.

The auditing and logging capabilities of Oracle Database can satisfy most organizations' security and compliance requirements, but setting up auditing and using its data can be complex and error-prone. These slides from one of our webinars outline the auditing and logging available at each layer of the database and our recommendations for configuring them to capture key application and security events.

The slides are based on our [Integrigy Guide to Database Auditing and Logging](https://www.integrigy.com/security-resources/integrigy-guide-database-auditing-and-logging) and [Integrigy Guide to Auditing and Logging in Oracle E-Business Suite](https://www.integrigy.com/security-resources/guide-auditing-oracle-applications). DBAs and security teams can then decide what to audit, alert on and report, and raise their auditing maturity one level at a time.

## Key Points

- Auditing done only for a compliance checkbox, poorly defined, unreviewed and not mapped to business requirements, has zero value, and most of the work comes after enabling it: monitoring, alerting, reporting and reviewing take 80% of the effort, archiving and purging 10%, and design and enabling 5% each.
- Before 12c, Oracle Database logs and audits at five layers, each set by its own parameters: the listener log (`LOGGING_name = ON`), the alert log (`BG_DUMP_DEST`), SYS auditing (`AUDIT_SYS_OPERATIONS`), standard auditing (`AUDIT_TRAIL`, to the `AUD$` table, OS or XML files, or syslog with `AUDIT_SYSLOG_LEVEL`) and fine-grained auditing (`DBMS_FGA.add_policy`, to `FGA_LOG$`).
- Startup, shutdown and SYS logons are always audited to the operating system, and we highly recommend `AUDIT_SYS_OPERATIONS` to record what SYS, SYSDBA and SYSOPER users do; standard, or traditional, auditing, which Oracle desupported in 23ai (now 26ai) in favor of Unified Auditing, audited 25 events by default and had more than 300 audit commands (`sys.stmt_audit_option_map`).
- Our framework maps 14 foundation security events to PCI DSS 10.2, SOX, HIPAA, ISO 27001 and FISMA, and its maturity model enables baseline auditing and alerts (Level 1), sends the logs to a centralized solution outside the database and application, such as Oracle Audit Vault (Level 2), then adds FGA, functional logging and more complex alerting (Level 3).
- Level 1 alerts for Oracle E-Business Suite cover direct database logins to EBS schema accounts, SYSADMIN logins and failed logins, logins to and unlocking of generic seeded accounts, new database accounts, updates to AOL tables under AuditTrail, and turning off Sign-On Audit, AuditTrail, Page Access Tracking or audit sys operations.
- To tie audit records to changes and people, have DBAs enter change ticket numbers and use the client identifier: EBS sets `CLIENT_IDENTIFIER` to `FND_USER.USERNAME` as of Release 12 (for 11i, now desupported, see Doc ID 1130254.1), PeopleTools 8.50 and later set the `PSOPRID`, and OBIEE needs a connect script calling `DBMS_SESSION.SET_IDENTIFIER`.
