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.

Risk

1/26/2016
09:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Post-Breach Costs And Impact Can Last Years

SANS study examines long-term effects of breach events.

The costs and implications of data breaches go far beyond the initial incident response and customer notification costs. In a new survey out by the SANS institute, only about one third of organizations are able to remediate breaches within a week of detection and the greatest financial impact from breaches extended months and even years beyond the event for the majority of organizations.

Conducted on behalf of Identity Finder, the SANS study took an in-depth dive into the post-breach ramifications of nearly 60 organizations. Coming from a fairly distributed range of organization sizes and industries, the study shows that even after remediation, over 60% of organizations still felt the impact from breaches. Meanwhile, the greatest financial impacts were felt long after the exposure occurred. Over 40% of organizations said they felt the biggest monetary pinch one- to 12 months after the fact.

These financial shocks often come from unexpected sources. For example, some organizations may recognize that there will need to be additional resources necessary to conduct forensics investigations during breaches, but don't realize they'll have to make unplanned purchases following an incident. Approximately 57% of respondents reported having to acquire additional tools for forensics or data recovery as a result of a breach.

Additionally, breaches frequently uncover root causes that require additional controls to prevent them from happening again and to keep the regulators at bay once an event brings their focus onto an organization. Nearly three-quarters of organizations needed to divert resources to bolster the development of administrative policies, and approximately 65% had to spend extra money on training and awareness programs following a breach. Additionally, 65% of organizations had to purchase technical tools outside the normal IT budget cycle, and over 60% needed to pick up physical controls in the wake of a breach. What's more, around a third of organizations realized they needed to add or change managed services to account for increased security after a breach.

"One could argue that these controls were needed anyway and that they should not be included in an accounting of post-breach costs. After all, having proactive security policies and procedures in place is always the best defense against a breach," wrote the report's author, Barbara Filkins. However, the fact that these purchases and resource allocations were sudden and unplanned invariably means they threw off the balance of budgeting and caused disruption in the flow of IT operations -- versus taking a pre-emptive and measured approach to increasing controls.

As things stand, fewer than half of organizations carry cyber insurance for breach events, and only about a third of organizations had enough coverage to completely cover post-breach costs, according to the report.

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
<<   <   Page 2 / 2
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/28/2016 | 10:39:14 AM
Re: Cyber insurance?
@Dr. T (10:33:36) I agree that relying on cyber insurance to heavily can be a hindrance however not having a basic policy for cyber insurance may also be detrimental. You need to way the cost of potential data loss against the policy you wish to acquire and what you are covered for. You don't want to pay more in the long run for an insurance policy than you stand to lose in a data breach.
<<   <   Page 2 / 2
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Lessons from the NSA: Know Your Assets
Robert Lemos, Contributing Writer,  12/12/2019
4 Tips to Run Fast in the Face of Digital Transformation
Shane Buckley, President & Chief Operating Officer, Gigamon,  12/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19807
PUBLISHED: 2019-12-15
In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for ...
CVE-2014-8650
PUBLISHED: 2019-12-15
python-requests-Kerberos through 0.5 does not handle mutual authentication
CVE-2014-3536
PUBLISHED: 2019-12-15
CFME (CloudForms Management Engine) 5: RHN account information is logged to top_output.log during registration
CVE-2014-3643
PUBLISHED: 2019-12-15
jersey: XXE via parameter entities not disabled by the jersey SAX parser
CVE-2014-3652
PUBLISHED: 2019-12-15
JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.