Figure sigad_vm_008.png describes the Oracle Audit Vault and Database Firewall architecture. From top to bottom, left to right, are the following components:
The top left corner contains an area representing the Audit Vault Server. It has two sets of components, one for an auditor and one for an administrator.
For the auditor, these components are shown: Alerts and Notifications, Stored Procedure Auditing, Audit Policy Management, Firewall Policy Management, Reporting.
For the administrator, these components are shown: Database Firewall Management, Third Party Integration, Archive and Backup, High Availability, Audit Vault Agent Management, Audit Data Lifecycle Management.
To the right of the Audit Vault Server are the auditor and administrator users, who each have a two-way connection with the server. (That is, they can send and receive data.)
Following the Audit Vault Server area are 10 icons representing secured targets. From left to right, they are: MySQL, SQLAnywhere, Oracle, SQL Server, Sybase ASE, IBM DB2, Solaris OS, Windows OS, Active Directory, Oracle ACFS. Above these icons, except for MySQL and SQLAnywhere, are smaller icons representing Audit Vault Agents. The figure shows an arrow indicating communication between these agents and the Audit Vault Server.
Below the secured target icons is a box representing the Database Firewall. Inside this box are two boxes labeled Traffic Management and Policy Engine.
Below the Database Firewall box, there are icons representing clients and applications. Two arrows point out from the set of clients and applications. One arrow points to the secured targets area directly, and the other other goes first into the firewall then from the firewall to the database secured targets. This indicates that for database secured targets, there may be a firewall deployed between the clients and the databases to monitor network traffic to those targets.