What security events conduct one audit for a business application?

Question

I already check the success of authorization, failure and logout.

I reviewed the audit (logging) of each method call and saved a version of each row and column that has ever been modified, but both of these options significantly increase the complexity of the audit. Auditing a random subset is too random.

Legal specifications (FISMA, C & A) just say that something needs to be checked.

Are there any other non-domain audit strategies that I forget?

Answer 1

, , , , -/- ..

, . " " .

- , , ... , , .... , , , , .

, -, , . ( ).

. - , , , " 2938". , , . , , - , "Dave deleted..." - , -

.

Answer 2

, , , . sql, ( , SQL Server). , , , . (dba backup) prod, , , , , . . , dbas , , - , .

, . , . , , . , , , - , .

, , , , .