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.

Endpoint //

Privacy

8/23/2018
02:30 PM
Tim Critchley
Tim Critchley
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
100%
0%

The GDPR Ripple Effect

Will we ever see a truly global data security and privacy mandate?

The race to comply with the European Union's General Data Protection Regulation (GDPR) by the May 25 deadline is over, but data security and privacy is a marathon, not a sprint. If the ever-evolving regulatory compliance landscape is any indication, GDPR is just the first of many mandates to come.

Although it certainly has been a headache for many organizations — with large firms allocating an average of $20 million to $25 million to become GDPR compliant — the GDPR is the catalyst for a much-needed global, all-encompassing data security and privacy law. This is something we need sooner rather than later.

Here's the challenge: Companies around the world have long been relying on a patchwork of laws and standards to secure customer data and keep their trust. Every day, security and compliance professionals deal with an alphabet soup of regulatory acronyms made up of industry, federal, state, and local mandates and standards. For example, a financial services organization that handles cardholder data must comply with the Payment Card Industry Data Security Standard. If that organization operates in the US, it must also abide by the Electronic Funds Transfer Act, which protects consumers when they manage their finances electronically. Should that entity conduct business with an EU citizen, it is also beholden to the GDPR, even though these three regulations each have different requirements, some of which complicate or even outright contradict each other. You can see how compliance can become muddled — quickly.

The GDPR is a breath of fresh air. Its guidelines represent a better way of working toward keeping customer data safe. We have already seen some of its ripple effects, sparking conversations about how companies must handle, share, and secure personally identifiable information (PII), and putting pressure on brands to instill trust in their constituents. To this point, a recent Forrester Research survey shows that 61% of US adults expressed concern about the sharing of their data or online behaviors between companies.

In addition, the GDPR is sparking updated and new legislation. For example, Canada is considering amending the Personal Information Protection and Electronic Documents Act — its federal privacy law for private-sector firms — to include GDPR compliance. And the state of California just passed the California Consumer Privacy Act of 2018. Coming into effect in 2020, it is believed to be the strictest privacy law in the US.

Although these mandates are steps in the right direction, it will still be years before we have a truly global regulation. In the meantime, the compliance landscape will only become more complex, with no single silver-bullet solution. However, there are a few steps you can take today to prepare for the regulations of tomorrow.

1. Define your data. Step back and understand where your customers' data is stored and map out the path it takes from the second it enters your system. Where does it go? How much do you have? How long are you storing it? Conduct a data discovery exercise that leverages artificial intelligence and machine learning to classify your information. Should a customer approach you to remove his or her data from a system (per GDPR's "right to be forgotten"), you can do so swiftly.

2. Assume your organization will be breached. It's no longer a matter of will we be breached, but when. For every customer record you hold, ask why you have it. If this data were stolen, could you provide a sound reason for storing it? For instance, if you are not a medical practice, can you justify holding a customer's healthcare data? If you're doubting whether you should hold a record, then don't!

3. Don't forget your team. Regularly train employees on basic security procedures, such as changing passwords regularly and looking out for phishing attacks. Clearly define your company's security policies and hold employees accountable. The crux of the matter is that insider threats (whether a malicious staff member stealing data or an innocent employee clicking on an email attachment containing malware) account for nearly half of all security incidents. To mitigate these risks, limit data access and apply the principle of "least privilege" — if someone doesn't need access to a record, he or she shouldn't have the ability to access it.

4. Remove as much PII as possible from your business environment. When viable, remove as much sensitive data as possible from the IT infrastructure. This could mean off-loading it to a compliant third party or simply and securely purging your database. For PII you can't remove, tokenize it and separate it from all other data so cybercriminals cannot obtain complete records. If you want to keep customer data past its shelf life, solely for statistical and research purposes, strip it of any personal identifiers such as names and addresses. As we like to say, "No one can hack the data you don't hold."

Related Content:

Learn from the industry's most knowledgeable CISOs and IT security experts in a setting that is conducive to interaction and conversation. Early-bird rate ends August 31. Click for more info

Tim Critchley has been the CEO of Semafone since 2009 and has led the company from a UK startup to an international business that spans five continents. He has helped secure Series A and Series B rounds of funding from various investor groups, including the BGF and Octopus. ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32697
PUBLISHED: 2021-06-21
neos/forms is an open source framework to build web forms. By crafting a special `GET` request containing a valid form state, a form can be submitted without invoking any validators. Form state is secured with an HMAC that is still verified. That means that this issue can only be exploited if Form F...
CVE-2020-19510
PUBLISHED: 2021-06-21
Textpattern 4.7.3 contains an aribtrary file load via the file_insert function in include/txp_file.php.
CVE-2020-19511
PUBLISHED: 2021-06-21
Cross Site Scriptiong vulnerability in Typesetter 5.1 via the !1) className and !2) Description fields in index.php/Admin/Classes,
CVE-2021-21422
PUBLISHED: 2021-06-21
mongo-express is a web-based MongoDB admin interface, written with Node.js and express. 1: As mentioned in this issue: https://github.com/mongo-express/mongo-express/issues/577, when the content of a cell grows larger than supported size, clicking on a row will show full document unescaped, however ...
CVE-2021-0532
PUBLISHED: 2021-06-21
In memory management driver, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-185196177