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/7/2011
11:59 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

ADMP: DAM For Web Apps

A look at the technology that combines application and database protection

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. 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 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
New 'Nanodegree' Program Provides Hands-On Cybersecurity Training
Nicole Ferraro, Contributing Writer,  8/3/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15820
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, the markdown parser could disclose hidden file existence.
CVE-2020-15821
PUBLISHED: 2020-08-08
In JetBrains YouTrack before 2020.2.6881, a user without permission is able to create an article draft.
CVE-2020-15823
PUBLISHED: 2020-08-08
JetBrains YouTrack before 2020.2.8873 is vulnerable to SSRF in the Workflow component.
CVE-2020-15824
PUBLISHED: 2020-08-08
In JetBrains Kotlin before 1.4.0, there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.
CVE-2020-15825
PUBLISHED: 2020-08-08
In JetBrains TeamCity before 2020.1, users with the Modify Group permission can elevate other users' privileges.