Endpoint

10/16/2017
01:00 PM
Sara Peters
Sara Peters
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

GDPR Compliance: 5 Early Steps to Get Laggards Going

If you're just getting on the EU General Data Protection Regulation bandwagon, here's where you should begin.
Previous
1 of 7
Next

Although the European Union's General Data Protection Regulation (GDPR) has been in effect since 2016, and although enforcement actions kick off a mere seven months from now, many companies didn't really appreciate the magnitude of the new privacy legislation until the Equifax breach.

An American company exposed the sensitive private data of 700,000 citizens of the United Kingdom (still part of the European Union); "sensitive, private data" that is, by the American definition. The European Union's definition is significantly broader, and in all Equifax exposed 12.5 million UK clients' records. It is possible that European data authorities might do different accounting.

Monetary penalties for GDPR are up to 20 million Euros or 4 percent of annual turnover (similar to revenue), whichever is higher. Data privacy authorities can also ban companies from processing certain kinds of data entirely, which can massively disrupt entire business models. Organizations must also consider the costs of defending themselves in the many lawsuits that citizens and data authorities might bring against them.

With retributions like that looming overhead, it's no wonder that organizations are waking up to the importance of GDPR preparation. Here are a few places to start.

 

Sara Peters is Senior Editor at Dark Reading and formerly the editor-in-chief of Enterprise Efficiency. Prior that she was senior editor for the Computer Security Institute, writing and speaking about virtualization, identity management, cybersecurity law, and a myriad ... View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/21/2017 | 3:28:41 PM
Compliance oopsies
All of these tips are important for all data-protection initatives, but especially the first one, IMHO. So many organizations, in my experience, think that they are in compliance when it turns out they have a big ol' OOPS glaring them in the face.

The relationship that TJX had with PCI-DSS comes immediately to mind, for instance. That company's CIO, way back when, before and during its major breach, chose to stand on a relatively shoddy justification of PCI-DSS compliance.
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
WSJ Report: Facebook Breach the Work of Spammers, Not Nation-State Actors
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/19/2018
4 Ways to Fight the Email Security Threat
Asaf Cidon, Vice President, Content Security Services, at Barracuda Networks,  10/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-10839
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
CVE-2018-13399
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
CVE-2018-18381
PUBLISHED: 2018-10-16
Z-BlogPHP 1.5.2.1935 (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
CVE-2018-18382
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
CVE-2018-18374
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.