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

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
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-2013-5704
Published: 2014-04-15
The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."

CVE-2013-5705
Published: 2014-04-15
apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header.

CVE-2014-0341
Published: 2014-04-15
Multiple cross-site scripting (XSS) vulnerabilities in PivotX before 2.3.9 allow remote authenticated users to inject arbitrary web script or HTML via the title field to (1) templates_internal/pages.tpl, (2) templates_internal/home.tpl, or (3) templates_internal/entries.tpl; (4) an event field to ob...

CVE-2014-0342
Published: 2014-04-15
Multiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors.

CVE-2014-0348
Published: 2014-04-15
The Artiva Agency Single Sign-On (SSO) implementation in Artiva Workstation 1.3.x before 1.3.9, Artiva Rm 3.1 MR7, Artiva Healthcare 5.2 MR5, and Artiva Architect 3.2 MR5, when the domain-name option is enabled, allows remote attackers to login to arbitrary domain accounts by using the corresponding...

Best of the Web