Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

3/27/2012
04:11 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Data Breach Lawsuits Less Likely In Hacks

Individuals whose personal data is exposed in a data breach more likely to sue if the victim organization mishandled their data, researchers find

Ever wonder about the odds of a lawsuit in the wake of a data breach? According to new research, breaches caused by careless handling of personal data inspire most victims to sue the breached organization that exposed their data. Companies who get hacked by outside forces are less likely to face litigation.

A group of researchers from Carnegie Mellon's Heinz College of Public Policy and Information Technology and Temple University's Beasley School of Law have published a new paper detailing their research on the probability of breach lawsuits and of cases reaching settlement. The researchers studied more than 200 federal data breach lawsuits filed between 1998 to 2011, and published their results in "Empirical Analysis of Data Breach Litigation."

Do the findings mean victims don't necessarily hold the company responsible for their exposed data if outside circumstances led to a hack or breach? It appears they are less tolerant or forgiving of missteps or carelessness with the handling of the data internally. It also bolsters the argument that victim organizations should come clean with a "mea culpa," according to one renowned security expert.

"Despite companies being told by their attorneys to never comment on [a hack], if in fact they get up and say, 'I'm sorry,' they are much less likely to get sued," says Bruce Schneier, CTO at BT Counterpane. "People are pretty forgiving. This is not surprising ... it's been confirmed in many other studies."

Breaches that occurred due to "unauthorized disclosure or disposal" of personal information are twice as likely to generate a lawsuit than ones that came out of a cyberattack. When the company that was breached mishandles data (think misplaced data drives or unauthorized access to the data), it has a 7 percent higher probability of getting sued. When a cyberattack is the cause of a breach, there's a nearly 3 percent more likely chance of a lawsuit, according to the study.

"These results suggest that plaintiffs respond more to the careless or negligent handling by a firm of their personal information than to the firm's inability to withstand a cyber-attack," the researchers wrote in their paper.

But the overall size and scope of a breach, the cause, and the types of personal information that's exposed aren't major factors in a data breach lawsuit ruling or outcome. "Instead, the probability of settlement appears to be driven by the presence of actual financial loss, and class certification," the researchers wrote.

When a plaintiff claims to have suffered financial damages from the breach, the defendant organization settles 30 percent more often, as well as if a class action suit is filed. Companies are 3.5 times more likely to be sued if their customers suffered financial harm from a breach. Offering free credit monitoring can cut those odds, however, according to the research.

Nearly 90 percent of the cases settled were ones where the individual could show harm as a result of the breach, and they were settled in half of the cases where harm wasn't demonstrated.

And if the breach exposed financial information, the chance of a lawsuit was 9.7 percent higher probability. "Surprisingly, however, breaches involving social security numbers were negatively correlated with lawsuit, though the effect was relatively, small at 2.4%," the report says. And medical data or credit card data don't affect the probability of litigation.

"Overall, these results suggest that only breaches of financial information and, oddly, date of birth are more likely to result in a lawsuit. While some may speculate that feelings of strong privacy for one's information may lead them to filing suit, this is not uniformly reflected in our results. If it were, we would expect that compromise of all forms of PII would be strong predictors of lawsuit," the report says.

A copy of the research paper, authored by CMU's Sasha Romanosky and Alessandro Acquisti and Temple's David Hoffman, is available here (PDF).

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

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Bprince
50%
50%
Bprince,
User Rank: Ninja
3/29/2012 | 3:13:24 AM
re: Data Breach Lawsuits Less Likely In Hacks
The fact that people are more likely to give companies a pass when they are hit with a cyber-attack versus when they misplace something shows a growing awareness of how easy it is to be hacked.
Brian Prince, InformationWeek/Dark Reading Comment Moderator
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...