ABSTRACT
In the previous chapters, you learned about auditing capabilities within the Oracle database. All of these chapters dealt with how to defi ne and control what gets audited-but the focus was always on a single database. Th ere was no discussion on how you can collect this audit data from many databases nor was there a discussion around the important issues relating to where to store the audit data and how to protect it from tampering. Th is is because database vendors tend to focus on the capabilities that they can build within the database engine, and Oracle has been no exception-until fairly recently. Oracle Audit Vault (AV) is a relatively new product that addresses how to collect audit data, how to manage it, and how to protect it.
