Welcome Guest. | Log In | Register | Membership Benefits


Topics:   Database Security Tech Center : Security Views

ADMP: DAM For Web Apps

A look at the technology that combines application and database protection

Dec 07, 2011 | 11:59 AM | 

By Adrian Lane
Dark Reading

Continuing the "DAM is morphing" thread, I am going to describe the ADMP variation -- or Application & Database Monitoring & Protection. As the name implies, ADMP couples application monitoring with database monitoring to provide more thorough analysis prior to real-time alerting, taking corrective action, or blocking transactions.

For those of you who follow my posts, you know I have talked about this before. I've described ADMP as "The Web AppSec" variation of database monitoring because it links DAM to Web application firewalls to provide activity monitoring and enforcement. And this make sense: databases don't just support Web applications -- they are Web applications.

In the ADMP model, DAM protects content in a structured application and database stack, and WAF shields application functions from misuse and injection attacks. The original synergy between these two platforms was the ability to de-alias user activity at the application layer (i.e., identify the user of the application) and share that information at the database layer to get a better idea if the user request was legitimate. As applications connect to databases with a generic account, DAM could not attribute SQL queries to specific users, limiting effectiveness. When ADMP was originally sketched out four years ago to predict where the DAM market would head, we focused on two areas of development. The first was business transaction validation, which was accomplished by anti-exploitation, transaction authentication, and adaptive authentication capabilities. The second was validating the right applications were communicating with each other; this was accomplished through session security and application access control (i.e., "NAC" at the application layer).

Remember, four years ago we were focused on virtualization, but this capability is even more pressing with cloud computing. What we have witnessed is coverage for a wider variety of applications and the "hooks" required to analyze business operations. Authentication of users and services is included, but implemented as a passive reporting feature instead of active validation and blocking. We did not witness application authentication or session validation capabilities predicted.

One surprise is the ADMP model has evolved to include File Activity Monitoring (FAM), which protects data as it moves in and out of documents or unstructured repositories. Yes, this means unstructured databases can be monitored, but the feature is especially helpful in protecting back-end applications that are leaking data or Web application servers from unwanted file substitutions.

The benefit of ADMP over the other evolutionary models of DAM is better application awareness. While the Business Activity Model I referenced in my last post is geared toward protecting data before it is read, this model is better at protecting the application infrastructure while reducing false-positives through transactional awareness. The ADMP model also provides advanced detection of Web-borne threats in a way that makes it unique among its peers. Since the majority of applications are designed to serve content over the Web, this provides the broadest application of the technology. Granted, the user will need to spend more time on set-up and policy creation, but that's the trade-off.

Next up I will talk about policy-driven monitoring hierarchy and how DAM fits within that model.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports