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.

Operational Security

6/20/2017
12:18 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

Cost of Cyber Breach Goes Down for Some

The cost of dealing with a cyber breach went down last year, but not for everyone. Were you on the lucky side of the equation?

Ready for some good security news? According to a study sponsored by IBM and conducted by Ponemon Institute, the cost of a data breach actually went down by 10% in 2017. The good news isn't evenly distributed, of course, and there are little nuggets of negativity sprinkled across the upbeat facts of the headline.

The information in Ponemon Institute's 2017 Cost of Data Breach Study: Global Overview shows that, for the first time, the cost of a data breach has gone down from the previous year, to $141 per lost or stolen record (or an average of $3.62 million per incident). The reduction wasn't uniform across all countries and regions, though; Europe saw a 26% decrease in incident costs while US costs rose by 5%, to an average per-incident tab of $7.35 million.

When IBM looked at the difference between nations and regions, they found one compelling factor: regulations. The facts around regulations won't offer vindication either to pro-regulation or pro-free-market advocates. While fewer regulations didn't correlate with lower costs, more uniform regulations did.

Specifically, companies in the US spent more for compliance failures and on notification to affected users than their counterparts in Europe, at least partially due to the fact that 48 states have individual laws and regulations concerning how companies must deal with data breaches. According to the report:

...compliance failures cost U.S. businesses 48 percent more than European companies, while rushing to notify cost U.S. businesses 50 percent more than European companies. Additionally, U.S. companies reported paying over $690,000 on average for notification costs related to a breach -- which is more than double the amount of any other country surveyed in the report.

While not a cost that varies by region, Ponemon's study did find two more significant factors in the cost of a breach. The first? Response time.

This study isn't the first to find a relationship between response time and breach cost -- we've covered similar conclusions here at Security Now. The new report does put a price tag on lethargy, saying that a breach that takes more than 30 days for detection and response costs, on average, more than a million dollars more than a breach met with a fast response.

The numbers become even more significant when combined with the average time for an organization to respond to a breach. According to the report, "On average, organizations took more than six months to identify a breach, and more than 66 additional days to contain a breach once discovered." This means that business, as a whole, is leaving millions and millions of dollars on the table simply because they have not yet put the organization and infrastructure in place to detect and remediate breaches quickly.

There will certainly be more studies on the cost of IT breaches. That's not in question. What is in question is whether the business community, in partnership with government, will work to reduce the cost of those breaches before they grow to become a major drag on profitability.

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
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
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7029
PUBLISHED: 2020-08-11
A Cross-Site Request Forgery (CSRF) vulnerability was discovered in the System Management Interface Web component of Avaya Aura Communication Manager and Avaya Aura Messaging. This vulnerability could allow an unauthenticated remote attacker to perform Web administration actions with the privileged ...
CVE-2020-17489
PUBLISHED: 2020-08-11
An issue was discovered in certain configurations of GNOME gnome-shell through 3.36.4. When logging out of an account, the password box from the login dialog reappears with the password still visible. If the user had decided to have the password shown in cleartext at login time, it is then visible f...
CVE-2020-17495
PUBLISHED: 2020-08-11
django-celery-results through 1.2.1 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.
CVE-2020-0260
PUBLISHED: 2020-08-11
There is a possible out of bounds read due to an incorrect bounds check.Product: AndroidVersions: Android SoCAndroid ID: A-152225183
CVE-2020-16170
PUBLISHED: 2020-08-11
The Temi application 1.3.3 through 1.3.7931 for Android has hard-coded credentials.