||Oracle Tips by Burleson
Chapter 11 Oracle Fine Grained Auditing
Note the columns referenced in the audit_column
and audit_condition parameters are different. This might create some
confusion on how various situations are handled. It can be
understood by using a few simple rules.
If the query selects the columns mentioned in
the audit_column parameter, then check the next step; otherwise,
this is not a candidate for auditing.
If the query selects rows that satisfy the
clause in the audit_condition, then the statement is audited;
otherwise, this is not audited.
Sometimes the query might reference the columns
implicitly, not explicitly naming them. The auditing is triggered in
that case, too. For instance, the following query is audited based
on the policy defined earlier.
select * from claims;
Even though the columns are not named, the fact
that all columns are selected triggers the audit. Another case is
select claim_id from claims where ssn =
The following table shows the expected audit
triggering in different scenarios.
The above text is
an excerpt from:
Oracle Privacy Security Auditing
Final Word on Oracle Security
This is the only authoritative
book on Oracle Security, Oracle Privacy, and Oracle Auditing written
by two of the world’s leading Oracle Security experts.
This indispensable book is only
and has an
immediate download of working security scripts: