Attacks/Breaches

1/28/2019
02:30 PM
Connect Directly
Twitter
RSS
E-Mail vvv
50%
50%

Why Privacy Is Hard Work

For Data Privacy Day, let's commit to a culture of privacy by design, nurtured by a knowledgeable team that can execute an effective operational compliance program.

This past May, you heard an awful lot about the GDPR, which is short for the EU's General Data Protection Regulation. For one brief, shining moment, the GDPR was searched more often than Beyoncé! But now that Data Privacy Day (January 28) has rolled around, Google Trends assures me, Beyoncé is back to being about 15 times more interesting.

And with Cardi B, it's 30 to one. That's so 2018.

Inside organizations around the world, however, interest is still very much piqued. The GDPR has moved from a looming deadline to a hovering reality, and it's not going away anytime soon.

This is a good thing for the people who've been hired to focus on compliance. Commensurate with the GDPR and all those subsequent emails, we have seen an explosion in the privacy profession, with the ranks here at the International Association of Privacy Professionals swelling to 47,000 members strong. Not only are they data protection officers, a role mandated for many companies by the GDPR, but they are privacy analysts, engineers, auditors, and so much more.

Many organizations have stood up teams to assure compliance with not only the GDPR but also the many privacy laws in the US that are popping up, including California's CCPA (California Consumer Privacy Act) of 2018. In January 2020, you can expect a little period where CCPA beats out Jay-Z, who isn't quite as popular as either his wife or Cardi, I’d wager.

These privacy laws, and those bubbling up around the globe as we speak, are no trifling matter.

Our annual research with EY tells us that just 44% of organizations considered themselves "fully compliant" with the GDPR when it went live in May, and of those companies, 20% admitted they'd basically never be fully compliant. And that's despite the average organization hiring three full-time employees and demanding time from another 2.5 staffers, just to handle the GDPR. Then, add to this the $3 million in average spending to adjust products and services and buy legal services and technology.

In 2018, the Global 500 spent an estimated $2.75 billion on GDPR compliance.

What, then, will be the impact of a U.S. federal privacy law that encompasses Internet firms and everyone else handling personal data?

In some ways, it may not be as impactful. The United States, despite some misconceptions, actually has a longer and deeper history of operationalizing privacy. It's something academics have labeled "Privacy on the Ground," and it relates to the compliance culture that popped up around HIPAA, the Fair Credit Reporting Act, the Children's Online Privacy Protection Act, data breach response laws, and others that were relatively early privacy laws with regulatory teeth.

In other ways, however, a US omnibus law could be very disruptive, potentially making industries like data brokers and ad-tech retool or rethink their business models. Data-driven companies in tech, finance and healthcare may find that there is a new normal and increased risk when it comes to gathering, using, and sharing data. Even small businesses will likely find that they need to start thinking carefully about privacy.

It's difficult to say what, exactly, will be the repercussions.  

One thing we do have relatively certainty on, however, is that managing privacy well is impossible without the right people. There is no "privacy tech" that can make an organization compliant overnight, nor any "policy" that can be put in place to solve the problem. Rather, organizations need widespread awareness of how personal data should be handled; a culture of privacy by design; and a team of privacy professionals who both know the law and how to execute an operational compliance program.

These things aren't easy. But, for Data Privacy Day, perhaps organizations can commit to getting the right people in place and getting started on the tough job of privacy. 

Related Content:

As president and CEO of the International Association of Privacy Professionals (IAPP), J. Trevor Hughes leads the world's largest association of privacy professionals, which promotes, defines and supports the privacy profession globally.  Trevor is widely recognized as a ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
New Free Tool Scans for Chrome Extension Safety
Dark Reading Staff 2/21/2019
Making the Case for a Cybersecurity Moon Shot
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  2/19/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-6485
PUBLISHED: 2019-02-22
Citrix NetScaler Gateway 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5 before build 69.5 and Application Delivery Controller (ADC) 12.1 before build 50.31, 12.0 before build 60.9, 11.1 before build 60.14, 11.0 before build 72.17, and 10.5...
CVE-2019-9020
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. Invalid input to the function xmlrpc_decode() can lead to an invalid memory access (heap out of bounds read or read after free). This is related to xml_elem_parse_buf in ext/xmlrpc/libxmlrpc...
CVE-2019-9021
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A heap-based buffer over-read in PHAR reading functions in the PHAR extension may allow an attacker to read allocated or unallocated memory past the actual data when trying to parse the file...
CVE-2019-9022
PUBLISHED: 2019-02-22
An issue was discovered in PHP 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.2. dns_get_record misparses a DNS response, which can allow a hostile DNS server to cause PHP to misuse memcpy, leading to read operations going past the buffer allocated for DNS data. This affects php_parser...
CVE-2019-9023
PUBLISHED: 2019-02-22
An issue was discovered in PHP before 5.6.40, 7.x before 7.1.26, 7.2.x before 7.2.14, and 7.3.x before 7.3.1. A number of heap-based buffer over-read instances are present in mbstring regular expression functions when supplied with invalid multibyte data. These occur in ext/mbstring/oniguruma/regcom...