SQL Server Audit (Audit)--Auditing and application design Architecture
Auditing is the monitoring log on the database server, paired with the design architecture of the application, such as client-server architecture (Client-server), multi-layered architecture (multi-tier), and so on. Although you can use audit to record the IP address of which work host the login account is from, it is more appropriate for the client-server architecture environment.
650) this.width=650; "title=" clip_image001 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "alt=" clip_image001 "src=" http://s3.51cto.com/wyfs02/M00/57/77/wKioL1Sbb77i767DAACV7TLCK0I964.jpg "border=" 0 "height=" 337 "/>
"Client-server architecture" can log IP addresses to individual client hosts
650) this.width=650; "title=" clip_image002 "style=" Border-top:0px;border-right:0px;border-bottom:0px;border-left : 0px; "alt=" clip_image002 "src=" http://s3.51cto.com/wyfs02/M01/57/77/wKioL1Sbb7-DBPeFAADMiqAS4qk433.jpg "border=" 0 "height=" 332 "/>
"Multi-layered architecture" logging to webserver IP address
Therefore, in a multi-layered architecture, if you need to perform a security audit on the client, you may need to take advantage of the front-end application to store data such as the IP address of the client host in the database.
In front-end application design, has its user account and Rights Management mechanism, generally assign database-level read and Write permissions, with a single SQL Server login account mode, access to the database server. Such a design architecture creates a blind spot for "auditing" on recorded data, because "audit" can be logged to the login account or the IP address of the client host, but it is not possible to know who is executing the application.
L Basically, a security monitoring tool that is set up on a database system may have the aforementioned blind spot, and there is no way of knowing which client has accessed the specified object.
In view of the application architecture described above, if you need to record which user is accessing the data table, you should design the appropriate recording method within the front-end application itself.
This article is from the SQL Server deep dives blog, so be sure to keep this source http://ultrasql.blog.51cto.com/9591438/1595730
SQL Server Audit (Audit)--Auditing and application design architecture