Informatica

[pic] | |
|[pic] |  |  |[pic] |
|  |  | | |
| |[pic] | | |
| |  | ||
| |Auditing and reporting Oracle user activity | | |
| |Oracle Tips by Burleson Consulting | | || | | | |
| | | | |
||Feb 9, 2004 | | |
| |Changes in U.S. federal laws have mandated increased security for auditing Oracle user activity. HIPAA, the Sarbanes-Oxley Act, | | |
||and the Gramm-Leach-Bliley Act have all produced serious constraints on Oracle professionals who are now required to produce | | |
| |detailed audit information for Oracle system users. | | |
||Starting with Oracle8i, Oracle introduced special triggers that are not associated with specific DML events (e.g., INSERT, | | |
| |UPDATE, and DELETE). These system-level triggers included database startup triggers, DDL triggers, and end-user login/logoff | | |
||triggers. | | |
| | | | |
||While Oracle provided the functionality for these new triggers, it was not clear how they could be used in order to track | | |
| |system-wide usage. This article describes my work in creating end-user login/logoff procedures to facilitate tracking end-user | | |
||activity. Please be advised that the initial implementation of system-level triggers for end-user tracking is quite new and, as | | |
| |such, is still a bit lacking in robust functionality. | | |
| |...