The last database activity monitoring (DAM) model I want to address is the proxy model. This is the final installment of my trends series, following the business activity monitoring, ADMP and the policy driven security model.
With the proxy model, DAM sits in front of the databases and all database requests are routed through the proxy. This is a deployment model shared with the ADMP and business activity monitoring models, allowing the proxy to detect and block malicious queries. But where it gets interesting is the other ways the proxy alters database output and function: In essence, the proxy model adds database functionality by modifying the results in non-standard ways.

The link for this article located at Dark Reading is no longer available.