May 23, 2023

GDPR: The Dust is Still Settling, But the Penalties are Real

The General Data Protection Regulation went into effect in May, pushing business owners with EU clients to scramble as the deadline approached. Those with the resources to comply have done so (for the most part) and those who don’t yet have the resources and information necessary to comply are still working on it (presumably). But as the well-prepared glide over the finish line and the stragglers put the final edits on their disclosure forms, the EU Commission has sent one message loud and clear: keep moving toward the goal…or else.

The GDPR allows fines of up to 20 million Euros or 4% of global revenue. (For perspective, that means that if the Cambridge Analytica scandal had taken place after the May 25th deadline, the $664,000 fine levied by the UK Information Commissioner’s office would have been about $1.9 billion.)  So far, these fines and penalties have not been distributed en masse, but as the dust settles, warnings are likely to be issued and fines will follow.

At this point, the Data Protection Authority (DPA) in each member state of the European Union can determine how stringently the rules are enforced and which failed audits will result in warnings versus actual penalties.

A kind of grace period appears to be underway during which DPAs in a host of member countries are listening to complaints and deciding how much sympathy or leeway should be granted to both parties (customer and company) in each case. During this period, both large companies and startups are likely to receive at least some form of notice before external audits commence and penalties are put in place…but that’s no reason to slow down if you still haven’t met the criteria.

If you fall into this category, it’s time to prioritize. Work on two aspects of compliance before all others: providing proper notification to customers regarding the use of their data (no unreadable messages or legalese!), and putting systems in place that allow you to immediately recognize a breach and notify those affected. Other aspects of the regulation can come later, but these two should be at the top of the list, if you haven’t addressed them already.

Consider this quiet chapter a kind of gift, and act quickly to take advantage of the moment. Need support and guidance? Our teams are still standing by to address GDPR late-comers—get this task taken care of! We can help.


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.