Happy (Audit) Trails to Oracle E-records Management
Mandated compliance with various regulations has placed an emphasis on data protection, retention, and security lately. This guide gets past the legalese and tackles electronic records management in Oracle using audit trails.
by Shirish Joshi
August 9, 2004
lthough electronic records have been around since the first databases, regulations about how to manage them are coming onto the scene only now. Legislation such as the Sarbanes-Oxley Act and HIPAA (Health Insurance Portability and Accountability) set standards for access, security of records, retention, and replacement of paper-based records.
This article discusses the management of electronic records in Oracle using audit trails, mechanisms for preventing previously stored information from being altered or corrupted. An audit trail is a time-stamped record of the changes that users make to a record. It contains the name/identification of the user who performed the modification and typically also includes the reason for the change. An audit trail enables you to audit the system for a record of alterations, as well as to reconstruct the data at a specified point in time.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
lthough electronic records have been around since the first databases, regulations about how to manage them are coming onto the scene only now. Legislation such as the Sarbanes-Oxley Act and HIPAA (Health Insurance Portability and Accountability) set standards for access, security of records, retention, and replacement of paper-based records.
