Risk
12/18/2012
07:42 AM
Adrian Lane
Adrian Lane
Quick Hits
Connect Directly
RSS
E-Mail
50%
50%

A Guide To Practical Database Monitoring

A look at what database activity monitoring can and can't do, and some recommendations on how to implement the best system for your organization

[Excerpted from "A Guide to Practical Database Monitoring," a new, free report posted this week on Dark Reading's Database Security Tech Center.]

Database activity monitoring, a form of application monitoring, examines how applications use data and database resources to fulfill user requests. DAM captures and records database events -- which, at minimum, includes all SQL activity -- in real time or near real time.

DAM is focused on the database layer, which allows for a contextual understanding of transactions, or how multiple database operations constitute a specific business function.

If you want to understand when administrators perform unauthorized alterations or view sensitive information, or be altered when systems are used in a manner inconsistent with best practices, DAM is a good choice.

DAM can even detect odd behavior that is hard to quantify but just doesn't look right -- such as when someone requests "too much" information or makes unusual requests.

It's the understanding of the database layer that allows DAM to provide both qualitative and quantitative analysis of events across multiple requesting applications and databases. It's this focus that allows DAM to provide value beyond traditional security information and event management or intrusion-detection systems, both of which collect generic system and network events.

DAM systems have been commercially available for more than a decade, and the platforms offer mature functions that scale with the IT systems they monitor. Here are the principal reasons companies use DAM products:

SQL Injection protection. DAM can filter and protect against many variants of SQL injection. While it does not provide completeprevention, statement and behavioral analysis techniques catch a great deal of known and previously unknown attacks. By whitelisting queries as acceptable from specific applications, DAM can detect most queries that have been tampered with and queries originating from unapproved applications.

DAM also can be deployed to block SQL injection and other attacks -- called "virtual patching"-- often before database vendors provide patches. Statements can be blocked before executing in the database, so there is no damage to data or the platform.

Behavioral monitoring. DAM systems capture and record activity profiles, both of generic user accounts and of specific database users. Detected changes in a specific user's behavior can indicate a disgruntled employee, hijacked accounts or even cases of oversubscribed permissions. Or maybe you're worried about attacks from mysterious Russian hackers or the much-hyped "insider threat." Behavioral monitoring is an effective technique to detect misuse, regardless of the source.

For a look at some of the other reasons why companies use DAM -- as well as a detailed guide on how to evaluate DAM products -- download the free report on database activity monitoring.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. 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
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5619
Published: 2014-09-29
The Sleuth Kit (TSK) 4.0.1 does not properly handle "." (dotfile) file system entries in FAT file systems and other file systems for which . is not a reserved name, which allows local users to hide activities it more difficult to conduct forensics activities, as demonstrated by Flame.

CVE-2012-5621
Published: 2014-09-29
lib/engine/components/opal/opal-call.cpp in ekiga before 4.0.0 allows remote attackers to cause a denial of service (crash) via an OPAL connection with a party name that contains invalid UTF-8 strings.

CVE-2012-6107
Published: 2014-09-29
Apache Axis2/C does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.

CVE-2012-6110
Published: 2014-09-29
bcron-exec in bcron before 0.10 does not close file descriptors associated with temporary files when running a cron job, which allows local users to modify job files and send spam messages by accessing an open file descriptor.

CVE-2013-1874
Published: 2014-09-29
Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the current working directory.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.