Database: 9 Database Security Resolutions for 2011
Gawker Media, McDonald's and Ohio State University all have something in common; they were each victims of a data breach in 2010. For Gawker, the compromise exposed user passwords; for McDonald's it was customer information. OSU had to deal with the compromise of a database server with personal information belonging to more than 760,000 students, faculty and alumni. As always, the conversation after such incidents turns to database security, and how these types of events can be avoided or their impacts minimized. There is a reason for that. Beyond just the damage to the brand or reputation of whatever organization is hit, there are the costs associated with notification and remediation. And it's not getting cheaper-a fact proven by Ponemon Institute's report earlier this year that data breaches cost U.S. companies an average of $204 per record in 2009, for an average-per-incident cost of $6.75 million. In discussions with database security pros from IBM, Sentrigo, Pythian and Application Security, we culled a list of tips for enterprises to consider as they plan their database defenses and management strategies for the New Year. Here are a few tips for your IT department to keep in mind.