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

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.

Government Shutdown Brings Certificate Lapse Woes
Curtis Franklin Jr., Senior Editor at Dark Reading,  1/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
The Year in Security 2018
This Dark Reading Tech Digest explores the biggest news stories of 2018 that shaped the cybersecurity landscape.
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-2019-6261
PUBLISHED: 2019-01-16
An issue was discovered in Joomla! before 3.9.2. Inadequate escaping in com_contact leads to a stored XSS vulnerability.
CVE-2019-6262
PUBLISHED: 2019-01-16
An issue was discovered in Joomla! before 3.9.2. Inadequate checks of the Global Configuration helpurl settings allowed stored XSS.
CVE-2019-6263
PUBLISHED: 2019-01-16
An issue was discovered in Joomla! before 3.9.2. Inadequate checks of the Global Configuration Text Filter settings allowed stored XSS.
CVE-2019-6264
PUBLISHED: 2019-01-16
An issue was discovered in Joomla! before 3.9.2. Inadequate escaping in mod_banners leads to a stored XSS vulnerability.
CVE-2019-6443
PUBLISHED: 2019-01-16
An issue was discovered in NTPsec before 1.1.3. Because of a bug in ctl_getitem, there is a stack-based buffer over-read in read_sysvars in ntp_control.c in ntpd.