Perimeter
Guest Blog // Selected Security Content Provided By Sophos
What's This?
4/25/2011
03:01 PM
Dark Reading
Dark Reading
Security Insights
Connect Directly
RSS
E-Mail
50%
50%

Lone Star State Learns Valuable DLP Lesson

The state of Texas has spent nearly $2 million responding to a major data leakage incident. Wouldn't it be cheaper to simply protect our data?

The state of Texas announced it has already spent roughly $1.9 million following the exposure of more than 3.5 million people's Social Security numbers, addresses, and other personal details.

More specifically, it has spent $1.2 million on notifying victims, $400,000 on setting up a call center, and $300,000 on hiring security professionals to investigate. This could be just the tip of the iceberg when it comes to the total cost of this incident.

Fortunately for the victims, the state has decided to provide credit monitoring, Social Security number protection, and identity theft insurance.

In Ponemon's report, the "Fifth Annual U.S. Cost of a Data Breach Study," it was determined that the average cost per record lost in data breaches was approximately $204. That implies Texas is getting off easy, to date having spent less than $1 per affected person.

Organizations need to look at these incidents as wake-up calls. In this case, it is believed that none of the exposed data was ever accessed, and yet the costs continue to rise. Had the data actually been accessed by criminals, the costs could have been much higher.

The state's mistake has been repeated frequently throughout the business community. It assumed the data did not need to be encrypted because it would always be stored "inside the network," where it would be safe and secure.

Sensitive data is more mobile than ever and needs protection regardless of where you think it will be stored or contained. Consider the quantity of digital data you can carry in your pocket on a regular basis; this changes the game when it comes to protection of records.

Could you imagine losing 2 million paper records? It would require some serious effort to move that quantity of data -- and a claim of ignorance would not be a reasonable defense. While the efficiency and convenience of digital records have revolutionized the business environment, this comes with the responsibility of controlling that information flow.

I hope this incident alerts IT professionals that full-disk encryption for laptops is simply not enough when looking to protect personally identifiable information (PII). If you handle sensitive information, then you should be taking steps to protect it, regardless of where it is stored or intended to be stored.

Chester Wisniewski is a senior security adviser at Sophos Canada.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

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
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
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.