Key takeaways
- SOC 1 and SOC 2 are AICPA attestation reports on a service organisation's controls, issued by an independent CPA firm. Neither is a certification.
- SOC 1 covers controls relevant to customers' internal control over financial reporting and is performed under AT-C section 320, one of the sections created by SSAE No. 18.
- SOC 2 covers security, availability, processing integrity, confidentiality and privacy, measured against the AICPA Trust Services Criteria (2017, points of focus revised in 2022).
- Type 1 and Type 2 mean the same in both families: design at a date, or design plus operating effectiveness over a period with the auditor's tests and results.
- SOC 1 is read by customers and their financial statement auditors, SOC 2 by specified parties such as the customer's security and procurement teams.
- Outside the US, ISAE 3402 from the IAASB covers the same subject as SOC 1. SOC 3 is the general use version of SOC 2.
SOC 1 and SOC 2 are AICPA attestation reports issued by an independent CPA firm on a service organisation's controls. SOC 1 covers controls relevant to customers' internal control over financial reporting. SOC 2 covers security, availability, processing integrity, confidentiality and privacy, against the Trust Services Criteria. Service feeds customers' accounts: SOC 1. Service handles their data: SOC 2.
Both reports come in a Type 1 and a Type 2 version, both have a restricted readership, and neither is a certification. What separates them is the subject matter, the yardstick the auditor uses and the person who reads the report on the customer's side. For a European company the request usually comes from a US customer, so the useful question is not which report is better, but who asked for it and what they will do with it.
What a SOC 1 report covers
The AICPA describes SOC 1 as an examination of controls at a service organisation that are likely to be relevant to user entities' internal control over financial reporting. The report is written for two readers: the customers that use the service (user entities, in AICPA terms) and the CPAs who audit those customers' financial statements (user auditors).
The typical SOC 1 candidate runs a process whose output ends up in someone else's accounts. The Journal of Accountancy, the AICPA's magazine, gives payroll processing and medical claims processing as traditional examples. For a European provider the same logic applies to outsourced payroll, billing, payment or transaction processing and fund administration delivered to US clients.
On the standards side, the AICPA's SOC 1 guide states that the examination is performed under AT-C section 320 of the attestation standards. The AT-C sections were created by SSAE No. 18, the clarified attestation standards issued by the AICPA Auditing Standards Board and effective for reports dated on or after 1 May 2017. That is why SOC 1 is often called an SSAE 18 report: SSAE 18 is the standard, SOC 1 is the report.
The yardstick in SOC 1 is a set of control objectives included in the service organisation's description of its system. The auditor gives an opinion on whether the controls are suitably designed to achieve those objectives and, in a Type 2, whether they operated effectively.
The international counterpart: ISAE 3402
Outside the US the same ground is covered by ISAE 3402, Assurance Reports on Controls at a Service Organization, released by the International Auditing and Assurance Standards Board (IAASB) in December 2009 and effective for service auditors' reports covering periods ending on or after 15 June 2011. The IAASB's staff overview places it on controls likely to be relevant to user entities' internal control as it relates to financial reporting, the same subject as SOC 1. If your customers and their auditors are European, ask whether they expect an ISAE 3402 report rather than a SOC 1.
What a SOC 2 report covers
SOC 2 looks at controls relevant to the security, availability or processing integrity of the systems a service organisation uses to process customers' data, and to the confidentiality and privacy of the information those systems process. The Journal of Accountancy (February 2026) describes it as giving a level of detail sufficient for the customer's vendor risk management needs.
Here the yardstick is set by the AICPA, not by the service organisation: the Trust Services Criteria, established by the AICPA's Assurance Services Executive Committee (ASEC). The AICPA's SOC 2 guide applies the 2017 Trust Services Criteria (with revised points of focus, 2022) to the controls and the 2018 description criteria (with revised implementation guidance, 2022) to the system description. ASEC has also published exposure drafts of proposed 2027 Trust Services Criteria and description criteria, so the reference set is under review.
The five categories are security, availability, processing integrity, confidentiality and privacy. Security is the base of every SOC 2, and the others are added when they matter for the service you provide. Our guide to what SOC 2 is and how Type I and Type II work goes through each one.
SOC 2 has a sibling for public use. SOC 3 addresses the same categories with less detail, which is why the AICPA treats it as a general use report that can be freely distributed. A SOC 2 report, by contrast, is restricted to specified parties with enough knowledge of the system and the service to read it.
SOC 1 Type 2 vs SOC 2 Type 2
This is where most of the confusion sits, because Type means the same thing in both families. A Type 1 report covers the description of the system and the suitability of the design of controls as of a specified date. A Type 2 report adds an opinion on operating effectiveness throughout a specified period, and includes a description of the auditor's tests of controls and their results.
So a SOC 1 Type 2 and a SOC 2 Type 2 share the same shape: a period, tests, results and any exceptions. They differ in three ways:
- What is tested. SOC 1 Type 2 tests controls against the control objectives relevant to financial reporting. SOC 2 Type 2 tests controls against the Trust Services Criteria you have put in scope.
- Who reads it. SOC 1 goes to the service organisation's management, its customers and the auditors of their financial statements. SOC 2 goes to specified parties, in practice the customer's security, risk and procurement teams.
- What it answers. SOC 1 tells the customer's auditor whether your service can be relied on in the financial statement audit. SOC 2 tells the customer whether your service handles systems and data in a way it can accept in its supplier review.
The length of the period is agreed with the auditor. If a customer asks for a Type 2, ask which period they expect it to cover before you plan the work, because the report can only be issued once that period has ended.
Which one does your company need?
Start from the person who asked, not from the report:
- Your service affects the figures in customers' accounts (payroll, billing, payments, transaction or claims processing, fund administration): the request is most likely for SOC 1, and it often comes from the customer's finance team or external auditor.
- Your service stores or processes customers' data (SaaS, hosting, managed IT or security services): the request is most likely for SOC 2, and it comes from the customer's security or procurement team during a vendor review.
- Both are true: some providers need both reports. A payroll platform is the classic case, where the customer's auditors want SOC 1 and its security team wants SOC 2. Scope and opinions are different, so one report does not stand in for the other.
- You want something public for your website: SOC 3, which uses the SOC 2 criteria in a general use report.
If the request is vague, for instance a questionnaire line asking for a SOC report, go back with two questions: which report, and which type. The answer keeps you from building the wrong scope.
What a SOC report is not
Neither SOC 1 nor SOC 2 is a certification. Both are attestation reports: a CPA firm gives an opinion on controls, and the report carries that opinion together with its scope and any exceptions. The Journal of Accountancy points out that compliance is a term never used in SOC 2 examinations, so a supplier describing itself as SOC 2 compliant is, in practice, saying it has a recent report to share.
For European buyers the usual reference is ISO/IEC 27001, a certification of the information security management system. The two overlap: the AICPA publishes a mapping of the 2017 Trust Services Criteria to ISO 27001, and a company selling on both sides of the Atlantic often plans them together (see our ISO 27001 services). If your customers are in scope of NIS2 or DORA, your SOC 2 report can feed into their supplier assessment, alongside the contract terms those laws push down the supply chain. Our guide to third-party risk management covers what they ask of suppliers.
Choosing the auditor
Only a CPA firm can issue a SOC report. The Journal of Accountancy (February 2026) reports concern within the profession about compliance tool vendors that market SOC 2 as fast and easy: most of them are not CPA firms and cannot attest to controls themselves, and some route examinations to networks of accounting firms. On its SOC page the AICPA states that it is looking into anonymously published allegations about the business practices of one such vendor, and that it will act where auditors have not followed professional standards, are not enrolled in peer review or are unlicensed.
Before signing an engagement, check that the firm is licensed and enrolled in AICPA peer review, ask about the size and capacity of the team that will work on your examination, and ask for client references. A compliance platform can shorten the evidence collection; the opinion still comes from the auditor.
AmagisTech helps European companies prepare for SOC 2 and work out whether a customer's request calls for SOC 1, SOC 2 or both, before the scope is fixed. If a US customer has asked you for a report, start from our SOC 2 services.
