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.

Cloud

3/16/2016
04:45 PM
James Bindseil
James Bindseil
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

EU-US Privacy Shield: What Now, What Next?

The good news: We finally have a clear direction for continuing trans-Atlantic data transfer after several months in limbo. The bad news is in the remaining uncertainties.

The recent U.S. and European handshake deal on a new framework for trans-Atlantic data transfer, dubbed the EU-U.S. Privacy Shield, has given global businesses renewed optimism that their operations will not be hampered by complex legal maneuvering. As with the defunct Safe Harbor framework before it, once Privacy Shield is approved by the Article 29 Working Party, businesses that become certified as meeting the agreement’s privacy and data security provisions will have a streamlined administrative path for cross-border data flows.

With Privacy Shield, the good news is that we will finally have a clear direction for continuing trans-Atlantic data transfer after spending several months in limbo. That bad news is in the remaining uncertainties.

One of the biggest areas of ambiguity with Privacy Shield lies with the potential enforcement of regulations or fines across the 28 member countries in the EU – especially now that we’ve passed a critical milestone which put a hold on penalties for organizations still following the outdated Safe Harbor rules. A small handful of U.S. companies with ample resources, like Microsoft and Facebook, have European data centers for keeping the collection of information on EU citizens within the Union’s boundaries.

Keeping data operations thus contained goes a long way toward ensuring compliance with European privacy law with or without a new framework. However, the vast majority of businesses that do overseas business, whether large or small, aren’t so equipped. For them (and their legal teams), waiting for a signal from the EU has been a test of patience, trying to read the regulatory tea leaves and determine how to make the decisions that would allow them to continue doing business without crossing ambiguous lines in shifting regulatory sands.

Yet, even as the U.S. business community breathed a collective sigh of relief at word of an agreement, questions remain as to what—if any—form EU-U.S. Privacy Shield will take in its final implementation. Many EU member states remain suspicious of U.S. intelligence agencies and of American companies’ ability to resist requests for access to their data for national security purposes. The level of trust between the U.S. and EU in the post-Edward Snowden era remains low, even with subsequent revelations of aggressive domestic surveillance programs among European countries.

While it’s a good bet Privacy Shield will be ratified by the Article 29 Working Party, if your organization does business internationally, it should take steps to ensure it can continue to transfer data from the EU and do so in a way that is in compliance with regulation and best practices. That begins with a thorough review of current processes, including the legal agreements, tools and policies used to effect such operations.

The attention paid to Privacy Shield underscores the value of data in today’s economy. Whether that data is personal information or intellectual property, the information we collect, create, share, and store is vital to the success of any organization and, as such, should be handled and protected with care.

As for the lessons of Safe Harbor and Privacy Shield, they are just the beginning. Expect more of the same both at home and abroad as the importance of data—and its protection and management—becomes better understood by everyone.

Related Content:

Interop 2016 Las VegasFind out more about security threats at Interop 2016, May 2-6, at the Mandalay Bay Convention Center, Las Vegas. Register today and receive an early bird discount of $200.

James Bindseil is President and Chief Executive Officer of Globalscape, a leading developer of secure information exchange solutions. He has more than 20 years of experience in the technology industry, including senior leadership roles at Fujitsu, Symantec, and Axent ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-25595
PUBLISHED: 2020-09-23
An issue was discovered in Xen through 4.14.x. The PCI passthrough code improperly uses register data. Code paths in Xen's MSI handling have been identified that act on unsanitized values read back from device hardware registers. While devices strictly compliant with PCI specifications shouldn't be ...
CVE-2020-5783
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the login functionality does not contain any CSRF protection mechanisms.
CVE-2020-11031
PUBLISHED: 2020-09-23
In GLPI before version 9.5.0, the encryption algorithm used is insecure. The security of the data encrypted relies on the password used, if a user sets a weak/predictable password, an attacker could decrypt data. This is fixed in version 9.5.0 by using a more secure encryption library. The library c...
CVE-2020-5781
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, the langSelection parameter is stored in the luci configuration file (/etc/config/luci) by the authenticator.htmlauth function. When modified with arbitrary javascript, this causes a denial-of-service condition for all other users.
CVE-2020-5782
PUBLISHED: 2020-09-23
In IgniteNet HeliOS GLinq v2.2.1 r2961, if a user logs in and sets the ‘wan_type’ parameter, the wan interface for the device will become unreachable, which results in a denial of service condition for devices dependent on this connection.