S317045 Real-World Deployment and Best Practices with Oracle Audit Vault

2. S317045Real-World Deployment and Best Practices with Oracle Audit Vault Tammy Bednar, Sr. Principal Product Manager, Oracle Mike McClure , Sr. Database Administrator, Amazon

3. The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

4. Program Agenda <Insert Picture Here> • Why Audit? • Oracle Audit Vault Reports • Implementing Audit Vault at Amazon • Best Practices • Q&A

5. Why Audit? • Its all about protecting sensitive data, maintaining customer trust, and protecting the business • Trust-but-verify that your employees are only performing operations required by the business • Detective controls to monitor what is really going on • Reduce the curiosity seekers from looking at data • Compliance demands that privileged users be monitored • Know what is going on before others tell you

6. Policies HR Data ! Alerts CRM Data Built-in Reports ERP Data Custom Reports Databases Oracle Audit VaultAutomated Activity Monitoring & Audit Reporting Audit Data Auditor • Consolidate audit data into secure repository • Detect and alert on suspicious activities • Out-of-the box compliance reporting • Centralized audit policy management

7. Audit Vault Reports

8. 8

9. 9

10. Any of the Audit Vault reports can be scheduled to run automatically and archived in the Audit Vault repository for viewing, printing, emailing, and attestation 10

11. Oracle Audit VaultDatabase Audit Support 11

12. Oracle Audit VaultFeatures by Release

13. Audit Vault at Amazon

14. Michael McclureDatabase Administrator Global Financial Systems Amazon.com

15. Oracle Audit Vault Catching the Big Bad Wolf

16. To Be, or Not To Be…? That is the Question….

17. Why Audit Vault? • Reduce Cost/Increase efficiency related to S-Ox, HIPPA, PCI/DSS+ and other compliance reporting • Cross Database compatibility • Separation of Duties • More efficient audit policy management • Catch the Big Bad Wolf

18. Auditing Challenges • We have lots of different RDBMS systems; They all audit differently • Policies/mechanisms for auditing are different across the organization • “Dealing with” our audit data • Watching the watchers – who do you trust?

19. Oracle Audit Vault Architecture

20. Concerns • Performance / Impact • Resource utilization • Scalability • Fault Tolerance / BCP / DR

21. Generation audit_trail = db* audit_trail = xml* redo Collection DBAUD Collector Collection OSAUD Collector REDO Collector

22. Which did we choose? • We liked the OSAUD collector from the XML audit trail

23. A Closer look at XML Audit Trail Generation and Collection

24. Audit Vault Low Impact / Fault Tolerant Architecture

25. AV Server & Dataguard w/FSFO • Using the OUI, install the AV Server application on two different machines using the same SID. • Choose one machine to be your primary machine and validate that AV works by logging into the web app. • Turn off Database Vault • Force Logging in your primary database • Modify init.ora parms and listener.ora for Dataguard and AV compatibility • Other cleanup of standardized AV install • Delete the database on your chosen standby server • Instantiate a DG standby on your standby server • Create and enable FSFO configuration

26. Disabling Database Vault Shutdown the database Recompile the oracle executable with Database Vault off:cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk dv_off cd $ORACLE_HOME/bin relink oracle Startup the database Grant the following:grant create user, alter user to avsys;

27. Force logging for Dataguard Force logging at the database level:SQL> alter database force logging; Force logging for each tablespace:SQL> select 'alter tablespace '|| tablespace_name || ' force logging;' from dba_tablespaces where contents = 'PERMANENT'; Cut/paste output into your sqlplus window.

28. Init.ora and listener.ora parms for DG/AV compatibility Init.ora dispatchers='(DISPATCHERS=2)(PROTOCOL=TCP)(SERVICE=${ORACLE_SID}XDB)(LISTENER=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<YOUR HOST NAME>)(PORT=1521))))‘ Listener.ora LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1)) (ADDRESS = (PROTOCOL = TCP)(HOST = <YOUR HOST NAME>) (PORT = 1521)) ) (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = <YOUR HOST NAME> )(PORT = 5707)) (Presentation=HTTP)(Session=RAW) ) ) SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /opt/app/oracle/product/10.2.3.1/avserver) (PROGRAM = extproc) ) (SID_DESC = (SID_NAME = <YOUR DBNAME>) (ORACLE_HOME = /opt/app/oracle/product/10.2.3.1/avserver) (global_dbname = <sid>.<domain> ) ) )

29. General database cleanup • Move datafiles, controlfile, online redo to better locations • Multiplex online redo and controlfiles across controllers • Increase the number of redolog groups • Appropriately size your SGA for your server • Setup log_archive_dest_1 to use something other than the AV install default • Setup log_archive_dest_2 to point to your standby database server • Setup log_archive_config, db_unique_name, fal_* entries and local_listener to use your database listeners in preparation for implenting Dataguard. • Move the flashback directory from the default of $ORACLE_BASE/flash_recovery_area to a better location and clean up the archivelogs backed up via rman to the old flash_recovery_area directory • Decide whether or not you want auto-extensible data files • Set whatever other init.ora parameters you like at your organization • Install backups / crontab / scripts / monitors to your company standard

30. Setting up the DG Standby and FSFO • Validate that Audit Vault works on the standby AV Server by logging into the application and “looking around” • Shutdown the Audit Vault server application • Delete the database from the standby machine • Bring over the init.ora and listener.ora modifications in Slide #15 to the standby, but change the machine name to that of the standby server. • Bring over the password file from the primary. • Restore a backup of your AV primary to your standby server and create a standby controlfile for it. • startup managed recovery • Implement FSFO • Validate that FSFO is working and the AV Web Application is working • Turn Database Vault back on • Troubleshoot in-house scripts that break as a result of Database Vault being turned back on

31. Other Dataguard / FSFO Considerations • If you use an XML audit trail, you may want to move your audit directories to faster files systems • If you use a DB audit trail, you’ll want to move your aud$ and fga_log$ tables to a non-system tablespace. • If you customize your sqlnet.ora NAMES.DEFAULT_DOMAIN, you’re going to have to manually modify every entry in the Audit Vault tnsnames.ora to include the value. You’ll also have to modify the tns configuration on the collector machines (whether they be source db servers or collector machines similar to slide #12).

32. Definitions and Context • Source – The database you are getting your audit data from. Regardless of how many nodes there are in your dataguard config, there is only 1 source. • Agent – Tied to a single server, an Agent connects to the Audit Vault Server to insert the audit trail data into the database. It “manages” the collectors. • Collector – The RDBMS specific process that knows how to get audit data from the source database. There are collectors that talk to Oracle, MS Sql, DB2, and Sybase. Multiple collectors can use the same agent to deposit all audit data into the same Audit Vault repository. • A collector is tied to a source; it “collects” from that source. • In an Audit Vault, the combination of Source and Collector is unique.

33. Setting up remote XML collection • Get local collection working on the source database server following the Audit Vault documentation. • Using avca on the AV Server, add a new agent mapped to the primary collector server(s). • Run the OUI to install the Audit Vault Agent software on each primary remote collector providing the new agent created in Step #2 to the installation dialog. • Using avorcldb on the AV Server, add a new source using the “flip-tolerant” host name. • Using avorcldb on the AV Server, add new collectors for the source created in #4 tied to the agents created in #3. • Using avorcldb on the remote collector server, run setup to create the wallet and tnsnames entries for passwordless connection from the primary remote collector to the source db. • Modify the source db tnsnames.ora entry created in #7 to change the source db entry from the “flip-tolerant” host name to the node specific host name. • If audit_trail = xml*, create identical audit trail directories on the remote collector. • If doing XML generation, sync the audit trail directories created in Step #6 between the source db server and the remote collector, and create job to sync them regularly. • Stop the collectors created in Step #1, and startup the newly modified collector and validate that it is collecting the sync’d files.

34. New Agent Mapping

35. Source Collector Map

36. Conclusion • In a world of compliance auditing, life can be easy or it can be hard • Audit data is just as important as production data and should be treated as such • In some ways, the stakes are higher: If we mess up, market cap plummets, companies fail and people go to jail. • How Big a Gambler are YOU? • Oracle Audit Vault with Dataguard/FSFO and remote collection is a high performance, low impact, highly available solution that makes compliance reporting easy.

37. Best Practices

38. What Do You Need To Audit? 38

39. Native Auditing Performance Guidelines • Original workload CPU 50% for 250 audit records/sec *Internal testing: Source: 4x 3.40 GHz Intel Xeons , 4 GB RAM, x86_64 Linux Oracle Database 11.2.0.1 Oracle Confidential 39

40. Use Automatic Audit Trail Clean-Up • Automatically deletes audit trails from target after they are securely inserted into Audit Vault • Reduces DBA manageability challenges with audit trails Database 1) Transfer audit trail data 2) Update last inserted record 3) Delete older audit records Oracle Confidential 40

41. Oracle Database Security Defense-in-Depth Encryption and Masking • Oracle Advanced Security • Oracle Secure Backup • Oracle Data Masking Access Control • Oracle Database Vault • Oracle Label Security Auditing and Tracking • Oracle Audit Vault • Oracle Configuration Management • Oracle Total Recall Blocking and Monitoring • Oracle Database Firewall

42. More Oracle Database Security Presentations • Monday: • 12:30 pm: Making a Business Case for Information Security MS 300 • 3:30 pm: Oracle Database 11g Release 2 Security: Defense-in-Depth MS 103 • Tuesday: • 12:30 pm: Real-World Deployment and Best Practices : Oracle Audit Vault MS 306 • 2:00 pm: Real-World Deployment and Best Practices : Oracle Advanced Security MS 300 • 2:00 pm: Best Practices for Ensuring the Highest Enterprise Database Security MS 304 • 3:30 pm: Database Security Event Management : Oracle Audit Vault and ArcSight MS 300 • 5:00 pm: Real-World Deployment and Best Practices :Oracle Database Vault MS 303 • Wednesday: • 10:00 am: Protect Data and Save Money: Aberdeen MS 306 • 11:30 am: Preventing Database Attacks With Oracle Database Firewall MS 306 • 4:45 pm: Centralized Key Management and Performance :Oracle Advanced Security MS 306 • Thursday: • 10:30 am: Deploying Oracle Database 11g Securely on Oracle Solaris MS 104 MS = Moscone South

43. Oracle Database Security Hands-on-Labs • Monday: • Database Vault 11:00AM | Marriott Marquis, Salon 10 / 11        Check Availability  • Database Vault 5:00PM | Marriott Marquis, Salon 10 / 11        Check Availability • Tuesday: • Database Security 11:00AM | Marriott Marquis, Salon 10 / 11     Check Availability • Thursday • Advanced Security 12:00PM | Marriott Marquis, Salon 10 / 11    Check Availability • Audit Vault 1:30PM | Marriott Marquis, Salon 10 / 11       Check Availability

44. Oracle Database Security Demo GroundsMoscone West • Oracle Database Firewall • Oracle Database Vault • Oracle Label Security • Oracle Audit Vault • Oracle Advanced Security • Oracle Database 11g Release2 Security

45. Oracle OpenWorldLatin America 2010 December 7–9, 2010

46. Oracle OpenWorldBeijing 2010 December 13–16, 2010

47. Oracle Products Available Online Oracle Store Buy Oracle license and support online today atoracle.com/store