Attacks/Breaches
3/7/2011
06:09 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Data Breach Costs Continue Climbing

Some of that cost may be unnecessary, a study has found.

The average cost of a data breach for a U.S. company continues to rise, having reached $7.2 million in 2010.

This represents an increase of 7% from 2009, when the average cost was found to be $6.8 million, according to Symantec which published "2010 Annual Study: U.S. Cost of a Data Breach," and the Ponemon Institute, which conducted the research.

The cost of losing data has grown for U.S. companies every year since 2006.

Larry Ponemon, founder of the Ponemon Institute, says that there was one unusual finding: A rapid response to a breach, which generally involves notifying everyone potentially affected, turns out to be more costly than a slow response.

Increasingly sophisticated data security threats and compliance pressures are pushing organizations to respond as rapidly as possible to data breaches. This is reflected in the finding that malicious attacks have become the most costly cause of breaches. But responding quickly to a breach may not be called for in every instance.

This isn't to say a slow response is always good; rather, it reflects the survey's finding that rapid notification can be a waste of money if subsequent investigation indicates some of those notified were not affected after all.

"In the world of data breaches, telling people your data is lost or stolen and then having to change that doesn't help anyone," said Ponemon in a phone interview.

Quick responders paid $268 per record, an increase of 22% from 2009, while organizations that took more time paid $174 per record, a decrease of 11% from 2009.

Symantec has created an online data breach calculator to help companies assess the potential cost and likelihood of a data breach. Not coincidentally, Symantec sells security solutions, particularly those focused on encryption.

Encryption has become more popular lately because data breach regulations often exempt companies from notification requirements if the lost data was encrypted.

This trend is partially reflected in the survey, which found: an increase in the number of organizations with an "above average IT security posture"; a decrease in breaches due to system failure, lost or stolen devices, and third-party mistakes; and more companies responding faster and putting CISOs in charge of response management.

Negligence remains the most common cause of breach incidents (41%), followed by lost or stolen portable or mobile devices (35%), malicious attacks (31%), and system failure (27%).

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-9710
Published: 2015-05-27
The Btrfs implementation in the Linux kernel before 3.19 does not ensure that the visible xattr state is consistent with a requested replacement, which allows local users to bypass intended ACL settings and gain privileges via standard filesystem operations (1) during an xattr-replacement time windo...

CVE-2014-9715
Published: 2015-05-27
include/net/netfilter/nf_conntrack_extend.h in the netfilter subsystem in the Linux kernel before 3.14.5 uses an insufficiently large data type for certain extension data, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via outbound network traffic that trig...

CVE-2015-1157
Published: 2015-05-27
CoreText in Apple iOS 8.x through 8.3 allows remote attackers to cause a denial of service (reboot and messaging disruption) via crafted Unicode text that is not properly handled during display truncation in the Notifications feature, as demonstrated by Arabic characters in (1) an SMS message or (2)...

CVE-2015-2666
Published: 2015-05-27
Stack-based buffer overflow in the get_matching_model_microcode function in arch/x86/kernel/cpu/microcode/intel_early.c in the Linux kernel before 4.0 allows context-dependent attackers to gain privileges by constructing a crafted microcode header and leveraging root privileges for write access to t...

CVE-2015-2830
Published: 2015-05-27
arch/x86/kernel/entry_64.S in the Linux kernel before 3.19.2 does not prevent the TS_COMPAT flag from reaching a user-mode task, which might allow local users to bypass the seccomp or audit protection mechanism via a crafted application that uses the (1) fork or (2) close system call, as demonstrate...

Dark Reading Radio
Archived Dark Reading Radio
After a serious cybersecurity incident, everyone will be looking to you for answers -- but you’ll never have complete information and you’ll never have enough time. So in those heated moments, when a business is on the brink of collapse, how will you and the rest of the board room executives respond?