What is SOC 2 compliance? A plain English guide
SOC 2 is an independent audit, performed by a CPA firm, of the controls a service organisation uses to protect systems and data, reported against the AICPA's Trust Services Criteria. Most advice tells you to look for a vendor's SOC 2 logo and move on. I wouldn't. The logo tells you almost nothing about what was checked, when, or for which product.
SOC 2 is an independent report, not a certificate
What is SOC 2 compliance in plain terms? It's an independent examination of the controls a service organisation uses to protect its systems and the data inside them. The framework was created by the American Institute of Certified Public Accountants (AICPA), and the current AICPA 2017 Trust Services Criteria with revised points of focus in 2022 covers security, availability, processing integrity, confidentiality, and privacy.
Think of a report from an independent building inspector on one specific building. It's not a stamp every builder in town can carry. The inspector writes about that building, at that time, against an agreed scope.
Three misreadings cause most confusion:
- Not a government license: No regulator grants it or fines you for lacking it.
- Not a one-time certification: There's no certificate on the wall. There's a report with an auditor's opinion.
- Not a guarantee: It doesn't prove a company can't be breached.
The company defines its own system, services, and scope first. The auditor then checks whether controls for that defined system are suitably designed and, for some reports, operating effectively. Two providers can both hold SOC 2 reports covering very different things. Cloud, SaaS, hosting, and data-processing providers get asked for it most, usually because enterprise buyers require it in procurement. Ask for the report and its scope, not just the logo.
The five trust services criteria and which ones matter
Security is the common foundation in every report. The other four are chosen with the auditor based on the commitments you've made to customers.
| Criterion | What it covers | Relevance for document and video platforms |
|---|---|---|
| Security | Protection against unauthorised access, including logical and physical controls | Required base for every SOC 2 report, and can cover access to shared links and stored files when they are in scope |
| Availability | Systems are operational and usable as committed | Relevant when buyers depend on links and video playback during deals |
| Processing integrity | Processing is complete, valid, accurate and timely | Relevant where view analytics and alerts must be correct |
| Confidentiality | Information designated as confidential is protected | Relevant for contracts, proposals, pricing and investor materials |
| Privacy | Personal information is collected, used, retained and disposed of as committed | Relevant for viewer email capture and view-tracking data |
What each one looks like in practice
Security covers who can open a shared link and whether stored files are encrypted. Availability is whether that link and its video playback work when a buyer opens your proposal an hour before a decision meeting.
Processing integrity asks whether page views and time-on-page are recorded completely and accurately, so the analytics you act on aren't fiction. Confidentiality covers the contract or investor deck you've marked confidential. Privacy covers the viewer email addresses you collect and how long view-tracking data is retained before deletion.
Adding a criterion widens the audit and the evidence you must produce. Choose only the ones your commitments support.
A report listing only security isn't weaker by default. It depends on what the customer needs covered. A narrow, honest scope beats five categories you can't evidence.
Type I and Type II reports answer different questions
A Type I report answers a point-in-time question: were the controls suitably designed on a particular date? A Type II report also examines whether those controls operated effectively over a defined period. The distinction is like checking a building's safety plans on one day versus reviewing records of how those safeguards worked over time.
| Question | Type I | Type II |
|---|---|---|
| What it tests | Whether controls are suitably designed | Whether controls are designed and operated effectively |
| Time frame | A specific point in time | A defined observation period, commonly several months |
| Test results | No detailed test results | Auditor's tests and any exceptions are described |
| What a buyer learns | Controls existed on the audit date | The auditor examined whether controls operated effectively across the period, and gave an opinion |
| Typical use | Early milestone for a new product | Full assurance for procurement and security reviews |
The US Department of Labor guide to SOC 1 and SOC 2 examinations explains that a Type II report includes a detailed description of the service auditor's tests of controls and the results.
A vendor's report status also matters:
- Readiness work: No report has been issued. The vendor may be preparing for an examination, but there is no auditor's opinion to review.
- Examination in progress: The work has started, but no report or opinion is available yet.
- Type I report: An early report describing control design as of a specific date.
- Completed Type II report: A report covering control design and operation during a defined period, often requested in procurement and security reviews.
A Type II report is not a guarantee that every control worked perfectly. Read the exceptions to see what the auditor found and how the vendor responded. If time has passed since the report period ended, ask whether the vendor can provide a bridge letter, a management statement covering the gap.
How a SOC 2 audit runs from scoping to report
The system description works like a property survey. It marks the services, infrastructure, and vendors the auditor may test. Work outside that line never enters the opinion.
- Define the system boundary: Write the system description covering services, infrastructure, data flows, subservice organisations, and the commitments you've made to customers. This is the document everything else hangs from.
- Choose your criteria: Pick the categories that match those commitments. Security is always in. The rest are a choice you make with your auditor.
- Run a readiness assessment: Find missing policies and weak controls before the auditor arrives. Surprises during fieldwork are expensive.
- Implement and document controls: Access reviews, change management, logging and monitoring, incident response, vendor management, backups, and recovery testing. Documented and followed in practice, not only written down.
- Run the observation period: For Type II, controls operate for several months while you collect evidence as work happens. A control skipped one quarter becomes an exception.
- Auditor fieldwork: The auditor samples evidence, inspects configurations, and interviews staff. You'll get a request list and upload evidence against each control.
- Respond to exceptions: Management explains what went wrong and what you've fixed. Honest remediation reads better than a defensive paragraph.
- Report issued: You get the opinion and system description, and decide who receives it, usually under a non-disclosure agreement.
First-time reports usually take longer than renewals, and the biggest delays typically come from unclear scope and missing evidence rather than from the auditor. Slow down at step one. It saves months at step six.
Keeping SOC 2 controls working between audits
The evidence is the core product of SOC 2. Teams that collect it as a side effect of normal work pass audits calmly. Teams that rebuild it each year don't.
For a document and video platform, useful evidence includes:
- Quarterly access reviews: Exported from your identity system, with leavers removed and dates that match.
- Administrative change logs: Role changes, share-link permission changes, and who made them.
- Deletion requests: Logged with timestamps, so you can prove the data went.
- Alert delivery logs: Proof that notifications fired when they should have.
- Change tickets: For new features, such as adding a video storage region.
- Subprocessor reviews: Annual checks on hosting, email, and content delivery providers.
Logging needs three things
Define which events are worth recording. Protect the logs so they can't be edited. Keep them long enough to cover the whole observation period. Miss any one of those and the auditor can't test what happened.
Scope drift is the quiet killer. A new feature or vendor gets added and never mapped into the system description.
My rule: every new feature gets a short scope check before it ships, the same way you'd check how documents are stored securely before uploading anything sensitive. Reports are typically refreshed annually, so the routine is what keeps the report meaningful.
How SOC 2 compares with ISO 27001 and HIPAA
These three get mixed up constantly. SOC 2 is an attestation report about a chosen system. ISO 27001 is a certification of a management system. HIPAA is a US federal regulation with no certificate at all.
| Factor | SOC 2 | ISO 27001 | HIPAA |
|---|---|---|---|
| Who issues it | Independent CPA firm report | Accredited certification body issues a certificate | No certificate, enforced by HHS Office for Civil Rights |
| Type | Attestation report | Certification | Federal regulation with a Security Rule |
| Scope | Chosen system and selected Trust Services Criteria | Defined information security management system | Protected health information (electronic, paper and oral under the Privacy Rule; electronic under the Security Rule) held by covered entities and business associates |
| Validity | Report covers a period or date, usually refreshed annually | Certificate valid for three years with annual surveillance audits | Ongoing legal obligation with no expiry |
| Where it is most asked for | US enterprise procurement | International customers and public tenders | Healthcare and health-data work in the US |
Which one you need depends on who is asking
US enterprise buyers usually ask for SOC 2. International buyers and public tenders often ask for ISO 27001. If you're a HIPAA covered entity or business associate, you must meet HIPAA regardless of SOC 2, and a SOC 2 report alone doesn't satisfy it.
Many companies hold both SOC 2 and ISO 27001 because the controls overlap heavily, so one piece of evidence can often serve both audits.
GDPR sits alongside these rather than replacing them. It's a data protection law, not an audit framework. We set out our own position on our HIPAA page and GDPR page, which is how any vendor should explain it.
Why document and video platforms get asked about SOC 2
When you share a proposal, contract, or investor deck through a platform, you're handing over confidential material and trusting the vendor to protect it and track who viewed it. Knowing who opened what matters, and so does knowing the link won't break mid-deal.
For a document and video platform, the system in scope has to cover the file, the walkthrough beside it, open and page-view records, and any email address collected before viewing. A logo on the homepage does not tell you whether those pieces were in the report, or which dates the auditor tested.
Viewer emails and view-tracking data create real privacy obligations. Availability is concrete too. A broken link during a sales cycle ends the conversation you meant to start. Buyers who already follow guides to secure file sharing for business use ask whether those controls were examined, and for which period.
The AI question current reports don't answer well
A current report can show that documented controls operated during its period and still say little about an AI feature added after that period closed. The AICPA proposal to update the Trust Services Criteria would bring AI governance into the criteria, including model monitoring, prompt manipulation, data poisoning, transparency of AI-generated outputs, training-data management, and automated-decision risks. Until those updates apply to the engagement you are reading, the report may not speak to them at all.
Ask the vendor directly, in writing:
- Training use: Are uploaded documents or videos used to train models?
- Admin control: Can administrators disable AI processing?
- Derived data: Are transcripts and summaries covered by retention and deletion rules?
Check the report and its scope before you trust a vendor
Start with the full report, not a badge or summary PDF. Ask for it under a non-disclosure agreement, then check it in this order:
- Report type and period: Type I or Type II, and does the observation period end recently?
- Auditor's opinion: Is it unqualified, or qualified or adverse? Read this before relying on the report.
- System description: Does it cover document storage, video delivery, view analytics, email capture, access controls, deletion, and subprocessors?
- Exceptions and management responses: Where did the auditor find gaps, and did the vendor fix them?
- Complementary user entity controls: Your jobs, such as managing your own user accounts and link settings.
- AI and data use: Put those questions to the vendor in writing.
A vendor that refuses to share the report under an NDA is telling you something. For broader context, our guide to security compliance requirements for vendors covers what to request across regimes. We list SOC 2 (AICPA SOC) and ISO 27001 on our security page, which is where I'd start. Ask for the report itself and check the scope and dates before the deal goes further, as you would with any vendor.
Frequently asked questions about SOC 2 compliance
Does SOC 2 compliance mean a company is secure
No. It's an independent examination of the controls inside one defined system over one period. It shows what was checked and how those controls performed, not a guarantee that nothing will go wrong. The system description tells you what the examination covered.
Is SOC 2 a legal requirement
No, it's voluntary. Enterprise contracts and procurement teams often require it anyway, which makes it mandatory in practice for many vendors. HIPAA is different. That's a US law that applies whether or not a company holds a SOC 2 report.
How long is a SOC 2 report valid
A report speaks for the period or date it covers rather than expiring on a fixed day. Most vendors refresh it annually so coverage stays continuous. If the observation period ended more than a year ago, ask for a bridge letter or a newer report before you rely on it.
---
If you're sending proposals, contracts, or investor decks that need protecting and tracking, LiveDocument lets you add a video walkthrough to a PDF or image, share it as one tracked link, and see who viewed it. Judge us by the scope of our controls, not by a logo.
About the Author
Cameron JamesCameron is the founder of LiveDocument. He writes about sharing documents, PDFs, decks and contracts, and why pairing a video walkthrough with a document beats sending it cold.