企业数据审计 [英] Enterprise Data Auditing

问题描述

我们目前的企业解决方案是由实体框架驱动的ASP.NET MVC应用程序。有几个关于如何挂钩到审计变更事件的链接。我对此并不感兴趣

Our current enterprise solution is a ASP.NET MVC application driven by the Entity Framework. There are a couple links on how to hook into the change events for auditing. I'm not really interested in this.

我对企业级审计架构感兴趣。那些与企业级战斗伤口的人，你的审计方案是什么？您是否在框架中的数据库中序列化对象。您是否设置数据库触发器来审核表？您是否一起使用单独的数据库，以便您的审计增长不会影响您的应用程序数据库？我对这里的尝试和真实的解决方案感兴趣。我知道我们的技术选择（EF）有选择，但我对该基金会感兴趣。

I'm interested in enterprise level auditing architecture. Those of you with the enterprise level battle wounds, what has been your auditing solutions? Do you serialize objects in databases in a framework. Are you setting up database triggers to audit tables? Do you use a separate database all together so your audit growth doesn't affect your app database? I'm interested in the tried and true solutions here. I know there's options in our technology choice (EF) but I'm interested in the foundation first.

链接将不胜感激。

推荐答案

几个解决方案，但我最喜欢的一个是简单本身：

I've seen several solutions, but my favorite one was simplicity itself:

• 创建镜像每个源表的审计表，添加一些额外的列跟踪更改的日期和类型（插入，更新或删除，如果您支持）和用户进行更改。删除所有约束和索引（除非你期望做大量的搜索）。

• Create audit tables that mirror each source table, adding a few extra columns to track the date and type of change (insert, update, or delete if you support it) and the user making the change. Remove all constraints and indexes (unless you expect to be doing a lot of searches).

在表内更新逻辑（我们使用过程，但没有原因在给定适当的钩子的情况下，OR / M或其他持久层无法完成），请写入源表和审核表。

Inside of the table update logic (we used procedures, but there's no reason it couldn't be done with an OR/M or other persistence layer, given the appropriate hooks), write to both the source table and the audit table.

这有很多好处，但最大的一个（在我看来）并不需要担心或编写所有代码来管理客户端中配对写入操作的事务完整性。

This has numerous benefits, but the biggest one (in my opinion) is not having to worry about or write all the code to manage the transactional integrity of the paired write operations in the client.

这篇关于企业数据审计的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！