|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:43 AM
Points: 582,
Visits: 1,601
|
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Monday, December 14, 2009 10:16 AM
Points: 20,
Visits: 3
|
|
| That is nice and robust solution! But since triggers can be disabled by privileged users, this won't work for internal access violation...
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 12:43 AM
Points: 582,
Visits: 1,601
|
|
I understand your point, but I would suggest that you could say the same about the data in the target audit tables. i.e. a privileged user would be able to delete / update data.
Whatever solution you use for auditing, you'll have to ensure that appropriate permissions are granted to make sure that the neither the auditing mechanism nor the audited data itself is tampered with.
|
|
|
|