Database forensics: Difference between revisions

Revision as of 18:31, 13 June 2014

Revision as of 21:12, 13 June 2014

Line 5:

The discipline is similar to [[computer forensics]], following the normal forensic process and applying investigative techniques to database contents and metadata. Cached information may also exist in a servers [[RAM]] requiring [[Digital forensics#live analysis|live analysis]] techniques.

A forensic examination of a database may relate to the timestamps that apply to the update time of a row in a relational table being inspected and tested for validity in order to verify the actions of a database user. Alternatively, a forensic examination may focus on identifying transactions within a database system or application that indicate evidence of wrongdoing, such as fraud.

Software tools such as ACL, [http://www.arbutussoftware.com Arbutus Analyzer] and Idea (which provide a read-only environment) can be used to manipulate and analyse data. These tools also provide audit logging capabilities which provide documented proof of what tasks or analysis a forensic examiner performed on the database.

Currently many database software tools are in general not reliable and precise enough to be used for forensic work as demonstrated in the first paper published on database forensics.<ref>[http://www.giac.org/certified_professionals/practicals/gcfa/0159.php Oracle Database Forensics using LogMiner - GIAC Certified Student Practical<!-- Bot generated title -->]</ref>

Line 25:

* Oracle Forensics, Paul Wright, Rampant Techpress, ISBN 0-9776715-2-6, May 2008. http://www.rampant-books.com/book_2007_1_oracle_forensics.htm

== References ==

{{Reflist}}