May 23, 2023

GDPR: Key Operational Impacts

The General Data Protection Regulation (GDPR) describes a set of laws put forth by the European Commission in 2012 and finally enacted in 2016. All companies that operate in the European Union—including US companies that conduct business with European clients—will need to make all changes necessary to become fully compliant with the GDPR by May of 2018.

“For those who haven’t looked into the issue, we have one message: Start now.”

Most companies, in our current era of emphasis on data security, have already adopted privacy rules and data safety measures that more-or-less align with the requirements of the new law. In fact, many data teams and CEOs have scrambled to change their protocols only to discover that most of the necessary boxes have already been checked. Recent high-profile breaches and the need for defense against increasingly sophisticated hacking techniques have kept some data teams unwittingly ahead of the game.

But for those who haven’t looked into the issue, we have one message: Start now. Recognize that the fines and penalties for non-compliant data managers are steep and serious. Here are a few of the finer points of the GDPR that can’t be ignored.

GDPR operational impacts

  1. Data breach notification requirements: The GDPR covers who, when, and how to contact when an unavoidable disaster takes place.
  2. Data Protection Officer (DPO): Companies will need to hire an employee for this role, and the sourcing, selection and onboarding process should start sooner rather than later.
  3. Consent: Consent rules have changed, and obtaining signatures and releases will now be a more in-depth process than before.
  4. Cross-border data transfers: Cross-border transfers, transfers with third countries, and transfers to international organizations will be allowed by the GDPR, as long as these transfers comply with set conditions and make provisions for onward transfer.
  5. Portability and other rights: The GDPR will establish new rights for those who own the data in question, including the right to portability and the right to be “forgotten.”
  6. Pseudonymisation: The GDPR does not apply to data subjects that cannot be identified as a “natural person”, or who have been rendered anonymous to the point that they can’t be identified at all. But pseudonyms can be applied which can separate the data from direct identifiers and hold each of these two pieces of information in distinct places. The GDPR encourages data controllers to use this process.

These are the primary impacts that the GDPR will bring to most affected companies in the US—though this list by no means covers all the required areas of compliance.


We’re here to help.

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt.

Get Started
LEARN MORE!
Responsive Components
Responsive Components
Responsive Components
Hey! Have any questions?

Frequently Asked
Questions

What type of compliance standard can you help with?

We help our clients based on their needs. The majority of our contracts involve SOC-2, HIPAA, and most recently GDPR. Feel free to ask us if we can help with your particular case. If we aren't able to, we can most likely recommend you to someone who can.

How long does a SOC 2 engagement usually take?

We move as fast as our clients are able to make progress. Our fastest client to date got their SOC-2 Type I four months after signing our engagement letter. That record is up for grab if you are up for it.

In our experience however, it takes 6-9 months to achieve a SOC-2 Type I,  and 3-6 additional months to obtain a SOC-2 Type II report.

Which standard do you follow for your security policies?

All of our security policies follow the ISO-27001 standard. The Confidentiality, Integrity, and Availability standards cover the range of standards we like to work with for SOC 2.

Why do we have to become SOC 2 compliant if we are relying on AWS which is already compliant?

SOC 2 stands for Service Organization Control, meaning your clients are interested in understanding your controls, not your hosting provider’s control. As part of your vendor assessment we recommend reviewing AWS’ SOC 2 report, but relying on their report is not enough to become SOC 2 compliant.

Who is behind SOC 2?

The American Institute of CPAs. The AICPA is an established and respected organization that provides two forms of audits to companies that demonstrate evidence of a secure data-protection infrastructure. A Type I is a point in time audit that addresses the company’s description of its system, the suitability of the system’s design, and the effectiveness of its internal data controls. A Type II report happens over a period of time and emphasizes design and also focuses on the validity of the company’s controls.

Are SOC 2 reports a legal obligation?

No, but most enterprise level organizations that engage with sensitive data (again, almost all of them) have an obligation to their stakeholders to prove due diligence regarding data security, which means they’ll want to vet their service providers using this tool. SOC 2 can help these prospective service providers set themselves apart from the competition. Just as important, a SOC 2 report represents a meaningful and respected signifier of trust.

What can happen to a company without a SOC 2 report?

A lack of a SOC 2 report won’t result in legal problems, but it can and will limit outside assessments of the company’s commitment to data security. When large-scale clients look for providers, or large-scale backers look for a likely return on their investment, they don’t want concerns about security to stand in the way. Trust is a chain made of links that have each been put the test and have proven their ability to withstand pressure and scrutiny. Company leaders are wise to let SOC 2 auditors apply this pressure so their clients and backers don’t have to.

When is it too late for a SOC 2 audit?

Never. Even companies that have been in business for years but have never obtained a SOC 2 report can—and should—take steps in this direction now. Being compliant with SOC 2 can open the door to a broader base of more significant clients and larger contract opportunities. That being said, startups in the threshold of the marketplace, and new business owners who hope for an eventual public offering, should obtain a SOC 2 report during the development and financing process. By the time the company approaches Series B and C fundraising rounds, a report should be in hand.

How complicated is the auditing process?

The auditing process can be easy, or complicated depending on your level of preparation.

Preparing for the audit can take some time, attention, and the guidance of reliable data security experts. Don’t leave any part of this process to chance. Approach SOC 2 compliance one step at a time, and start by contacting a consulting firm with track record of experience in your area of the marketplace.