Flamingo Raises $4.5M Seed Round

Skip to content

What is SOC compliance? SOC 1 vs SOC 2 vs SOC 3 explained

Aliaska VarievaAliaska Varieva
November 9, 2026
9 views
What is SOC compliance? SOC 1 vs SOC 2 vs SOC 3 explained

What SOC compliance means under the AICPA framework, who reads SOC 1, SOC 2 and SOC 3 reports, Type 1 vs Type 2, bridge letters, SOC for Cybersecurity and SOC 2+, 2026 audit costs and timelines, and which SOC report an MSP needs as a provider and as a buyer.


Updated: November 2026

A client asks for "your SOC report," a vendor sends you one, and three different documents all go by the same three letters. SOC compliance means a licensed CPA firm has examined a company's controls under the AICPA's System and Organization Controls framework and issued a SOC 1, SOC 2 or SOC 3 report. This guide shows who each report is for, what Type 1 and Type 2 mean, what they cost in 2026, and which one an MSP needs from both sides of the table.

TL;DR

  • The definition. SOC compliance means holding a current AICPA SOC report signed by an independent CPA firm.
  • SOC 1. Controls behind a client's financial statements, read by their auditors.
  • SOC 2. Security controls, read by client security teams under NDA.
  • SOC 3. A public summary of a SOC 2 Type 2.
  • Type 1 vs Type 2. One date versus months of tested operation.
  • For MSPs. Clients want your SOC 2 Type 2.

What is SOC compliance

Quick fork first: this post is about audit reports, not the security operations center that watches alerts around the clock (that SOC lives in our SOC as a service guide).

SOC stands for System and Organization Controls. It's a family of attestation reports owned by the AICPA, the body that sets standards for US CPAs. A service organization hires a licensed CPA firm. The firm examines the controls, tests them, and writes an opinion.

Two things trip people up. First, there's no such thing as "SOC certified." You don't get a certificate. You get a report with an auditor's opinion in it, and the report expires in practice after about a year. Second, no law requires one. Customers do. A SOC report is how a vendor answers "why should we trust you with this?" once, instead of answering every security questionnaire from scratch.

The numbers in SOC 1, SOC 2 and SOC 3 aren't levels. You don't graduate from SOC 1 to SOC 2. Each report answers a different question for a different reader, which is the part generic explainers skip.

The AICPA SOC framework and who each report is for

Start with the reader, not the report. Ask who's going to open the PDF, and the right report usually picks itself.

SOC 1 is for your client's financial auditors. It's performed under the AICPA's SSAE 18 attestation standard (section AT-C 320) and covers controls relevant to a client's internal control over financial reporting, or ICFR. The readers are the client's controller and the CPAs who audit their books. If the client is public, those auditors use a SOC 1 Type 2 as evidence for SOX 404 testing, so they don't have to test your controls themselves. Payroll processors, claims administrators, fund administrators and hosting providers that run a client's ERP all get asked for one.

SOC 2 is for your client's security team. It reports on controls against the AICPA's Trust Services Criteria: Security (always in scope), plus Availability, Processing Integrity, Confidentiality and Privacy if you choose them. The reader is a security or vendor risk reviewer. Distribution is restricted to people who understand the system, which is why vendors share it under NDA. Our SOC 2 guide for MSPs goes deep on the five criteria, readiness and the audit itself, so this post won't repeat it.

SOC 3 is for everyone else. It's built from the same examination as a SOC 2 Type 2, but it strips out the detailed system description and the test results. What's left is the auditor's opinion, management's assertion and a short overview. It's general use, so you can post it on your trust page. Per BD Emerson (August 2026), a SOC 3 is derived only from a Type 2, and there's no SOC 3 for a Type 1.

SOC 1 vs SOC 2 vs SOC 3 compared

SOC 1SOC 2SOC 3
Question it answersCan our auditors rely on your controls for our financials?Do you protect our data and systems?Can you show the public you passed a SOC 2?
FrameworkSSAE 18, AT-C 320, control objectives you defineTrust Services Criteria, Security plus optional fourTrust Services Criteria
Primary readerClient controller and external financial auditorsClient security, IT and vendor risk teamsProspects, the public, procurement
DistributionRestricted to clients and their auditorsRestricted, shared under NDAGeneral use, post it anywhere
Test details includedYesYesNo, opinion and summary only
Type 1 availableYesYesNo, Type 2 basis only
Typical 2026 audit fee$20K to $40K (Type 1), $30K to $60K (Type 2)$15K to $45K Type 2 at specialist firms$2K to $8K added to a SOC 2
Who asks MSPs for itClients whose financial systems you host or runNearly every security questionnaireProspects early in a deal

Fee sources are in the cost section below. A company can hold more than one. A payroll SaaS often carries a SOC 1 for its customers' auditors and a SOC 2 for their security teams, covering the same system from two angles.

Type 1 vs type 2

Both SOC 1 and SOC 2 come in two types. The difference is time.

A Type 1 report tests whether controls are designed properly as of one date. It's a photo. A Type 2 report tests whether those controls operated effectively across a review period, usually 3, 6 or 12 months. It's the film. The auditor samples evidence from across the whole window, so every missed access review or unlogged change during those months can show up as an exception.

Buyers almost always want Type 2. A Type 1 is useful as a first step when a deal can't wait, or to prove the design before the observation window starts. Per SOC2Auditors (October 2026), a SOC 2 Type 1 takes about 3 to 6 months end to end, and a first Type 2 takes about 6 to 12 months or more.

The hard part of Type 2 is rarely the controls. It's proving they ran, month after month. This r/Compliance thread from March 2026 sums it up: the team passed, nothing was missing, and finding the proof in PRs, screenshots and Slack was the painful bit.

Bridge letters cover the gap between reports

A Type 2 period ends on a fixed date, and the report lands weeks later. So there's always a gap between the end of the last tested period and today. A bridge letter (also called a gap letter) fills it.

The service organization's management signs it, not the auditor. It states that controls kept operating as described since the period ended, or lists material changes and incidents. Per BD Emerson (July 2026), a bridge letter carries no independent assurance, three months of gap is routine, and six is occasionally accepted. Past that, vendor risk teams ask for a new report.

SOC for cybersecurity and SOC 2+

Two more members of the family come up often enough to know by name.

SOC for Cybersecurity reports on an organization's whole cybersecurity risk management program, not one service. Any organization can get one, not just service providers. Management describes the program across nine areas, from governance to monitoring. The auditor tests controls against a baseline the company picks, such as the Trust Services Criteria, NIST CSF or ISO 27001. It's general use, so it suits boards, investors and insurers. Schellman (updated March 2026) still calls it "pretty new," and it's rare in MSP deals.

SOC 2+ is a SOC 2 with additional subject matter tested in the same report. Common add-ons are HIPAA Security Rule requirements, NIST CSF, ISO 27001 controls, HITRUST and the CSA Cloud Controls Matrix for CSA STAR. One examination answers several questionnaires. The catch: a SOC 2+ mapped to ISO 27001 is not an ISO certification, and one mapped to HITRUST isn't HITRUST certification either. If the client needs the certificate, you still need that separate audit. For where these frameworks sit relative to each other, see our cybersecurity frameworks list.

The AICPA also launched SOC for Supply Chain in 2020, for companies that make or distribute products. It doesn't apply to IT services.

What SOC reports cost and how long they take in 2026

Audit fees are only part of the bill. Readiness work, tooling and staff hours usually cost more than the auditor. The ranges below are the audit fee alone, from published 2026 planning estimates.

ReportAudit fee, 2026TimelineSource
SOC 1 Type 1$20K to $40KFirst report 2 to 6 months from kickoffBD Emerson, Oct 2026
SOC 1 Type 2$30K to $60K6 to 12 month period, report 4 to 8 weeks afterBD Emerson, Oct 2026
SOC 2 Type 1$10K to $24K specialist, $40K to $145K Big FourAbout 3 to 6 months end to endSOC2Auditors, Oct 2026
SOC 2 Type 2$15K to $45K specialist, $65K to $200K Big FourFirst one 6 to 12+ monthsSOC2Auditors, Oct 2026
SOC 3$2K to $8K on top of a SOC 2 Type 2Issued with the Type 2BD Emerson, Aug 2026
SOC for CybersecurityQuoted per engagement, no common range publishedDepends on program scopeSchellman, Mar 2026

Sources: BD Emerson SOC 1 guide, SOC2Auditors cost data across 184 firms, BD Emerson SOC 3 guide. These are planning ranges, not quotes.

Scope drives the number more than anything. More Trust Services Criteria, more systems, more locations and a Big Four logo all push the fee up. The SOC 2 guide linked above breaks down the all-in first-year cost for an MSP, including readiness and staff time. And plan for it to recur. Clients expect a fresh Type 2 every year.

This 2025 explainer from Audit Decoded walks through all three reports in about six minutes:

Which SOC report does an MSP need

An MSP sits on both sides of this. Clients ask for your report, and you should be asking your vendors for theirs.

As the provider. Start with SOC 2 Type 2, scoped to Security plus whatever your contracts promise, usually Availability and Confidentiality. That's what security questionnaires and RFPs ask for. Add a SOC 3 for a few thousand dollars if prospects keep asking for something they can see before the NDA. Consider a SOC 1 only when you host or operate systems that feed a client's financial statements, such as a managed ERP or accounting environment for a company that gets audited. Their auditors may then ask for a SOC 1 covering your IT general controls (access, change management, backups, operations). A SOC 2+ with HIPAA makes sense when healthcare clients are a big slice of revenue. Pick the report by who's asking, not by the number.

As the buyer of vendors. Your RMM, PSA, backup, EDR and remote access tools can each reach every client you manage. The 2021 Kaseya VSA attack showed what that means: Kaseya counted about 60 of its direct customers, mostly MSPs, and fewer than 1,500 downstream businesses hit through one tool. So collect a SOC 2 Type 2 from every vendor with privileged access, and check these points before you file it:

  1. The product you use is inside the audited system, not a sister product with a similar name.
  2. The review period ended within the last 12 months, with a bridge letter covering the rest.
  3. Subservice organizations like AWS or Azure are usually "carved out," so get their reports too.
  4. The complementary user entity controls list what the vendor expects you to do, such as enforcing MFA on your own logins.
  5. A SOC 3 or a trust-page badge is fine for a first look, but it isn't enough for a tool with admin rights to client networks.

Point 4 is the one that bites. A vendor's clean report assumes you did your half. The SOC 2 guide covers how to read the exceptions and the auditor's opinion in detail.

One more lever: every tool in your stack is another system to evidence and another vendor report to chase. Fewer tools means a smaller audit scope. OpenFrame, Flamingo's platform, puts RMM, remote access and PSA into one open, AI-native platform, so there are fewer consoles to govern and fewer vendor reports to review. The data stays yours, which also makes the "where does client data live" question easier to answer in your own SOC 2.

This guide explains the SOC framework in general terms. It isn't legal or audit advice. Confirm scope and report type with your CPA firm and with the client asking for it.

The short version

Ask who'll read the report. Financial auditors get a SOC 1, security teams get a SOC 2, and the public gets a SOC 3. Buyers want Type 2, and a bridge letter only stretches it by a few months. As an MSP, earn a SOC 2 Type 2 and collect one from every vendor that can touch client networks.

Next, read the SOC 2 guide for MSPs for the audit itself. Same three letters, very different jobs.

Aliaska Varieva

Aliaska Varieva

VP of Engineering

Hi! I’m Aliaska, and I’ve been working as a software engineer (mostly Java + a bit Kotlin) for over 8 years now. I mostly spend my time building backend services, integrating systems, fixing bugs (the fun part 🙃), and making sure things don’t fall apart behind the scenes.

Related Content

Frequently Asked Questions

/blog/what-is-soc-compliance

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions