Attacks/Breaches

6/5/2018
02:25 PM
Connect Directly
Twitter
Twitter
RSS
E-Mail
50%
50%

The Breach Disclosure Double Standard

Cybersecurity pros expect to be notified immediately when they're breached, but most don't do the same - and some even cover up breaches.

For many cybersecurity professionals, swift breach disclosure is a matter of do as I say, not as I do. A new survey out today from Thycotic shows a big double standard exists between how quickly security pros expect their vendors and partners to disclose breaches and how fast they themselves tell others about security incidents. 

Conducted across the IT security community convened at RSA Conference earlier this spring, the survey shows that 84% of respondents say they want to be notified immediately if a company they've worked with has experienced a breach. Yet at the same time, just 37% of these people say they would extend the same courtesy of notifying customers expeditiously in the event that their firms were breached.

A big part of this may well be that companies don't have the capability for swift disclosure due to insufficient preparation on the incident response front. Only a little over half of the respondents say they have a tested incident response plan in place, while just one in five say they've prepared a contact list and communications plan to manage an incident. What's more, just one in ten organizations say they have a public relations and legal team prepped and ready to manage security incident communications should they be breached. 

This lack of preparation is putting global organizations under considerable regulatory risk now that the EU General Data Protection Regulation (GDPR) has gone live. One of the key requirements of GDPR is that organizations be ready to publicly disclose breaches that affect European residents' data within 72 hours. A recent study by Enterprise Strategy Group shows that only 33% of organizations are ready to meet this mandate.

The high prevalence of companies unable to quickly detect breaches, let alone swiftly notify victims, is troubling enough. But perhaps even more disconcerting is how many organizations go out of their way to actively hide incidents from being disclosed. 

Indeed, almost one in six respondents admit they've kept data breaches secret from the public or unsuspecting victims, according to Thycotic's study. These kind of numbers aren't a new revelation. Back in 2015, a different survey at that year's RSA Conference, from AlienVault, found that 20% of respondents have at the very least witnessed their companies trying to hide or cover up a breach.

What's new now, though, is the level of public furor kicked up following the egregious under-the-carpet sweeping behavior at Uber following its massive breach of 57 million people's data. As the embarrassing details kept unfolding, it came out that the ride-share company paid an attacker $100,000 from a bug bounty program that usually only paid out a fraction of that per bug to cover up the breach.

It's this kind of lack of accountability that's pushing regulators to stiffen the consequences for organizations that fail to quickly notify affected parties after a breach. Not only is the big hammer of GDPR hovering over global organizations, but US regulators also are making noises. US legislators are now toying with the idea of sentencing executives with jail time for not disclosing data breaches.  

<p> <img src="https://img.deusm.com/darkreading/MarilynCohodas/InSecurityvplug-368592_DR18_DR-VE-Logo-Signature.png" alt="" width="380" height="49" style="vertical-align: top;" /></p>

<p><strong>Top industry experts will offer a range of information and insight on who the bad guys are – and why they might be targeting your enterprise. </strong><strong>Click for <a href="https://event.darkreading.com/3453?keycode=sbx&cid=smartbox_techweb_upcoming_webinars_8.500000825" target="_blank">more information</a></strong></p>

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Veterans Find New Roles in Enterprise Cybersecurity
Kelly Sheridan, Staff Editor, Dark Reading,  11/12/2018
Empathy: The Next Killer App for Cybersecurity?
Shay Colson, CISSP, Senior Manager, CyberClarity360,  11/13/2018
Understanding Evil Twin AP Attacks and How to Prevent Them
Ryan Orsi, Director of Product Management for Wi-Fi at WatchGuard Technologies,  11/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Online Malware and Threats: A Profile of Today's Security Posture
Online Malware and Threats: A Profile of Today's Security Posture
This report offers insight on how security professionals plan to invest in cybersecurity, and how they are prioritizing their resources. Find out what your peers have planned today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-18519
PUBLISHED: 2018-11-19
BestXsoftware Best Free Keylogger 5.2.9 allows local users to gain privileges via a Trojan horse &quot;%PROGRAMFILES%\BFK 5.2.9\syscrb.exe&quot; file because of insecure permissions for the BUILTIN\Users group.
CVE-2018-19355
PUBLISHED: 2018-11-19
modules/orderfiles/ajax/upload.php in the Customer Files Upload addon 2018-08-01 for PrestaShop (1.5 through 1.7) allows remote attackers to execute arbitrary code by uploading a php file via modules/orderfiles/upload.php with auptype equal to product (for upload destinations under modules/productfi...
CVE-2008-7320
PUBLISHED: 2018-11-18
** DISPUTED ** GNOME Seahorse through 3.30 allows physically proximate attackers to read plaintext passwords by using the quickAllow dialog at an unattended workstation, if the keyring is unlocked. NOTE: this is disputed by a software maintainer because the behavior represents a design decision.
CVE-2018-19358
PUBLISHED: 2018-11-18
GNOME Keyring through 3.28.2 allows local users to retrieve login credentials via a Secret Service API call and the D-Bus interface if the keyring is unlocked, a similar issue to CVE-2008-7320. One perspective is that this occurs because available D-Bus protection mechanisms (involving the busconfig...
CVE-2018-19351
PUBLISHED: 2018-11-18
Jupyter Notebook before 5.7.1 allows XSS via an untrusted notebook because nbconvert responses are considered to have the same origin as the notebook server. In other words, nbconvert endpoints can execute JavaScript with access to the server API. In notebook/nbconvert/handlers.py, NbconvertFileHand...