Perimeter
1/4/2011
05:12 PM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Going Out With A Bang

We like to think that most firms have 'gotten the memo' that hackers hack databases, yet the flurry of breaches at years end suggests otherwise

2010 ended with a slew of database breaches being reported. Mozilla's database for addons.mozilla.org was hacked, Ohio State University leaked 760,000 student and faculty social security numbers, St. Louis University reported a breach, and Silverpop leaked most of its clients' customer email addresses.

But in the greater scheme of things, these breaches will have the same financial impact as CitySights NY's leaking 110,000 credit card numbers.

CitySights NY had 110,000 credit card numbers, along with both personal information (name, address, email) and CVV2 data -- sometimes called the security code. Storage of the CCVV2 is expressly forbidden under these circumstances by the Payment Card Industry Data Security Standard. It stands to recon that if you have 110k credit card numbers, you might have heard of PCI-DSS, or have been flagged by a PCI assessor. Somehow CitySights NY got around this restriction.

Each one of these cases involves a database breach, caused by anything from SQL injection attack to simple user errors that expose data to anyone who happens to stumble upon it. It's easy to become desensitized reading about breaches given the frequency has barely slowed in the past five years. Most companies storing credit card numbers have received the memo that they need to take care of their data, but there are a lot that have lax security and are still storing portions of the mag stripe data that they should not. I find that universities remain defiant about data security, and most institutions I speak with have a cultural issues that run counter to data security. An open environment that promotes the free exchange of ideas is at odds with the need to lock down personal information. It's not that they can't -- it's just counter to their philosophy, and I believe why we will continue to see student data compromised for the foreseeable future.

Whatever the cause, we have technologies and processes to help mitigate breaches and make is far tougher for attackers to compromise a database. What's not always obvious is that a single account compromise or SQL injection attack should not automatically expose every data record, or all types of data. It does not need to be catastrophic and total failure.

Simple adjustments to permissions, segregation of admin roles, or patching more frequently don't cost money -- rather it's a change to the operations processes. What's more is these steps account for some of the biggest breaches. Labeling and masking technologies, commonly available from the database vendor at a small cost, can prevent leakage through mistakes and some forms of injection attacks. Transparent database encryption is, once again, inexpensive and effective with minimal disruption to operations. Finally, choosing to _not_ store some types of information is free and incredibly effective.

You don't need to do a lot to raise the bar, but you actually have to _do_ something. Outside of Mozilla, it does not look like any of these institutions had security in mind whatsoever.

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
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-3946
Published: 2014-04-24
Cisco IOS before 15.3(2)S allows remote attackers to bypass interface ACL restrictions in opportunistic circumstances by sending IPv6 packets in an unspecified scenario in which expected packet drops do not occur for "a small percentage" of the packets, aka Bug ID CSCty73682.

CVE-2012-5723
Published: 2014-04-24
Cisco ASR 1000 devices with software before 3.8S, when BDI routing is enabled, allow remote attackers to cause a denial of service (device reload) via crafted (1) broadcast or (2) multicast ICMP packets with fragmentation, aka Bug ID CSCub55948.

CVE-2013-6738
Published: 2014-04-24
Cross-site scripting (XSS) vulnerability in IBM SmartCloud Analytics Log Analysis 1.1 and 1.2 before 1.2.0.0-CSI-SCALA-IF0003 allows remote attackers to inject arbitrary web script or HTML via an invalid query parameter in a response from an OAuth authorization endpoint.

CVE-2014-0188
Published: 2014-04-24
The openshift-origin-broker in Red Hat OpenShift Enterprise 2.0.5, 1.2.7, and earlier does not properly handle authentication requests from the remote-user auth plugin, which allows remote attackers to bypass authentication and impersonate arbitrary users via the X-Remote-User header in a request to...

CVE-2014-2391
Published: 2014-04-24
The password recovery service in Open-Xchange AppSuite before 7.2.2-rev20, 7.4.1 before 7.4.1-rev11, and 7.4.2 before 7.4.2-rev13 makes an improper decision about the sensitivity of a string representing a previously used but currently invalid password, which allows remote attackers to obtain potent...

Best of the Web