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.

Operational Security //

Compliance

2/26/2018
08:05 AM
Dawn Kawamoto
Dawn Kawamoto
Dawn Kawamoto
50%
50%

GDPR Non-Compliance: Will Your Enterprise Get Busted?

GDPR enforcement begins May 25 and regulators are likely to focus on particular industries and types of companies, according to attorneys and analysts.

With the deadline for General Data Protection Regulation (GDPR) compliance fast approaching, US companies may be surprised to find that some organizations may face greater regulatory scrutiny than others.

Supervisory Authorities for each of the 28 European Union member states will be responsible for investigating and enforcing GDPR violations and compliance, according to cybersecurity audit and advisory firm Sera-Brynn. Come May 25, companies that have not taken the necessary steps to safeguard personally identifiable information of European Union citizens under the GDPR may face fines up to 4% of their company's annual revenues.

Data breaches that reveal thousands of users' personally identifiable information will likely draw the attention of supervisory authorities, but so will the type of industry and size of the company, say security and compliance analysts and attorneys.

Dissecting the sectors
Healthcare companies and organizations that deal with background checks are some of the industry sectors regulators will likely focus on, given the highly sensitive data that they access and process, Jim Halpert, partner and co-chair of global data protection, privacy and security practice for law firm DLA Piper, told Security Now.

He pointed to France and how regulators there have already publicly announced certain sectors they plan to focus on for potential GDPR investigations in the beginning of the year, such as the healthcare industry and online advertising industry.

Enza Iannopollo, a security and risk analyst for Forrester Research, agrees that some sectors will be targeted by regulators more than others.

"If you handle a large quantity of users' sensitive data, such as the financial industry or healthcare industry, then you'll likely be a target," Iannopollo told Security Now. "Although it goes to the sensitivity of the data, at the end of the day, it comes down to how well did you handle sensitive data."

Big companies vs. SMBs
EU regulators will generally go after large companies for GDPR violations, in part to make an example of them and also to collect higher enforcement fees, Halpert predicts.

Iannopollo agrees that while regulators may turn to large companies to make an example of GDPR enforcement, it has been the small and midsized companies that have been dinged more frequently for privacy violations and fines under Europe's existing data protection laws.

"There will be nothing different with GDPR except under this regulation you do not have to have a physical presence in Europe," she said.

Rick Hemsley, managing director of Accenture Security, told Security Now that the UK's Information Commissioner's Office (ICO) has noted they are going to provide more support to small businesses, so he doubts SMBs will be targeted for GDPR investigations.

And as for fines against companies that have failed to comply with the GDPR, Hemsley makes this prediction: "The big numbers associated with GDPR, 2% to 4% [of revenue], will only be enforced if there is significant or gross-negligence type of breaches."

He added there is nothing to suggest that companies that repeatedly fall out of GDPR compliance will face a progressively larger fine, adding, it is unlikely a "three-strikes" and you are out type of rule will be imposed.

Related posts:

— Dawn Kawamoto is an award-winning technology and business journalist, whose work has appeared in CNET's News.com, Dark Reading, TheStreet.com, AOL's DailyFinance, and The Motley Fool.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32615
PUBLISHED: 2021-05-13
Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
CVE-2021-33026
PUBLISHED: 2021-05-13
The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the ca...
CVE-2021-31876
PUBLISHED: 2021-05-13
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with ...
CVE-2019-10062
PUBLISHED: 2021-05-13
The HTMLSanitizer class in html-sanitizer.ts in all released versions of the Aurelia framework 1.x repository is vulnerable to XSS. The sanitizer only attempts to filter SCRIPT elements, which makes it feasible for remote attackers to conduct XSS attacks via (for example) JavaScript code in an attri...
CVE-2020-23995
PUBLISHED: 2021-05-13
An information disclosure vulnerability in ILIAS before 5.3.19, 5.4.12 and 6.0 allows remote authenticated attackers to get the upload data path via a workspace upload.