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.

Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-1695
PUBLISHED: 2019-02-15
IBM QRadar SIEM 7.2 and 7.3 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 134177.
CVE-2018-1701
PUBLISHED: 2019-02-15
IBM InfoSphere Information Server 11.7 could allow an authenciated user under specialized conditions to inject commands into the installation process that would execute on the WebSphere Application Server. IBM X-Force ID: 145970.
CVE-2018-1727
PUBLISHED: 2019-02-15
IBM InfoSphere Information Server 9.1, 11.3, 11.5, and 11.7 is vulnerable to a XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 147630.
CVE-2018-1895
PUBLISHED: 2019-02-15
IBM InfoSphere Information Server 11.3, 11.5, and 11.7 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ...
CVE-2019-4059
PUBLISHED: 2019-02-15
IBM Rational ClearCase 1.0.0.0 GIT connector does not sufficiently protect the document database password. An attacker could obtain the password and gain unauthorized access to the document database. IBM X-Force ID: 156583.