Perimeter
1/11/2011
08:57 PM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%

A Textbook Case For Monitoring

Vodafone's customer database leak demonstrates dangers of not properly monitoring database activity

A common problem with protecting sensitive database is limiting what data users see. An employee might be allowed to see any record in a database, but he is not allowed to see every record at the same point in time. For example, it's perfectly acceptable for customer service or a salesperson to view a customer record in service of that relationship. It's not OK that he be able to select the entire freakin' customer database.

But if the quotes from the management team are accurate, that's exactly what happened with the Vodafone data breach. And like many breaches, the company found out only when it was informed from someone outside the company.

The Vodafone case is a textbook example of why database activity monitoring (DAM) exists. One of the principle drivers behind monitoring software is to verify usage of systems or applications -- or conversely detect misuse. While this category of problem is commonly referred to as "the insider threat," that's really only a hyped subset of the specific operational problems being addressed. It's about protecting data while still performing the tasks the application was designed to perform. And this is most problematic with databases because the SQL query language is designed to return lots of information quickly and easily. Providing every row in the database except those filtered out by the "WHERE" clause is a core database feature. Validation of business and security rules is not.

Technologies like labeling can limit the rows within a table a single user is allowed to see, but it does not help limit the quantity of data extracted. Similarly, using an application or stored procedure to limit the amount of information a user can access at any one time can help, but most applications don't have this capability built in. Worse, they are expensive to retrofit and don't have the capabilities to track users over time. Perhaps most important, queries sent directly to the database bypass these controls. The point is there are several (kludgy) ways to accomplish the goal, but none is as easy or effective as DAM.

Every single DAM product on the market has policies to detect when a user selects "too many rows," or selects entire columns of sensitive information instead of a single row. Most have the capacity to track usage over time, so they build a profile of user activity and results and compare this with proper use models, alerting when there is a significant deviation from what is considered normal. At a minimum, someone runs "select * from customers" and security gets alerted. Some products will even block the query before the data is leaked. At the very minimum, even if you don't have a specific policy to protect data from the attack, you have an activity trail for forensic audits. This problem keeps popping up because most companies don't monitor or validate database usage.

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
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3861
Published: 2014-09-02
Cross-site scripting (XSS) vulnerability in CDA.xsl in HL7 C-CDA 1.1 and earlier allows remote attackers to inject arbitrary web script or HTML via a crafted reference element within a nonXMLBody element.

CVE-2014-3862
Published: 2014-09-02
CDA.xsl in HL7 C-CDA 1.1 and earlier allows remote attackers to discover potentially sensitive URLs via a crafted reference element that triggers creation of an IMG element with an arbitrary URL in its SRC attribute, leading to information disclosure in a Referer log.

CVE-2014-5076
Published: 2014-09-02
The La Banque Postale application before 3.2.6 for Android does not prevent the launching of an activity by a component of another application, which allows attackers to obtain sensitive cached banking information via crafted intents, as demonstrated by the drozer framework.

CVE-2014-5452
Published: 2014-09-02
CDA.xsl in HL7 C-CDA 1.1 and earlier does not anticipate the possibility of invalid C-CDA documents with crafted XML attributes, which allows remote attackers to conduct XSS attacks via a document containing a table that is improperly handled during unrestricted xsl:copy operations.

CVE-2014-6041
Published: 2014-09-02
The Android Browser application 4.2.1 on Android allows remote attackers to bypass the Same Origin Policy via a crafted attribute containing a \u0000 character, as demonstrated by an onclick="window.open('\u0000javascript: sequence.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.