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

11/30/2011
02:44 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

DAM Is Morphing

DAM may not be DAM much longer.

The database activity monitoring (DAM) market has changed over the last 18 months, specifically in the ways DAM is augmenting base functionality to solve a broader range of security threats.

The changes include both the incorporation of existing security technologies into DAM platforms along with the seamless linking of other -- external -- security services. This deserves mention both because the integration is tighter than we have seen with other security products like IDS or SIEM, and because the DAM vendors are coupling technologies to fit different visions of how customers want to manage security and compliance.

Why is this important? DAM may not be DAM much longer. It's morphing into something -- maybe more than one thing -- entirely different.

Here I am going to describe one such adaptation of DAM, one of four trends that I have been monitoring. I'll go over the others in subsequent posts.

The first trend I see is the applying DAM features generically to many back-office applications. Data operations -- such as a a file read, MS Sharepoint request or SAP transaction -- are treated just like a database query. The structure of the user request is different but DAM parses each request for critical attributes and make sure the call complies with security policies. As before, if the analysis shows a rule was violated, a security response is triggered.

The beauty of this adaptation from the user perspective is that the deployment model is unchanged. Events are collected through same basic OS layer agents as before, and sent to a central server for analysis and storage. The agents are modified to collect and understand many different types of application events, and the policy management engine is tweaked to accommodate non-database rules.

Note that DAM does more than alerting and blocking -- it will also leverage masking, encryption and labeling technologies to address security and compliance requirements. This model relies heavily on discovery to help administrators locate data and define usage policies in advance.

You'll notice there is a little overlap with SIEM, but the types of events being monitored are much more focused on the application layer, and the responses are intended to be real time. There is also some overlap with DLP, but DAM approach lacks the endpoint capabilities and full content awareness.

To be honest, I don't know what to call this yet. It's application monitoring, but focused on data usage. The architecture is one that mimics the business processing systems, acting as underlying sensors for each data exchange. For now, I am describing this as an "Business Activity Monitoring," for lack of a better term. I am sure this name will change several times during the course of the research project and as I delve into the other models in more detail.

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

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Cybersecurity Team Holiday Guide: 2019 Gag Gift Edition
Ericka Chickowski, Contributing Writer,  12/2/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19647
PUBLISHED: 2019-12-09
radare2 through 4.0.0 lacks validation of the content variable in the function r_asm_pseudo_incbin at libr/asm/asm.c, ultimately leading to an arbitrary write. This allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via crafted input.
CVE-2019-19648
PUBLISHED: 2019-12-09
In the macho_parse_file functionality in macho/macho.c of YARA 3.11.0, command_size may be inconsistent with the real size. A specially crafted MachO file can cause an out-of-bounds memory access, resulting in Denial of Service (application crash) or potential code execution.
CVE-2019-19642
PUBLISHED: 2019-12-08
On SuperMicro X8STi-F motherboards with IPMI firmware 2.06 and BIOS 02.68, the Virtual Media feature allows OS Command Injection by authenticated attackers who can send HTTP requests to the IPMI IP address. This requires a POST to /rpc/setvmdrive.asp with shell metacharacters in ShareHost or ShareNa...
CVE-2019-19637
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is an integer overflow in the function sixel_decode_raw_impl at fromsixel.c.
CVE-2019-19638
PUBLISHED: 2019-12-08
An issue was discovered in libsixel 1.8.2. There is a heap-based buffer overflow in the function load_pnm at frompnm.c, due to an integer overflow.