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.

Attacks/Breaches

12/6/2018
11:10 AM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail

7 Common Breach Disclosure Mistakes

How you report a data breach can have a big impact on its fallout.
2 of 8

Not Having a Plan
To a large extent, how well you report and disclose a breach depends on how well you have planned for it in advance. Make sure the response plan cuts across functions and includes members from marketing, communications, and legal, says Tim Erlin, vice president of product management and strategy at Tripwire. 'The worst time to figure out how to respond to a breach is while it's happening,' he says. 'Make decisions ahead of time, not in the heat of the moment.
The plan should include who will release breach information, what information will be released, and when. 'If you don't do it correctly, not only can you have extra damage to your brand, but you increase your likelihood of being sued, which drives up the cost of the breach,' says Laura Lee, executive vice president of rapid prototyping at Circadence.
Image Source: Shutterstock

Not Having a Plan

To a large extent, how well you report and disclose a breach depends on how well you have planned for it in advance. Make sure the response plan cuts across functions and includes members from marketing, communications, and legal, says Tim Erlin, vice president of product management and strategy at Tripwire. "The worst time to figure out how to respond to a breach is while it's happening," he says. "Make decisions ahead of time, not in the heat of the moment.

The plan should include who will release breach information, what information will be released, and when. "If you don't do it correctly, not only can you have extra damage to your brand, but you increase your likelihood of being sued, which drives up the cost of the breach," says Laura Lee, executive vice president of rapid prototyping at Circadence.

Image Source: Shutterstock

2 of 8
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
12/29/2018 | 6:32:00 PM
Panera example
Another common way that organizations frequently downplay/cover up a security issue: Dismissing out of hand the security researchers who notify the organization of the vulnerability as a nuisance or criminal.

Happens a lot. See, e.g., Panera.

Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
7 SMB Security Tips That Will Keep Your Company Safe
Steve Zurier, Contributing Writer,  10/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: The old using of sock puppets for Shoulder Surfing technique. 
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-17513
PUBLISHED: 2019-10-18
An issue was discovered in Ratpack before 1.7.5. Due to a misuse of the Netty library class DefaultHttpHeaders, there is no validation that headers lack HTTP control characters. Thus, if untrusted data is used to construct HTTP headers with Ratpack, HTTP Response Splitting can occur.
CVE-2019-8216
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure .
CVE-2019-8217
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-8218
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure .
CVE-2019-8219
PUBLISHED: 2019-10-17
Adobe Acrobat and Reader versions , 2019.012.20040 and earlier, 2017.011.30148 and earlier, 2017.011.30148 and earlier, 2015.006.30503 and earlier, and 2015.006.30503 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .