theDocumentId => 1333401 7 Common Breach Disclosure Mistakes

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
50%
50%

7 Common Breach Disclosure Mistakes

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

Image Source: Shutterstock

Image Source: Shutterstock

Marriot International is quickly emerging as the latest example of the importance of proper breach disclosure.

Last week the hotel giant disclosed that sensitive data belonging to some 500 million Starwood Hotels customers had been compromised in an intrusion that began in 2014 and remained undiscovered until this September.

Since the disclosure, the parent company has been hit with at least two lawsuits accusing it of delaying the breach disclosure and not providing enough details on the incident. The lawsuits are expected to be the first of many the company will face over the breach.

The breach has focused considerable attention on familiar topics, such as the need for organizations to have better breach detection and response capabilities, and on issues including data collection and data minimization, encryption, access controls, and strong authentication.

It is also serving as a new example of the need for organizations to have strong processes in place for breach reporting and disclosure, especially in an era of stringent regulations like the EU's GDPR.

"The fact this breach happened around four years ago and Marriott found out two months ago is concerning," says Ken Underhill, master instructor at Cybrary. "We all understand that a company needs to investigate what happened, but two months to report something this large is not acceptable," he says.

Here, according to Underhill and several security industry experts, are some of the most common pitfalls to avoid when making a breach disclosure.

 

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
 

Recommended Reading:

Previous
1 of 8
Next
Comment  | 
Print  | 
More Insights
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.

Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-37457
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the SipRule field (stored).
CVE-2021-37458
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the primary phone field (stored).
CVE-2021-37459
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via the customer name field (stored).
CVE-2021-37460
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via /planprop?id= (reflected).
CVE-2021-37461
PUBLISHED: 2021-07-25
Cross Site Scripting (XSS) exists in NCH Axon PBX v2.22 and earlier via /extensionsinstruction?id= (reflected).