Cloud

8/24/2017
10:30 AM
Peter Merkulov
Peter Merkulov
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
Google+
RSS
E-Mail vvv
100%
0%

GDPR Compliance Preparation: A High-Stakes Guessing Game

It's difficult to tell if your company is meeting the EU's data privacy and security standards -- or US standards, for that matter.

The countdown to the European Union's General Data Protection Regulation (GDPR) continues, and while companies spend their millions on compliance, questions remain as to whether they are spending their precious euros wisely. Data management tech firm Veritas recently issued a report concluding that although 31% of companies surveyed believe they are already compliant with GDPR, which goes into effect May 2018, only 2% really are operating under the terms of this omnibus data security and privacy regulation.

That's a gaping hole in readiness, one that should give pause to everyone doing business in the EU and with European trading partners.

Part of the problem may be in the vagaries that come with any regulation. Initially, terminology can be unclear and subject to broad interpretation. Often regulators draft their laws in the hope that vigorous legal challenges will aid in setting precedents and establishing the definitions that provide clarity. This is an important part of the regulatory process.

When it comes to data security, the landscape seemingly shifts daily, upsetting convention. In recent months, for example, two global malware campaigns — WannaCry and NotPetya — exposed common vulnerabilities in the security of thousands of companies whose systems were infected by ransomware. It's difficult to say whether the companies whose data was affected would have been found in violation of GDPR. However, if such an attack takes place after May 2018, and it is believed negligence was involved, there's a chance the European Commission could choose to act.

I've spoken to several legal and compliance experts regarding whether the WannaCry and NotPetya attacks could trigger action under the current GDPR regulation. One expert's answer summed up the consensus: "It depends; it's complicated."

This particular expert told me his firm has fielded inquiries from companies concerned that US data breach notification laws could have been triggered as a result of the ransomware attacks. In the case of California's data breach law, SB 1386, the conditions for noncompliance are "unauthorized acquisition of computerized data that compromises the security, confidentiality, or integrity of personal information maintained by the person or business."

This expert commented that the information known about the NotPetya attack doesn't seem to meet California's data breach standard. However, when working with hypotheticals, there's no way to definitively say. Perhaps there are terms in customer agreements that bind the enterprise to a lower standard of compliance under contractual obligation.

The definition of a data breach under GDPR is much broader than US law, he said, and includes the "accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, personal data transmitted, stored or otherwise processed." In short, according to GDPR there is a lower threshold for the conditions under which an incident may be considered a data breach. Falling victim to a ransomware campaign may well qualify.

The challenge for organizations preparing for GDPR compliance is in determining their appetite for risk and investing in the tools and processes necessary to achieve their desired level of security.

After that, businesses can only wait and hope their data protection measures meet with the authorities' approval and that their organization isn’t chosen by the EU to be used as a cautionary tale.

Given the questions and uncertainties that are swirling around GDPR compliance today, I wonder if Veritas's figure of a 2% rate of compliance isn't overly optimistic.

Related Content:

 

Learn from the industry’s most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Click for more info and to register.

Peter Merkulov serves as chief technology officer at Globalscape. He is responsible for leading product strategy, product management, product marketing, technology alliances, engineering and quality assurance teams. Merkulov has more than 16 years of experience in the IT ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
KaelynLowmaster
50%
50%
KaelynLowmaster,
User Rank: Author
8/25/2017 | 4:33:34 AM
GDPR v. CSL?
I'm curious whether compliance rates for China's Cybersecurity Law are progressing any more quickly than those for companies trying to navigate GDPR. Two very different emerging regulatory regimes to be sure (esp. as they relate to geographical reach - GDPR's extraterritoriality v. China's focus on domestic internet sovereignty), but the personal data they're seeking to govern is similar, as are the financial consequences for getting it wrong. Hopefully the longer runway for preparation will lead to fewer of the "cautionary tale"-type prosecutions you mention as possible for EU companies, but we're already seeing some investigations of big domestic players in China. I have a feeling the latter will be a much less consistent process, and that other juristictions will have a lot to learn from the differing approaches we're seeing with instituting GDPR v. CSL.
PeterMerkulov
50%
50%
PeterMerkulov,
User Rank: Author
8/29/2017 | 2:42:36 PM
Re: GDPR v. CSL?
You raise a good point about CSL. Whereas there has been much discussion and debate about GDPR, and the EU has promoted it and pushed for compliance preparation well in advance of next year's implementation, China's Cybersecurity Law was put into effect without much understanding within China, let alone among foreign businesses doing business in China. The NY Times wrote about the problem earlier this year: https://www.nytimes.com/2017/05/31/business/china-cybersecurity-law.html.
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
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-2018-20735
PUBLISHED: 2019-01-17
** DISPUTED ** An issue was discovered in BMC PATROL Agent through 11.3.01. It was found that the PatrolCli application can allow for lateral movement and escalation of privilege inside a Windows Active Directory environment. It was found that by default the PatrolCli / PATROL Agent application only...
CVE-2019-0624
PUBLISHED: 2019-01-17
A spoofing vulnerability exists when a Skype for Business 2015 server does not properly sanitize a specially crafted request, aka "Skype for Business 2015 Spoofing Vulnerability." This affects Skype.
CVE-2019-0646
PUBLISHED: 2019-01-17
A Cross-site Scripting (XSS) vulnerability exists when Team Foundation Server does not properly sanitize user provided input, aka "Team Foundation Server Cross-site Scripting Vulnerability." This affects Team.
CVE-2019-0647
PUBLISHED: 2019-01-17
An information disclosure vulnerability exists when Team Foundation Server does not properly handle variables marked as secret, aka "Team Foundation Server Information Disclosure Vulnerability." This affects Team.
CVE-2018-20727
PUBLISHED: 2019-01-17
Multiple command injection vulnerabilities in NeDi before 1.7Cp3 allow authenticated users to execute code on the server side via the flt parameter to Nodes-Traffic.php, the dv parameter to Devices-Graph.php, or the tit parameter to drawmap.php.