Perimeter
2/24/2011
05:44 PM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

DAM Market Observation

Despite talk about the lack of innovation in the data security market, excellent technologies like DAM and DLP have been available for years before customers embraced them

A thought hit me this week that is worth mentioning in regard to database security. This is the first time in my 10 years working with database activity monitoring (DAM) technologies that it was the principal driver in several proof-of-concept engagements. The RSA Security Conference for 2011 concluded last week, during which I heard from multiple vendors and customers that DAM was the specified technology need, fulfilling the bulk of the requirements.

I have been working with DAM technology since 2000, writing my own ad-hoc tools to do basic misuse detection. That was a couple of years before there even was a DAM market. At the time it was considered a strange offshoot of intrusion detection systems. Even in 2002, when a handful of vendors popped on the scene, sales were few and far between.

Now the DAM market is well more than $100 million and growing, but this is the first time I have seen DAM repeatedly the buyer's focus. Sales were not because SIEM customers needed better application layer detection. Not because customers wanted a detective control to complement a vulnerability assessment product. Not because they wanted to buttress their Web application firewall product for better protection against SQL Injection. Not because it helped performance and operations management task. These customers had specific data and database security challenges that were only addressed with DAM.

I think this is newsworthy for a very specific reason: It has taken a decade before mainstream IT has embraced database monitoring. There is a lot of talk about the lack of innovation in the data security market. However, there have been excellent technologies, like DAM and DLP, available for years, but it has taken the better part of the past decade before customers were even aware of these technologies and understood the benefits to data security. Compliance, database security, and database operations management all benefit. The platforms are fully mature. Firms like IBM, Fortinet, and Oracle jumped in with both feet, making investments in Guardium, IPLocks, and Secerno, respectively. Maybe it has taken those big firms to get the word out, or maybe it has taken a while for IT to understand perimeter and network security tools are not solving security problems. But it does look like Joel Spolsky was right: it takes ten years.

Either way, focusing more at the data layer is a good thing.

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
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-0460
Published: 2014-04-16
The init script in kbd, possibly 1.14.1 and earlier, allows local users to overwrite arbitrary files via a symlink attack on /dev/shm/defkeymap.map.

CVE-2011-0993
Published: 2014-04-16
SUSE Lifecycle Management Server before 1.1 uses world readable postgres credentials, which allows local users to obtain sensitive information via unspecified vectors.

CVE-2011-3180
Published: 2014-04-16
kiwi before 4.98.08, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands via shell metacharacters in the path of an overlay file, related to chown.

CVE-2011-4089
Published: 2014-04-16
The bzexe command in bzip2 1.0.5 and earlier generates compressed executables that do not properly handle temporary files during extraction, which allows local users to execute arbitrary code by precreating a temporary directory.

CVE-2011-4192
Published: 2014-04-16
kiwi before 4.85.1, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands as demonstrated by "double quotes in kiwi_oemtitle of .profile."

Best of the Web