Manish Bhagwani, Arpana Rawal, Jyoti Singh
email@example.com , firstname.lastname@example.org , email@example.com
Manish Bhagwani1, Dr. Arpana Rawal2, Dr. Jyoti Singh3
1Research Scholar, Bhilai Institute of Technology, Durg (CG), India.
2Professor, Bhilai Institute of Technology, Durg (CG), India.
3Joint Controller, CGVYAPAM, Raipur (CG), India.
Volume - 10,
Issue - 1,
Year - 2020
Majority of database breaches that include temporary data tampering, data copying, changing time stamps in log files, tampering data in database, done by intruders in various enterprise databases; both Government and commercial, have made it essential to apply diagnostic methods like auditing tools to identify the type, place and time of data corruption. These tools offer a lot of features that can provide data useful for database investigation. Moreover, auditing techniques can be applied to these databases to enable database forensic investigator to do the analysis and find the answers as to WHERE, WHEN and WHO corrupted the data. This kind of analyses has been done by various algorithms (Trivial, Monochromatic, RGB, Polychromatic, RGBY, Tiled Bitmap, a3D). These algorithms fail to detect temporary data corruption and un-authorized copying of data. This paper focuses on the study and analysis of techniques for making transaction logs, tracking the user activities and detecting transactions that copy data from tables, specially using SELECT operations.
Cite this article:
Manish Bhagwani, Arpana Rawal, Jyoti Singh. Implementing Auditing Techniques in Enterprise Databases. Int. J. Tech. 2020; 10(1):97-101. doi: 10.5958/2231-3915.2020.00019.X
Manish Bhagwani, Arpana Rawal, Jyoti Singh. Implementing Auditing Techniques in Enterprise Databases. Int. J. Tech. 2020; 10(1):97-101. doi: 10.5958/2231-3915.2020.00019.X Available on: https://www.ijtonline.com/AbstractView.aspx?PID=2020-10-1-19
1. The SQL Server“AUDIT (Traditional Auditing)”, https://docs. oracle.com/database/121/SQLRF/statements_4007.htm#S QLRF01107
2. “MySQL Enterprise Audit”, https://dev.mysql. com/doc/refman/8.0/en/audit-log.html
3. “Audit Trail in Access Forms in 6 Steps”, https://blueclawdatabase.com/access-forms-audit-trail“SQL Server Audit”, https://docs.microsoft.com /en- us/sql/relational-databases/security/auditing/sql-server- audit-database-engine?view=sql-server-ver15
4. “SQLite Triggers”, https://www.w3resource.com /sqlite/sqlite-triggers.php
5. Kyriacos Pavlou, Richard T. Snodgress, “Forensic Analysis of Database Tampering,” SIGMOD’06, pp: 109- 120, June 27-29, 2006.
6. Kyriacos Pavlou, Richard T. Snodgress, “Generalizing Database Forensics,” ACM Transaction on Database Forensics, pp. 1-60, June 2013.
7. David Litchfield, “Oracle forensics part 7 Using the oracle system change number in forensic investigations,” An NGSSoftware Insight Security Research (NISR) Publication, November 2008.
8. “Auditing SELECT statements on SQL Server”, https://solutioncenter.apexsql.com/auditing-select- statements-on-sql-server/
9. “SQL Server must generate Trace or Audit records when unsuccessful attempts to add privileges/permissions occur”, https://www. stigviewer.com/stig/ms_sql_server_2014_instance/2018- 09-18/finding/V-67923
10. Wagner J. at el. (2017), “Carving database storage to detect and trace security breaches,” Digital Investigation (Elsevier), Issue 22, pp. 127-136.