May 23, 2023

GDPR: Missing the Deadline?

The EU General Data Protection Regulation will go into effect on May 25, 2018, and as of this very moment, that’s 25 days away. A few months ago, the compliance timeline allowed mid-sized companies to overhaul their entire data management systems searching for areas of potential compromise, it allowed time to address security gaps, and it even allowed time to carefully source, screen and hire a Data Protection Officer if the company’s circumstances required one under the new law.

But at this point, the window is narrowing. That’s fine for those who have been steadily checking off every item on the compliance to-do list, but for those who are just getting started—or just finding out that the law applies to them—this means the time has come to change course or implement Plan B.

And these organizations are by no means alone. According to a survey by Solix Technologies taken at the end of February, about 22% of companies that handle sensitive data still aren’t sure if the GDPR applies to them since they operate outside of the EU but serve European customers. And up to 65% of the companies surveyed are expected to wake up on May 25th with critical compliance issues still unaddressed. That’s no small number.

So if your business seems likely to fall short of the deadline, you have plenty of company. But that doesn’t mean you’re on the right track, and it certainly doesn’t mean that the related penalties (up to 4% of global revenue or 20 million euros, whichever is higher) won’t be applied to you.

If you’re making progress and you have a strategy in place, great. But if not, it’s time to put contingency plans into action. Take these steps, starting today.

1.       Map out your course and determine which tasks simply won’t be fulfilled by May. No alert system or reporting structure in place in the event of a hack or data breach? No DPO hiring contract on the horizon? Find out which aspects are under your control and identify those that are simply non-starters.

2.       Review the text of the law with a help of a team of GDPR experts. Enlist professional support and go through each line item one at a time. Let go of the items that don’t apply to your enterprise (not every company needs to fulfill hiring requirements, and some elements of the law allow workarounds for certain non-EU data managers). Shift your focus to areas of high exposure.

3.       Start right now to establish a culture of compliance. This is something that can be done by any company at any time. Some types of data breach, loss, hacks or exposure may be unavoidable. But many are not, and regardless of specific GDPR compliance issues, there’s never a bad time to start taking data protection seriously.

4.       Do what you can with what you have. It’s possible that by May, an appeals process may be in place for those who face specific obstacles or hardships on the path to a new data security infrastructure. But don’t count on this, and instead, try to limit your exposure to fines and penalties using whatever methods are available to you. If and when you’re subject to an audit, be ready to demonstrate your efforts, including your contacts with outside support.

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.