Chapter 9: Database Security and Auditing 331
Auditing
Oracle uses a number of different auditing methods to monitor what kinds of privileges are being
used as well as what objects are being accessed. Auditing does not prevent the use of these
privileges, but it can provide useful information to uncover abuse or misuse of privileges.
In Table 9-16, we summarize the different types of auditing in an Oracle database.
In the next few sections, we??™ll review how a DBA can manage audits of both system and
object privilege use. When the granularity is required, a DBA can use fine-grained auditing to
monitor access to certain rows or columns of a table, not just whether the table was accessed.
Auditing Locations
Audit records can be sent to either the SYS.AUD$ database table or an operating system file.
To enable auditing and specify the location where audit records are recorded, the initialization
parameter AUDIT_TRAIL is set to one of the following values:
Parameter Value Action
NONE, FALSE Disable auditing.
OS Enable auditing. Send audit records to an operating system file.
DB, TRUE Enable auditing. Send audit records to the SYS.AUD$ table.
DB_EXTENDED Enable auditing. Send audit records to the SYS.AUD$ table, and record
additional information in the CLOB columns SQLBIND and SQLTEXT
XML Enable auditing and write all audit records in XML format.
EXTENDED Enable auditing and record all columns in the audit trail, including
SqlText and SqlBind values.
Pages:
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545