May 23, 2023

How to Securely Share a SOC 2 Report

Today, many technology vendors are placing SOC 2 compliance as a key objective on their roadmap. The reasons are simple: SOC 2 compliance proves that you have made a strong commitment to your security and data protection efforts, it offers an industry-recognized stamp of approval, and it automatically generates trust with enterprise clients that are willing to spend lots of money on your product. 

In addition to that, a SOC 2 report makes the sales process a lot easier, reducing the time typically spent on filling out long security questionnaires to a tiny fraction. The problem here, however, is that companies don’t usually think about how they’re going to share their report with potential customers. 

Companies aren’t allowed to publish their SOC 2 report publicly. They can share that they are compliant and use that to start conversations, but they can’t publish the report and make it readily available. If they do, they risk sharing proprietary information that puts the company at risk. 

So, what’s the alternative? 

Modern sales processes require sales teams to share confidential information with prospects as part of the “procurement process”, however sales teams are not given the tools they need to do this without exposing the company. A rudimentary approach to solving this problem is by having prospects sign an NDA and then (and only then) sharing the report with the buyer. This can quickly become a clunky process as prospects often require chasing — especially if they need their legal team to review the NDA — and it can take a long time to get a signature. This is time that sales teams often can’t afford to waste when they’re trying to meet their quarterly targets and not lose contracts to competitors. 

In this regard, it can be easy to think that the legal team is holding sales reps back from being as efficient as possible — but there’s more to it than that. One tool that was designed to help remedy this disconnect is Pima.app. Pima.app was designed to allow salespeople to share confidential documents with their prospects, without compromising the legal shield offered by an NDA.

Lawyers can set up templatized Non Disclosure Agreements and enable their sales team to share most commonly asked documents such as a SOC 2 report or the results of a pentest.

Additionally, Pima can act as a lead generation tool by embedding a “Request center” on your website, allowing prospects to request your compliance documents directly, even if they’re not in a sales conversation yet.

Your sales team can then automatically approve requests, or filter them and approve them manually. Prospects will only be able to review the document after signing the NDA template provided by your legal team — but the beauty of the application is that it massively reduces the time it takes a prospect to sign. In addition, Pima offers a secure channel for sharing these sensitive materials, as opposed to email.

Curious to learn more about Pima? Check it out!


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.