Data Protection Impact Assessments are the sleeping giants that lie deep in the GDPR. Doing DPIAs well requires organizations to commit to responsible data management at a deep, deep level. That’s one of the reasons why they are so challenging.
Data Protection Impact Assessments are the sleeping giants that lie deep in the GDPR. Doing DPIAs well requires organizations to commit to responsible data management at a deep, deep level. That’s one of the reasons why they are so challenging.
If one were to poll a sample of business, technical, and marketing professionals on “GDPR provisions that keep you up at night,” it’s likely DPIA’s wouldn’t make the top three. There are flashier aspects of GDPR. Consent management. Right-to-object. Data Subject Requests. Since these are the elements most frequently in the headlines, they tend to take up the most space on a business’s priority list.
But DPIA’s represent the biggest challenge to most businesses in their present state. And for that reason, establishing a DPIA process that adheres to the GDPR guidelines is a key indicator that a business is making a deep, meaningful commitment to data privacy.
For the uninitiated, here are the basics of a DPIA. It’s intended to let a business analyze and minimize the privacy risk from a processing activity. Under GDPR, businesses conduct a DPIA when undertaking a range of data processing activities, from monitoring public places to using innovative technologies to using biometric data. You can read more about the circumstances in which a DPIA is legally required here.
The Assessment itself is a multi-step process that involves coordination across a number of teams. The ICO describes the following nine steps as essential:
The purpose of this article isn’t to walk through the step-by-step of how a DPIA exercise should be conducted. The ICO has already published an excellent one of those here. Rather, it’s to point out what a challenge this poses for most businesses in their present state. Put simply, if most businesses did DPIA’s the way they’re supposed to, it would result in a productivity nightmare.
Within a modern large business, there could be hundreds of processing activities every year. Under GDPR many will require a DPIA. But the vast majority of businesses lack the processes or technology to perform them quickly; they are handled entirely manually. The result is not pretty. Members of the dev team emailing the legal department to set up a meeting where they present a proposed activity and, together, fill in half of a DPIA template form. Then a question comes up. The legal team consults with enforcement authorities for clarity, and the response takes a week to arrive. Meanwhile, developers are bottlenecked as they’re unsure whether they can proceed until getting clearance from legal. And the marketing team awaiting delivery of their snazzy new retargeting tool is frustrated. Multiply this scenario by a hundred cases a year, and the efficiency costs that a DPIA represents to many organizations becomes clear.
Given this, it’s not surprising that many businesses opt to take a “managed-risk” view of DPIA’s. Perhaps that represents the best of a bad bunch of options. With a fully manual process, the efficiency cost of compliance can look disastrously high.
But enforcement around GDPR is picking up. What’s more, consumers are beginning to expect higher standards of privacy practice. As time passes, the cost of DPIA non-compliance will rise steeply. And businesses that decide they can’t afford deep privacy measures today may find the long-run cost of their inaction significantly higher.
Ethyca hosted its second P.x session with the Fides Slack Community earlier this week. Our Senior Software Engineer Thomas La Piana gave a live walkthrough of the open-source privacy engineering platform, Fides 2.0. He demonstrated how users can easily deploy Fides and go from 0 to full DSR automation in less than 15 minutes. If you weren’t able to attend, here are the three main points addressed during the session.
Introducing consent management in Fides 2.0. With the coming state privacy laws in 2023, your business needs to have granular control over users’ data and their consent preferences. Learn more about how Fides can enable this for your business, for free.
Ethyca launched its privacy engineering meetup, P.x, where Fides Slack Community members met and interacted with the Fides developer team. Two of our Senior Software Engineers, Dawn and Steve, gave presentations and demos on the importance of data minimization, and how Fides can make data minimization easier for teams. Here, we’ll recap the three main points of discussion.
We enjoyed two great days of security and privacy talks at this year’s Symposium on Usable Privacy and Security, aka SOUPS Conference! Presenters from all over the world spoke both in-person and virtually on the latest findings in privacy and security research.
At Ethyca, we believe that software engineers are becoming major privacy stakeholders, but do they feel the same way? To answer this question, we went out and asked 337 software engineers what they think about the state of contemporary privacy… and how they would improve it.
The UK’s new Data Reform Bill is set to ease data privacy compliance burdens on businesses to enable convenience and spark innovation in the country. We explain why convenience should not be the end result of a country’s privacy legislation.
Our team of data privacy devotees would love to show you how Ethyca helps engineers deploy CCPA, GDPR, and LGPD privacy compliance deep into business systems. Let’s chat!
Get a Demo