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
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
The Fundamental Flaw in Security Awareness Programs
Ira Winkler, CISSP, President, Secure Mentem,  7/19/2018
Number of Retailers Impacted by Breaches Doubles
Ericka Chickowski, Contributing Writer, Dark Reading,  7/19/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19990
PUBLISHED: 2018-07-23
October CMS version prior to build 437 contains a Cross Site Scripting (XSS) vulnerability in the Media module and create folder functionality that can result in an Authenticated user with media module permission creating arbitrary folder name with XSS content. This attack appear to be exploitable v...
CVE-2018-19990
PUBLISHED: 2018-07-23
October CMS version prior to Build 437 contains a Local File Inclusion vulnerability in modules/system/traits/ViewMaker.php#244 (makeFileContents function) that can result in Sensitive information disclosure and remote code execution. This attack appear to be exploitable remotely if the /backend pat...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit cced03dd667a5df6df8fd40d8de0bff477ee02e8 contains multiple out of array access vulnerabilities in the mms protocol that can result in attackers accessing out of bound data. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fix...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit 2b46ebdbff1d8dec7a3d8ea280a612b91a582869 contains a Buffer Overflow vulnerability in asf_o format demuxer that can result in heap-buffer-overflow that may result in remote code execution. This attack appears to be exploitable via specially crafted ASF file that has to be provide...
CVE-2018-19990
PUBLISHED: 2018-07-23
FFmpeg before commit 9807d3976be0e92e4ece3b4b1701be894cd7c2e1 contains a CWE-835: Infinite loop vulnerability in pva format demuxer that can result in a Vulnerability that allows attackers to consume excessive amount of resources like CPU and RAM. This attack appear to be exploitable via specially c...