Attacks/Breaches

9/5/2017
07:30 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Data Breach Costs Vary Significantly by Organization

Don't use publicly reported breach costs at other organizations as an estimate for what you might end up paying for a breach, Forrester says.

One of the biggest mistakes that security professionals make when estimating data breach costs is to assume they can use publicly reported costs from breaches at other organizations as a reasonable proxy for their own.

In reality, data breach costs can vary substantially by organization and some of those costs may not even become apparent for several years, analyst firm Forrester Research cautioned in a report released this week. So, when building a business case for investments in data security and operational security, it is better to develop tailored breach estimates instead, Forrester said.

"The biggest misconception is believing that using publicly reported costs from another organization's breach is a reasonable proxy for possible costs for a data breach" in your own organization, says Heidi Shey, the author of the Forrester report.

What's publicly reported in other breaches is typically a subset of measurable short-term costs, such as the cost of investigation and breach notification, she says. They do not always include all other breach-related costs such as those associated with lost employee productivity, regulatory fines, lawsuits, brand damage and recovery, and additional security and audit requirements.

Costs can also vary by the type of data that was compromised. For instance, a breach of customer data or employee data will have very different cost implications compared to breach of intellectual property.

"When organizations think of costs, most of them are the immediate or short-term costs" that typically are incurred in the first six to nine months or so, Shey says.

Firms can overlook some of the squishier, more difficult to measure costs, such as reputation with customers and reputation as an employer. The latter, for instance, could make it more difficult for a breached entity to hire new security staff. Organizations can also often overlook long-term costs, including lawsuits that drag on for years, regulatory investigations that require time and attention to respond to, and settlements such as those with the Federal Trade Commission that can tack on 20 years' worth of audits, Shey says.

When developing a breach estimate, it is better to use a range that shows how different variables can affect the final outcome, rather than a specific number. "The goal," says Shey, "is to understand the factors that influence the costs and move forward the internal discussion about breach impact in a meaningful way."

For instance, use your own estimates as a starting point to show how greater investments in incident response can help minimize breach costs or how delayed notification can increase costs.

The Forrester report identified seven broad direct and indirect cost categories that security professionals need to consider when developing an estimate: response and notification; loss of productivity; lawsuits and settlements; regulatory fines; audit costs; brand recovery costs; and other costs such as higher interest rates because of lower credit ratings after a breach.

For each of these categories, the Forrester report provided an estimated range of the costs that organizations could incur in the event of a breach.

The analyst firm pegged the notification costs for a customer-facing data breach at between $5 and $10 per customer, for example, though it can sometimes be as high as $40 per customer. Forrester estimated hourly rates for incident response services to range between $250 and $550, for public relations and outreach services at between $200 and $500, and for legal services at between $390 and $1,200 per hour.

Forrester's advice on developing customized breach estimates follows a recent report from the Ponemon Institute that showed average breach costs increasing in the US even as it declined elsewhere for the first time in 10 years. The report pegged average breach costs in the US at $7.35 million compared to a global average of just over $3.6 million.

Related content:

 

Learn from the industry’s most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Click for more info and to register.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
1.9 Billion Data Records Exposed in First Half of 2017
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/20/2017
Get Serious about IoT Security
Derek Manky, Global Security Strategist, Fortinet,  9/20/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
Security Vulnerabilities: The Next Wave
Just when you thought it was safe, researchers have unveiled a new round of IT security flaws. Is your enterprise ready?
Flash Poll
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
[Strategic Security Report] How Enterprises Are Attacking the IT Security Problem
Enterprises are spending more of their IT budgets on cybersecurity technology. How do your organization's security plans and strategies compare to what others are doing? Here's an in-depth look.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.