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.

Security Management

10/19/2017
08:50 AM
Simon Marshall
Simon Marshall
Simon Marshall
50%
50%

GDPR Pressure Begins on US Multinationals

GDPR may be an EU regulation but it will have a significant impact on US companies doing business with any European customer, and the impact will start soon.

Europe's influence in US data protection law will soon prove whether businesses that hold personally identifiable information (PII) can meet the new General Data Protection Regulations (GDPR), currently awaiting launch in the US after the EU-US Privacy Shield act was ratified Wednesday by the EU.

May 25, 2018 is the date when GDPR will come into force. The scope of the regulation is quite frankly staggering. It affects not just EU businesses conducting trade with US companies, but anyone and everyone resident in Europe.

GDPR applies to any individual, whether their PII includes their private, professional or public life. The PII can be anything from a name, a home address, a photo, an email address, bank details, posts on social networking websites, medical information, right down to a computer's IP address.

And it will ask fundamental questions about data itself, essentially, what it is, how it is collected, where it goes, and it is stored.

Agreement between the EU and the Washington over just how those questions are answered could be a major stumbling block when it comes to enforcement, where definitions may be at odds between the two governments.

"Notification of breaches must be stringent, violation fines are expected to be stringent," Steve Schlarman, director of product marketing and GRC Strategist at security giant RSA, told Security Now. "It's a question of how law enforcement will look at the definition of what is an organization and how its data is used."

So, US firms could easily be forgiven for feeling somewhat panicked about the implications of GDPR. These include the difficulty of agreeable definitions concerning data breaches, how they are reported, and how the fine structure and tariffs for non-compliance should be calculated.

"How closely did companies conform to the regulations may form the basis of the fine. But there's a lot of interpretation here," said Schlarman. "The enforcement will have a structure, but there will be some learning."

Given attackers can sit unobserved within a network or system for months, this will inevitably pressure firms on their ability to detect, resolve -- and in the case of a breach -- qualify and quantify it using forensics.

Some observers accused SOINC Drive-In and Equifax -– two of the most recent data breaches –- of being slow to report and publicize their PII data exposures, potentially further endangering consumers financial and personal security. So an interpretation of "how quickly is good enough" looks like another basis for quibbles with the regulation.

Supporters of GDPR are positive about the regulation because is viewed as giving back control to citizens and residents over their personal data, and because it intends to simplify the regulatory environment for international business by unifying regulations within the EU with those in the US.

That should make it easier for non-European companies to comply; however, this comes at the cost of the strict data protection compliance regime with financial penalties of up to 2% of worldwide company turnover.

For its part, RSA announced Wednesday it is upgrading its security products to keep step with the rapidly developing GDPR environment. Data governance and privacy program management systems can now be paired with RSA breach response systems to tackle issues more quickly. Identity and data access assurance has been improved to help firms keep step with continuous compliance capabilities.

RSA also point to a recent PWC survey that indicates that GDPR compliance is at the top of the data protection list for over half of US multinationals.

Related posts:

— Simon Marshall, Technology Journalist, special to Security Now

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.