Sooner or later, a customer will ask your organization for a "SOC report." For a first-timer, the follow-up questions come fast: SOC 1 or SOC 2? Type 1 or Type 2? Which Trust Services Criteria? This guide explains the options in plain language so you can choose with confidence.
What is a SOC report?
A System and Organization Controls (SOC) report is an independent CPA firm's report on the controls at a service organization — a company that provides services to other organizations. SOC reports are issued under attestation standards established by the American Institute of Certified Public Accountants (AICPA), and the examinations must be performed by a licensed CPA firm.
SOC reports exist so that each of your customers doesn't need to audit you individually. One examination, shared under appropriate terms, answers many customers' questions at once.
SOC 1: controls relevant to financial reporting
A SOC 1 report covers controls at a service organization that are relevant to its customers' internal control over financial reporting (ICFR). It's designed for your customers' management and their financial statement auditors.
You likely need a SOC 1 if your services directly affect the numbers in your customers' financial statements — for example, payroll processing, claims administration, loan servicing, investment management, revenue or billing platforms, or outsourced accounting.
In a SOC 1, management defines control objectives (for example, "controls provide reasonable assurance that payroll is processed completely and accurately") and the controls that achieve them. The auditor tests those controls.
SOC 2: security and the Trust Services Criteria
A SOC 2 report covers controls related to one or more of the AICPA's Trust Services Criteria (TSC):
| Category | What it addresses |
|---|---|
| Security (required) | Protection against unauthorized access, use or modification |
| Availability | Systems are available for operation and use as committed |
| Processing integrity | Processing is complete, valid, accurate, timely and authorized |
| Confidentiality | Information designated as confidential is protected |
| Privacy | Personal information is collected, used, retained and disposed of appropriately |
Every SOC 2 includes the Security category (the "common criteria"). The other categories are optional; include them when they match commitments you make to customers. Many SaaS companies add Availability, and companies handling sensitive customer data often add Confidentiality.
SOC 2 reports are intended for customers and prospects who understand the system and its controls, so they're typically shared under a nondisclosure agreement.
SOC 3: the public summary
A SOC 3 report covers the same Trust Services Criteria as a SOC 2 but omits the detailed description of tests and results. It's a general-use report you can share freely or post on your website. A SOC 3 is a useful marketing and trust signal, but security-minded customers will usually still ask for the SOC 2.
Type 1 vs. Type 2
SOC 1 and SOC 2 reports come in two types:
- A Type 1 report evaluates whether controls are suitably designed and implemented as of a specific date.
- A Type 2 report also evaluates whether controls operated effectively over a period of time, commonly 6 to 12 months.
Type 2 reports provide much stronger assurance, and most enterprise customers ask for them. A Type 1 can still be valuable as a first step: it demonstrates progress while you build the operating history a Type 2 requires.
How to decide which report you need
Start with three questions:
- Who is asking, and why? If the request comes from a customer's controller or external auditor, they probably need a SOC 1. If it comes from a security or procurement team, they probably need a SOC 2.
- What do your contracts promise? If you commit to uptime, include Availability. If you handle confidential data, consider Confidentiality.
- When do you need it? If a deal depends on having something soon, a Type 1 followed by a Type 2 may be the right path.
When in doubt, ask the requesting customer exactly what they need. It's common for organizations to over-scope their first report.
What the process looks like
A typical first SOC 2 follows four stages:
- Scoping: define the system, services, locations and Trust Services Criteria, and identify subservice organizations such as your cloud provider.
- Readiness: assess current controls against the criteria and remediate gaps.
- Examination: the CPA firm tests design (Type 1) or design and operating effectiveness over the review period (Type 2).
- Reporting: the CPA firm issues the report, including management's description of the system and the auditor's opinion.
A note on independence
The CPA firm that issues your SOC report must be independent. Readiness assessments are common and valuable, but the auditor can't design or operate your controls for you. Good firms are clear about where that line is — and help you get ready without crossing it.
The bottom line
Choose the report that answers the question your customers are actually asking: SOC 1 for financial reporting, SOC 2 for security and related commitments, SOC 3 for a public trust signal. Plan for a Type 2, scope carefully, and treat the report as the visible result of a security and controls program that runs all year.