What Do Oracle Audit Vault Collection Agents Do?
The Oracle Audit Vault is installed on a server, and collector agents are installed on the hosts running the source databases. These collector agents communicate with the audit vault server.
If the collection agents are not active, no audit data is lost, as long as the source database continues to collect the audit data. When the collection agent is restarted, it will capture the audit data that the source database had collected during the time the collection agent was inactive.
There are three types of agent collectors for Oracle databases. There are other collectors for third-party database vendors such as SAP Sybase, Microsoft SQL-Server, and IBM DB2.
Audit Value Collectors for Oracle Databases* |
||
---|---|---|
Audit Trail Type |
How Enabled |
Collector Name |
Database audit trail |
For standard audit records: For fine-grained audit records: The |
DBAUD |
Operating system audit trail |
For standard audit records: For syslog audit trails, For fine-grained audit records: The |
OSAUD |
Redo log files |
The table that you want to audit must be eligible. See "Creating Capture Rules for Redo Log File Auditing" for more information. |
REDO |
*Note if using Oracle 12c; the assumption is that Mixed Mode Unified Auditing is being used
If you have questions, please contact us at mailto:info@integrigy.com
Reference
- Integrigy Guide to Oracle Audit Vault Integrigy Guide to Oracle Audit Vault
- Presentation “Developing Value with Oracle Audit Vault Developing Value with Oracle Audit Vault