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 Jr.
Curtis Franklin Jr.
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
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-23599
PUBLISHED: 2022-01-28
Products.ATContentTypes are the core content types for Plone 2.1 - 4.3. Versions of Plone that are dependent on Products.ATContentTypes prior to version 3.0.6 are vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscree...
CVE-2022-0395
PUBLISHED: 2022-01-28
Cross-site Scripting (XSS) - Stored in Packagist remdex/livehelperchat prior to 3.93v.
CVE-2022-21721
PUBLISHED: 2022-01-28
Next.js is a React framework. Starting with version 12.0.0 and prior to version 12.0.9, vulnerable code could allow a bad actor to trigger a denial of service attack for anyone using i18n functionality. In order to be affected by this CVE, one must use next start or a custom server and the built-in ...
CVE-2022-23598
PUBLISHED: 2022-01-28
laminas-form is a package for validating and displaying simple and complex forms. When rendering validation error messages via the `formElementErrors()` view helper shipped with laminas-form, many messages will contain the submitted value. However, in laminas-form prior to version 3.1.1, the value w...
CVE-2021-4160
PUBLISHED: 2022-01-28
There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis sug...