Compliance guide
SOC 2 compliance: what it is, Type 2 and how it compares to ISO 27001
SOC 2 is a report, not a certificate. A licensed accounting firm (a CPA firm) examines how a service company protects its customers' data against criteria set by the AICPA, an American accounting body, and writes a report the company can hand to customers. A Type 1 report evaluates controls "as of a specific date" (a CPA quoted by AICPA). AICPA's sample Type 2 report includes "tests of controls and results thereof". No EU or Swedish law requires SOC 2.
On this page
This is a plain-language summary, not legal or audit advice. SOC 2 is an American professional standard. The full criteria sit behind a free AICPA account, so this page only states what AICPA's public pages say. Ask your CPA firm for the rest.
1. In short
- SOC stands for System and Organization Controls. AICPA describes it as a suite of services that CPAs may provide about the controls of a service organization.
- A SOC 2 engagement is an "assertion-based examination" of a company's description of its system and its controls, judged against the AICPA Trust Services Criteria.
- The criteria have five categories: security, availability, processing integrity, confidentiality and privacy.
- The result is a report written by a CPA firm. AICPA calls SOC reports "assurance reports". It is not a certificate from a certification body.
- Customers often ask for it. NIS2, GDPR and Sweden's cybersecurity rules do not mention it.
2. What SOC 2 means
SOC stands for System and Organization Controls. AICPA, the American Institute of CPAs, describes SOC as "a suite of service offerings CPAs may provide in connection with system-level controls of a service organization or entity-level controls of other organizations". A service organization is a company that runs a service for other companies, such as a software, hosting or payroll provider.
The number names the type of report. AICPA's course description for CPAs gives the split:
| Report | What it covers, in AICPA's words |
|---|---|
| SOC 1 | Controls that affect "internal control over financial reporting". |
| SOC 2 | "Controls related to information privacy, security, confidentiality, availability, and processing integrity." |
| SOC 3 | The same subjects as SOC 2. AICPA describes SOC 3 as a "general use report", with less detail than SOC 2 and meant to be freely distributed. |
AICPA also publishes other SOC services, such as SOC for Supply Chain. That one is separate from SOC 2.
Changing criteria. On 16 November 2026 AICPA posted exposure drafts of proposed 2027 changes to the SOC 2 Trust Services Criteria and the description criteria. A draft is not final. Ask your CPA firm which version your report will use.
3. The five categories
The criteria are called the Trust Services Criteria. AICPA says they were "established by the AICPA's Assurance Services Executive Committee (ASEC) for use in attestation or consulting engagements to evaluate and report on controls over the security, availability, processing integrity, confidentiality, or privacy of information and systems". The current set is the 2017 criteria with revised points of focus (2022).
The middle column is a plain-words reading for this page. It is not AICPA's wording. The exact criteria are in the AICPA document.
| Category | In plain words |
|---|---|
| Security | The system is protected against unauthorised access and damage. |
| Availability | The system is up and usable when customers need it. |
| Processing integrity | The system does what it should, completely and correctly. |
| Confidentiality | Information meant to be restricted stays restricted. |
| Privacy | Personal information is handled as the company says it will be. |
AICPA's public pages do not say which categories a report must include. Companies and their customers usually agree the scope with the CPA firm. Do not assume a report covers all five.
4. Type 1 and Type 2
AICPA's public pages use both names (its sample report is titled a "SOC 2 Type 2 report", and another page mentions "SOC 2 type 1"). They describe the two only in part:
| Type 1 | Type 2 | |
|---|---|---|
| What the auditor looks at | Controls "as of a specific date" (a panel of CPAs quoted by AICPA). | Controls, with "tests of controls and results thereof" (AICPA's sample Type 2 report). |
| Plain question | Were the controls in place on that day? | Did the auditor test the controls, and what did the tests show? |
How long the testing period is for a Type 2 report is not set out on the public AICPA pages read for this guide. Ask the CPA firm.
5. A report, not a certification
AICPA's own wording is "assurance reports" and "attestation services". The work is done by CPAs, and the guide for CPAs calls a SOC 2 engagement an examination, with a SOC 2 report as the result. There is no certificate and no certification body in that description. So "SOC 2 certified" is not AICPA's term. Read it as "has a SOC 2 report". This is the main difference from ISO 27001, where an outside certification body issues a certificate.
That makes the CPA firm important. AICPA says "SOC services should be thoroughly evaluated by service organizations and CPA firms". It has also said it is looking into anonymous allegations about a compliance vendor that offers SOC services, and that it will act if auditors are unlicensed or not enrolled in peer review. Before you buy a SOC 2 engagement, check that the firm is a licensed CPA firm.
As the buyer of a report: read the report, not only the cover letter. Check the date or period, the categories covered, the system described, and any exceptions the auditor listed.
6. Who asks for it
AICPA's guide says why: customers and business partners "usually need information about the design, operation, and effectiveness of controls within the service organization's system", and "customers and business partners often request a SOC 2 report from the service organization".
- Customers and business partners who outsource a function to you and want proof of how you handle their data.
- Procurement and security questionnaires that ask "do you have a SOC 2 report?". Some customers may accept an ISO 27001 certificate or your answers to their own questionnaire instead. Ask each one.
If the question comes from a NIS2-covered customer in the EU, see NIS2 requirements for suppliers. It explains what that customer must do about its suppliers.
7. SOC 2 vs ISO 27001
The two are often compared, but they are different things.
| SOC 2 | ISO 27001 | |
|---|---|---|
| What it is | An attestation report written by a CPA firm. | A standard with requirements. Organisations can be certified against it. |
| Rules used | The AICPA Trust Services Criteria, five categories. | ISO/IEC 27001:2022, requirements for an information security management system, plus the 93 controls of Annex A. |
| Who sets the rules | AICPA, a US accounting body. | ISO and IEC, international standards bodies. |
| Who checks | A licensed CPA firm. | An external certification body. |
| What you get | A report with the auditor's findings, which you can share with customers. | A certificate for the scope you defined. |
| Named in EU rules | No. | Named as an example standard. See section 8. |
The two overlap in subject but not in form, and one does not replace the other automatically. For ISO 27001 itself see ISO 27001 certification. Its management system, the thing the standard asks you to run, is explained in What is an ISMS?
8. If you are in Sweden or the EU
SOC 2 is not required by EU or Swedish law. The words "SOC 2" do not appear in NIS2 (Directive (EU) 2022/2555), in the GDPR (Regulation (EU) 2016/679), in Implementing Regulation (EU) 2024/2690, in Cybersäkerhetslagen (2025:1506), in the ordinance (2025:1507) or in the rule books MCFFS 2026:1, 8, 11 and 12 (issued by MCF, applied unchanged by FRA since 1 July 2026). Those are the texts this guide searched.
What those texts do say about standards:
- Sweden's binding rule: an operator covered by the security rules must "identify and handle the need to use relevant standards" in its cybersecurity work (MCFFS 2026:11, 3 kap. 2 §). That is a duty to assess the need, not a duty to adopt a named standard.
- Sweden's advice, not binding: as support, the standards SS-ISO/IEC 27001:2022 and SS-EN ISO/IEC 27002:2022 "or equivalent" should be used (3 kap. 2 §, general advice). SOC 2 is not named. The rule book has been in force since 1 October 2026.
- Digital providers: the Commission's rules for DNS, cloud, data centre and similar providers say their requirements are based on standards "such as ISO/IEC 27001, ISO/IEC 27002 and ETSI EN 319401" (Regulation 2024/2690, recital 3).
- GDPR: a controller must use appropriate technical and organisational measures (Article 24(1)). Article 24(3) names approved codes of conduct and approved certification mechanisms as ways to help show compliance. SOC 2 is not named.
So an EU company asked for SOC 2 is asked as a business matter by a customer, not by the law. The law's duties are in Cybersäkerhetslagen and GDPR compliance. Whether an ISO 27001 certificate helps with NIS2 is in Is there a NIS2 certification? The short answer there: no certificate replaces the duties themselves.
Practical order for an EU company. First meet the duties that apply to you by law. Then, if a customer asks for SOC 2, ask them whether your ISO 27001 certificate, your policies or a completed questionnaire is enough. Whether a CPA-firm examination is worth doing depends on what your customers will accept.
9. How SimpleSecurity helps
SimpleSecurity is not a CPA firm and cannot issue a SOC 2 report. It does not make an organisation compliant by itself. It keeps the records and evidence that a CPA firm or a customer will ask about.
| What you need | Service |
|---|---|
| Map your controls to SOC 2 and 21 other frameworks | Compliance, with an auditor-ready export pack |
| Show who trained and who read each policy | People & Awareness: timestamped per person, exports as CSV |
| Keep policies with a lifecycle and review SLAs | Policy Register |
| Track risks and who owns them | Risk Register |
| Show how you handle vendors | Vendor Risk |
| Log changes with an approval step | Change Register |
| Log incidents and show backup checks | Incident Register, Backups with restore-test log |
| Find known vulnerabilities | Vulnerability Scanner |
See every service or see the plans.
Related guides
10. Sources
- AICPA & CIMA, System and Organization Controls: SOC Suite of Services, including the notice on SOC providers and the 16 November 2026 exposure drafts
- AICPA & CIMA, SOC 2 Reporting on an Examination of Controls at a Service Organization (guide, 2022 update)
- AICPA & CIMA, 2017 Trust Services Criteria (with revised points of focus, 2022)
- AICPA & CIMA, Introduction to SOC for Service Organizations Reporting
- AICPA & CIMA, Illustrative SOC 2 Report with Illustrative System Description
- AICPA & CIMA, SOC 3: Trust Services Criteria for General Use Report
- AICPA & CIMA, Maintaining high standards for SOC engagements (the Type 1 "as of a specific date" remark)
- ISO/IEC 27001
- Directive (EU) 2022/2555 (NIS2)
- Regulation (EU) 2016/679 (GDPR), Article 24
- Implementing Regulation (EU) 2024/2690, recital 3
- MCFFS 2026:11, 3 kap. 2 §, in force 1 October 2026