Is SOC 2 Mandatory? Who Actually Requires It
No general U.S. law requires a SOC 2 report. Learn where the requirement really comes from, when a contract makes it binding, and what to check before you sign.

No general U.S. law requires a company to have a SOC 2 report. SOC 2 is an examination a CPA firm performs under AICPA standards, and no federal regulator fines you just for not having one. A customer’s procurement rule or security review can make SOC 2 a condition of the deal, and a contract clause you sign makes it binding. Many of those customers ask because their own regulators make them check their vendors. So the useful question for a startup is “who is asking, what will they accept, and what did we agree to?” This guide shows where the requirement comes from, when it becomes binding, and what to check before you promise a report.
TL;DR
- No U.S. law or regulation covered here names a SOC 2 report as something a company must have.
- Customers set the requirement. Regulated customers often ask because their rules make them oversee vendors, and a SOC 2 report is one common way to show that.
- A signed contract clause that requires a SOC 2 report makes delivery your obligation. Read the report type, date, and remedy before you sign.
- Ask whether the customer accepts something else for now, such as a questionnaire, a Type 1 report, or a dated plan.
- Do not call the company “SOC 2 compliant” or “SOC 2 certified.” Say whether a report exists, its type, scope, and date or period.
Is SOC 2 required by law?
SOC 2 is part of the AICPA’s System and Organization Controls suite, which describes reports CPAs provide about controls at service organizations. The AICPA sets the standards the CPA firm follows. It does not require any company to get a report, and it does not penalize a company that has none.
The rules and guidance below show how regulation reaches SOC 2 in practice. Banks and financial firms must oversee their providers based on risk, and HIPAA requires business associate agreements. None of them names a SOC 2 report as the required proof:
| Rule or guidance | Who it applies to | What it requires about vendors | Does it name SOC 2? |
|---|---|---|---|
| FTC Safeguards Rule, 16 CFR 314.4(f) | Financial institutions under FTC jurisdiction | Select capable providers, require safeguards by contract, and periodically assess providers based on risk | No |
| SEC Regulation S-P, 17 CFR 248.30(a)(5) | Broker-dealers, funding portals, investment companies, registered advisers, and transfer agents | Oversee service providers through due diligence and monitoring, with policies reasonably designed to ensure providers give notice within 72 hours | No |
| Interagency Guidance on Third-Party Relationships (2023) | Banking organizations supervised by the Federal Reserve, FDIC, or OCC (guidance, not a rule) | Risk-based due diligence, contracts, and ongoing monitoring of third parties | Says a bank “may consider reviewing” SOC reports, as one option |
| HIPAA Security Rule | Covered entities and business associates | Safeguards and business associate agreements | No, and HHS does not recognize private certifications |
| FedRAMP | Federal agencies using cloud services | Follow FedRAMP’s authorization process | No. FedRAMP is its own program, separate from SOC 2 |
This table is a set of examples, not a survey of every law. If your buyer works in a regulated field, ask which rule drives its vendor review, and ask your own counsel when a legal duty may apply to your company directly.
Where the requirement actually comes from
The requirement starts with a customer. It shows up in one of four places, and each carries different weight:
| Source | Example | Is it binding on you? |
|---|---|---|
| A sales conversation | “Do you have SOC 2?” on a discovery call | No. It is a question to clarify |
| The customer’s procurement or vendor rules | “Vendors with access to customer data must provide a SOC 2 Type 2” | Not on you, but it can block the deal |
| A security questionnaire | A question asking for your latest SOC 2 report | Not by itself, but answers are often attached to the contract. Answer truthfully, including “not yet” |
| A signed contract | “Vendor will provide a SOC 2 Type 2 report within 12 months” | Yes. You agreed to it |
Write down which one you are facing, with the exact wording. A loose question on a call does not need the same response as a signed clause with a date. The first-response guide for a customer SOC 2 request covers what to ask before you commit to anything.
Why regulated customers ask for SOC 2
Regulated financial customers have to show their examiners or regulators that they checked their vendors. A SOC 2 report from an independent CPA firm gives them a document they can file for that review.
The bank guidance is the clearest example. The Interagency Guidance on Third-Party Relationships says that, when relevant and available, a bank may consider reviewing SOC reports during due diligence, and that contract terms may describe the types and frequency of audit reports the bank can receive. That wording is “may consider,” not “must obtain.” The same passage also mentions other independent certifications and assessments. In practice, banks also send questionnaires, and the guidance keeps the bank responsible for the decision.
The FTC Safeguards Rule at 16 CFR 314.4(f) tells covered financial institutions to select capable service providers, require safeguards by contract, and periodically assess providers based on risk. The amended SEC Regulation S-P at 17 CFR 248.30 requires covered firms to oversee service providers through due diligence and monitoring, with policies reasonably designed to ensure providers give notice no later than 72 hours after becoming aware of a qualifying breach.
Notice what those rules ask the customer to get from you: proof of safeguards, contract terms, and in Regulation S-P’s case a notification promise. A SOC 2 report helps with the first. It does not replace the contract terms, so expect the security addendum to arrive with the report request.
Healthcare works differently. HHS says no Security Rule standard requires a covered entity to certify compliance, and that it does not recognize private organizations’ certifications. A hospital may still ask for your SOC 2 report, but the report does not settle your HIPAA duties. The SOC 2 versus HIPAA guide separates the two.
Federal agencies use a different program again. FedRAMP says agencies are required by law and OMB policy to follow its process when they use cloud services. A SOC 2 report does not stand in for what FedRAMP now calls certification, or for an agency’s authorization to operate.
When SOC 2 becomes mandatory for your company
SOC 2 becomes your obligation when you sign a contract that requires it. After that, the clause decides what you owe, so read it like an engineer reads an API contract. Check each term:
| Clause term | What to check | Safer wording to ask for |
|---|---|---|
| Report type | Type 1 or Type 2. Type 2 needs an operating period before the report | Type 1 by a date, then Type 2 after the first period |
| Deadline | A fixed date, or a period after the contract starts | A date you planned backward from CPA availability and the evidence period |
| Scope | Which product, service, or system the report must cover | The service this customer actually buys |
| Criteria | Security only, or also Availability, Confidentiality, or others | The categories that match what you promise the customer |
| Frequency | One report, or “annually” or “at all times” | A report each year, plus a bridge letter between periods |
| Equivalents | Whether ISO/IEC 27001 or another independent assessment counts | “SOC 2 Type 2 or an equivalent independent assessment” |
| Remedy | Termination right, fee credit, or breach of contract if the report is late | Notice and a cure period before termination |
| Exceptions | Whether a report with exceptions or a modified opinion still satisfies the clause | Delivery of the report plus a written plan for any exceptions |
The deadline and the report type decide whether the clause is possible to meet. A Type 2 report covers a period, so a clause that asks for a Type 2 within three months of signing may be impossible for a company that has not started. The Type 1 versus Type 2 guide and the timeline guide help you set a date you can meet. Have counsel review the remedy and liability terms. This guide is not legal advice.
Read the rest of the security addendum too
The SOC 2 clause usually sits next to other promises: breach notification windows, encryption, data deletion on termination, subprocessor notice, or uptime. Those promises matter twice. You must keep them, and the AICPA’s description criteria (DC 200) say service commitments may be communicated through contracts, service-level agreements, and published policies. Your system description discloses the principal ones, and the CPA firm’s opinion covers whether your controls provide reasonable assurance that you meet them, based on the criteria in scope. A promise you cannot keep today can become an exception or a scoping problem later.
What to do when nobody requires it yet
If no customer has asked, or the only signal is a question on a sales call, you can wait. Use the startup decision guide to decide whether to start now, and keep doing the security work the service needs anyway: access control, change review, backups, logging, incident response, and vendor oversight. Keep the records those processes create, because a later Type 2 period cannot use history you did not record.
When a buyer asks before you have a report, answer what is true today. The security questionnaire guide shows how to answer from current systems, name gaps, and agree on a next step. Ask whether the buyer will accept a questionnaire, a call with an engineer, or a dated plan for a first report.
Cost matters too. The SOC 2 cost guide breaks out CPA fees, team time, tools, and remediation, so you can compare the cost with the deal that depends on it.
Claims to avoid while SOC 2 is optional
These shortcuts cause trouble later, often in the same contract that asks for the report:
- “We are SOC 2 compliant.” Say instead whether a CPA firm has issued a report, and give its type, scope, and date or period.
- “We are SOC 2 certified.” SOC 2 is an attestation report, not a certification. The CPA firm issues an opinion.
- “Our cloud provider has SOC 2, so we are covered.” The provider’s report covers the provider’s controls. The cloud provider SOC 2 guide explains what it does and does not cover for your product.
- “We will have it in 90 days.” Do not promise a date before you know the report type, the CPA firm’s schedule, and how much remediation you need.
Track contract promises in FileGRC
FileGRC is an open source, Git-native GRC workspace for SOC 2 work. JSON
holds structured records, Markdown holds long-form work, and Git supplies the
change history. It has a commitment record type for customer promises,
service requirements, and approved business objectives, linked to the Systems
and Controls that keep them.
When a customer contract adds a security promise, record it before you rely on
it. This example records a 72-hour incident notice from a customer agreement
and links it to the starter incident response control, which is a proposal
you tailor to how your team actually responds. Start in a workspace
created with npx create-filegrc@latest, and run every step in the same
terminal session, because later commands reuse $mutation_dir:
mutation_dir="$(umask 077; mktemp -d)"
npx filegrc scaffold commitment \
--title "Notify Acme of security incidents within 72 hours" \
> "$mutation_dir/commitment.json"
The scaffold leaves required fields empty. Fill them in before you preview. Match the trigger and deadline to your contract exactly, because “after becoming aware” and “after confirming” start the clock at different times. Paraphrase the rest and cite the clause number. Quote contract text only when the agreement’s confidentiality terms allow it, and keep the signed copy in the system that already holds it. If the agreement also keeps the customer relationship confidential, use an internal customer code instead of the name in the ID, title, and statement:
{
"record": {
"id": "commitment-notify-acme-of-security-incidents-within-72-hours",
"type": "commitment",
"title": "Notify Acme of security incidents within 72 hours",
"status": "active",
"effectiveOn": "2026-11-01",
"commitmentKind": "service",
"statement": "Notify Acme in writing as soon as possible and no later than 72 hours after becoming aware of a security incident that affects Acme data, per section 9.2 of the Acme MSA.",
"ownerIds": ["person-program-lead"],
"customerFacing": true,
"controlIds": ["control-incident-response"]
}
}
This example records a signed clause, so it is active from the contract’s
effective date. For a clause still under negotiation, use planned, leave out
effectiveOn, and leave the open applicability finding in place until the
contract is signed. Then switch it to active and record the applicability
review below. That way an agent or reviewer can tell which promises are in
force. If you stop before the last step, or a command fails, run
rm -rf "$mutation_dir" so the draft does not stay in your temp folder.
Next, preview the change, create it, and check the workspace:
npx filegrc preview-mutation "$mutation_dir/commitment.json"
npx filegrc create "$mutation_dir/commitment.json"
npx filegrc validate
The preview reports one added finding: the new commitment needs an
applicability review. Scaffold the review into the same folder and fill in
reviewedByIds, reviewedOn, and a rationale. Set decision to
applicable, or to not-applicable, externally-managed, or
zero-population when that is true. The scaffold lists every commitment that
still needs review, so remove entries you are not reviewing now. Then preview
and apply it:
npx filegrc review-applicability --scaffold --type commitment \
> "$mutation_dir/applicability.json"
npx filegrc review-applicability "$mutation_dir/applicability.json" --preview
npx filegrc review-applicability "$mutation_dir/applicability.json" --yes \
&& rm -rf "$mutation_dir"
Add systemIds once you have a System record for the service. Use the
record’s Markdown for context and a pointer to the signed contract, not for
the contract itself.
The CLI writes files but does not commit them, so review the diff before you commit. With the promises in the repository, an agent can list every customer-facing commitment, check which ones link to a control, and draft a security addendum review that flags promises with no control behind them. A person still decides whether to accept the clause.
FileGRC does not tell you whether SOC 2 is required, negotiate contracts, or decide whether a control meets a promise. Your team operates the controls in your source systems. An independent CPA firm performs the SOC 2 examination and issues the report.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Is SOC 2 required by law?
No general U.S. law requires a company to have a SOC 2 report. SOC 2 is an examination a CPA firm performs under AICPA standards, not a statute or a regulation. Banks, FTC-covered financial institutions, and firms covered by SEC Regulation S-P must oversee their service providers, and HIPAA covered entities must sign business associate agreements with vendors that create, receive, maintain, or transmit protected health information on their behalf. Many of them ask vendors for a SOC 2 report as part of that work, but the 2023 interagency guidance for banks (which lists SOC reports as one option), the FTC Safeguards Rule, SEC Regulation S-P, and HIPAA do not name a SOC 2 report as the required proof.
Who requires SOC 2?
Customers and business partners do. A customer or partner can make a SOC 2 report a condition of the deal through its procurement policy or security review, or make it binding through a signed contract. Customers in regulated industries often ask because their own rules make them check their vendors. Once you sign a contract clause that requires a report, delivering it becomes your contractual obligation.
Is there a penalty for not having SOC 2?
Neither federal regulators nor the AICPA fine a company just for not having a SOC 2 report. The cost is commercial: a lost or delayed deal, a failed renewal, or a breach of a contract clause you already signed. Read the remedies in that clause, such as a termination right, before you agree to a report date.
Does a contract make SOC 2 mandatory?
Yes, for you, once you sign it. A clause such as "Vendor will provide a SOC 2 Type 2 report within 12 months" makes delivery a contractual obligation. Before signing, check the report type, deadline, scope, criteria, frequency, whether an equivalent assessment counts, and the remedy if the report is late. Have counsel review the remedy and liability terms.
Do banks and fintech customers require SOC 2?
Their regulators require them to manage third-party risk, and the 2023 interagency guidance for banks says a bank may consider reviewing SOC reports during due diligence. That makes a SOC 2 report a common request from financial customers, but the bank decides what evidence it accepts. Non-bank fintechs often fall under the FTC Safeguards Rule or SEC Regulation S-P, and some also face state rules or bank-partner contracts. The federal rules require service-provider oversight but do not name a SOC 2 report. Ask what the customer will take if you do not have a report yet.
Do federal agencies require SOC 2?
Not as a rule. For cloud services, federal agencies follow FedRAMP, a separate federal program with its own assessment and authorization process. FedRAMP says agencies are required by law and OMB policy to follow its process. A SOC 2 report does not stand in for FedRAMP, so ask the agency which program and level apply to your service.