All geek questions in one place

Linq to SQL Audit Trail / Audit Log: should I use triggers or doddleaudit?

I am working on a business application that requires verification of all database transactions (mainly for legal purposes).

I went through the website and came across DoddleAudit ( http://www.codeplex.com/DoddleAudit ), which basically adds the ability to track Linq to SQL changes. Similar to how people use interceptors in sleep mode.

What bothers me is the reliability issue. Although the audit log at the ORM level can record everything that happens with the code, it will not record any changes if it says that someone manually issues an SQL statement to a database or hacker, etc. Basically the information I'm dealing with is a little sensitive. This is what makes me think that triggers are probably the most reliable way. (?)

Other logging methods can be done through code or through stored procedures that seem a bit hacked and unreliable. Therefore, I basically cannot use triggers or something like DoddleAudit.

I was hoping to get some opinions, but before choosing.

+3
source share
2 answers

If the audit is for legal purposes, you need to do this using a certified compliance methodology. Such methodologies are very specific for addressing specific threats through auditing. You need to read the Database Engine and, most likely, turn to a specialist who can give you guidance on the various legal frameworks that surround data audits specific to your location and domain.

SQL Server C2, . c2 Option, . Linq2sql , , ( ).

+3

Source: https://habr.com/ru/post/1729991/

More articles:


All Articles