Browser unable to execute script; please use the site map to navigate the site.

Determining Trigger Involvement During Forensic Attribution in Databases

Hauger and Olivier


(Citation)Citation information

W. Hauger and M. S. Olivier. “Determining Trigger Involvement During Forensic Attribution in Databases”. In: Advances in Digital Forensics XI. Ed. by G. Peterson and S. Shenoi. Vol. 462. IFIP Advances in Information and Communication Technology. Springer, 2015, pp. 163–177


Researchers have shown that database triggers can interfere with the attribution process in forensic investigations. Triggers can perform actions of commission and omission under the auspices of users without them being aware of the actions. This could lead to the actions being wrongly attributed to the users during forensic investigations. This chapter describes a technique for dealing with triggers during forensic investigations of databases. An algorithm is proposed that provides a simple test to determine if triggers played any part in the generation or manipulation of data in a specific database object. If the test result is positive, a forensic investigator must consider the actions performed by the implicated triggers. The algorithm is formulated generically to enable it to be applied to any relational SQL database that implements triggers. The algorithm provides forensic investigators with a quick and automated means for identifying the potentially relevant triggers for database objects, helping to increase the reliability of the forensic attribution process.

(Authoritative version on publisher's site)Definitive version

The definitive version of the paper is available from the publisher.
DOI: 10.1007/978-3-319-24123-4_10

(BibTeX record)BibTeX reference

author={Werner Hauger and Martin S Olivier},
title={Determining Trigger Involvement During Forensic Attribution in Databases},
booktitle={Advances in Digital Forensics XI},
editor={Gilbert Peterson and Sujeet Shenoi},
series={IFIP Advances in Information and Communication Technology},
volume={462} )