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
Oldest First  |  Newest 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.

US Mayors Commit to Just Saying No to Ransomware
Robert Lemos, Contributing Writer,  7/16/2019
A Lawyer's Guide to Cyber Insurance: 4 Basic Tips
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  7/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-13951
PUBLISHED: 2019-07-18
The set_ipv4() function in zscan_rfc1035.rl in gdnsd 3.2.0 has a stack-based buffer overflow via a long and malformed IPv4 address in zone data.
CVE-2019-13952
PUBLISHED: 2019-07-18
The set_ipv6() function in zscan_rfc1035.rl in gdnsd 3.2.0 has a stack-based buffer overflow via a long and malformed IPv6 address in zone data.
CVE-2019-10100
PUBLISHED: 2019-07-18
The Sleuth Kit 4.6.0 and earlier is affected by: Integer Overflow. The impact is: Opening crafted disk image triggers crash in tsk/fs/hfs_dent.c:237. The component is: Overflow in fls tool used on HFS image. Bug is in tsk/fs/hfs.c file in function hfs_cat_traverse() in lines: 952, 1062. The attack v...
CVE-2019-10102
PUBLISHED: 2019-07-18
SaltStack Salt 2018.3, 2019.2 is affected by: SQL Injection. The impact is: An attacker could escalate privileges on MySQL server deployed by cloud provider. It leads to RCE. The component is: The mysql.user_chpass function from the MySQL module for Salt (https://github.com/saltstack/salt/blob/devel...
CVE-2019-10102
PUBLISHED: 2019-07-18
Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must open a specifically ...