| 2 Minute Drill for Setting up Oracle DB Auditing |
|
|
|
| Written by RD | ||||||
| Sunday, 09 December 2007 | ||||||
|
This is for someone who is PSADMIN and not expert in Oracle DB Security setups and wants to enable quick and safe, especially when the SOX auditor is asking you to enable it. And also this is specific for PeopleSoft Application DBs. Init.ora: Tables sys.aud$ and dba_audit_trail should return no rows. If there are any rows, you want to clean them up before you turn on auditing. Else run this script, as SYS internal, $ORACLE_HOME/rdbms/admin/cataudit.sql For audit_trial=OS: If you want to have the audit to OS level file, it should be audit_trial=OS Make sure to change the location where the file should be written, with the parameter AUDIT_FILE_DEST, if you don’t want it to write in $ORACLE_HOME/rdbms/audit location. For audit_trial =DB: Check if any audit option is enabled with the query, select * from DBA_STMT_AUDIT_OPTS. It should not return any rows, before the start of audit. For PeopleSoft, SYSADM the following should be enough, unless you want to add more or your SOX auditor wants you to add anything specific: In one command: audit all by sysadm by access; or if you want to do one by one and you can keep or remove anything from the list. audit UPDATE ANY TABLE by sysadm by access; CAUTION: DONOT enable audit by session, unless you are sure that you want to.
noaudit ALL by sysadm; or just copy and paste the following in SQL prompt.
To ensure that nothing is being audited, check DBA_STMT_AUDIT_OPTS if there are any rows returned. If any run noaudit command for those things. More to come.. Well, don’t forget to archive the entries frequently or delete them once the report is taken to avoid unwanted data in the DB. Also make sure that the SYSTEM tablespace or the tablespace where the sys.aud$ table is assigned and the default storage for the table sys.aud$ , DOES NOT HAVE PCTINCREASE as 50%. The default storage for system tablespace is 50% and remember to change it to 0% else, you will run into trouble when the table size grows, especially if there are any brutal attacks on your system. If you want to get into details of auditing, you should consider Oracle Audit Vault, especially you have many production instances to manage and managing then would be easier with OAV. Add as favourites (47) | Quote this article on your site | Views: 12055 | Print
Write Comment
Copy Right: AKOComments v.1.4.6 |
||||||
| Last Updated ( Wednesday, 27 February 2008 ) | ||||||
| < Prev |
|---|












