Auditing database access
Auditing database access is a much bigger topic than you might expect because it can cover a whole range of requirements.
Getting ready
First, decide which of these you want and look at the appropriate subsection:
- Which privileges can be executed? (Auditing access)
- Which SQL statements were executed? (Auditing SQL)
- Which tables were accessed? (Auditing table access)
- Which data rows were changed? (Auditing data changes)
- Which data rows were viewed? (Not described here—usually too much data)
Auditing just SQL produces the lowest volume of audit log information, especially if you choose to log only data definition language (DDL). Higher levels accumulate more information very rapidly, so you may quickly decide not to do this in practice. Read each section to understand the benefits and trade-offs.
Auditing access
Reviewing which users have access to which information is important. There are a few ways of doing...
