Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Perimeter

12/22/2011
10:28 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Database Security Proxies

Using DAM as a security proxy

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 proxy model works is by intercepting inbound queries and after analysis, reacting with different technologies. One major feature is DAM recognizes incoming queries and provides the result directly to the user without passing the query to the database. The proxy system works as a database cache, lowering the resource demand on the database and improving query response times.

Another key feature is the proxy will protect sensitive information through masking or query re-writing. Depending upon the query, the data requested and the user credentials, the proxy will automatically alter the results a user would normally receive by either rewriting the query to omit sensitive data, or dynamically altering the result set. This masking model helps protect sensitive information without altering the database or encumbering it with overhead of data substitution. Finally, the proxy model of DAM acts as a firewall to protect the database from known attack signatures. Often called virtual patching, this feature protects the database from attacks and gives the database administrators some leeway as to when they apply security patches.

The downside of this deployment option is it's a one-to-one model, meaning one proxy serves one database. There are ways to minimize this, but at it's heart, the proxy is part of the database. Most DAM products offer a hierarchical deployment with end-point collectors to serve dozens -- if not hundreds -- of databases. Further, the proxy needs careful administration to ensure that the masks, caching, and attack signatures are working properly and do not interfering with normal business operations.

Finally, the implementations of this model are harder to use for compliance management. This is both for scaling policies across and organization, as well as full lifecycle integration with assessment, discovery, patch management, and protection. Some of the capabilities are present, but it's not as evolved as the other platforms.

With all of the DAM models I've discussed in this series, none are without concerns and side effects. Every option has detractors. The good news is between the four variations, there is likely a model that matches your security and/or operations model, making the system -- as a whole -- a better fit for your organization. And as I talk to a dozen large firms every month, I know every IT organization has their own peculiar way of doing things, and that's just the way it is.

It will take some time for you to understand DAM vendors' vision of security and compliance to see if it's in line with your IT operations model. You're not going to figure that out with your standard set of RFP/RFI questions, so start asking better questions that take into account your organizational oddities.

I want to make some final comments on this series as well. As DAM is morphing beyond databases and encompasses data and application security, what we ultimately call this/these new products is still up for debate. Unlike antivirus, which is a single-use tool, DAM is spreading across organizations for multiple applications and use cases. The commonality between the models discussed in this series is DAM is the cornerstone, and each model possesses and architecture capable of extending well beyond databases. The existing architecture readily accepts new capabilities (file activity monitoring is an example) and can handle a much broader array of security, compliance, and operations challenges than the original platform focus. It will be exciting to watch as customer choose which best fits their needs.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/2/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9498
PUBLISHED: 2020-07-02
Apache Guacamole 1.1.0 and older may mishandle pointers involved inprocessing data received via RDP static virtual channels. If a userconnects to a malicious or compromised RDP server, a series ofspecially-crafted PDUs could result in memory corruption, possiblyallowing arbitrary code to be executed...
CVE-2020-3282
PUBLISHED: 2020-07-02
A vulnerability in the web-based management interface of Cisco Unified Communications Manager, Cisco Unified Communications Manager Session Management Edition, Cisco Unified Communications Manager IM & Presence Service, and Cisco Unity Connection could allow an unauthenticated, remote attack...
CVE-2020-5909
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, when users run the command displayed in NGINX Controller user interface (UI) to fetch the agent installer, the server TLS certificate is not verified.
CVE-2020-5910
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection would be authorized.
CVE-2020-5911
PUBLISHED: 2020-07-02
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.