By organization
Small businessesSecurity done right, your days kept for the business.
Mid-marketA program run every week, across sites and teams.
Enterprise & security teamsQoBot takes the routine, your team does strategy.
Public sectorSteer your cybersecurity, keep agents on their mission.
IT service providers & MSPsYour vCISO service, for every client.
Developers & agentsGive your agents a CISO, through API and MCP.
By need
Security questionnairesAnswered from your evidence, sources cited.
Cyber insuranceRenewal forms drafted, requirements in place.
NIS2, ISO 27001 & other obligationsSOC 2, TISAX, Cyber Essentials too: know what applies, get ready for the auditor.
IncidentsCalm, step-by-step response when something happens.
A security program from scratchA prioritized plan in plain words, then the follow-up.
Support for your CISOBacklog, drafts, evidence and reporting prep.
Somewhere in between? QoBot asks a few quick questions when you join.Join the waitlist

SOC 2 in plain words: for European and UK companies selling to the US

US customers often ask for a SOC 2 report before they sign. Here's what it is, the difference between Type 1 and Type 2, who can issue it, and what you need in place, whether you're in Lyon, Munich or Leeds.

Last updated 4 min readAICPA 2017 Trust Services Criteria (revised points of focus, 2022)ENFR

In 30 seconds

What
An examination of the controls of a service organisation, relevant to security, availability, processing integrity, confidentiality or privacy. The result is a report with the auditor's opinion.
Criteria
The AICPA's 2017 Trust Services Criteria, with points of focus revised in 2022. You and your auditor agree which categories the report covers.
Two types
Type 1: your system description and the design of your controls, at one date. Type 2: the same, plus whether the controls worked throughout a period.
Who issues it
A licensed CPA firm, under the AICPA's attestation standards. You receive an attestation report with the firm's opinion.
Who sees it
Restricted use: customers and others who understand your system, usually under NDA. SOC 3 is the short public version.
Your part
Management describes the system and asserts that it's accurate. Your team runs the controls and keeps the evidence for the whole period.

What SOC 2 is

SOC 2 is a US attestation report. A CPA firm examines how a service organisation protects the systems it uses to serve its customers, against the Trust Services Criteria set by the AICPA, the US accounting profession’s body. The result is a report: a description of your system, your controls, the auditor’s opinion and, for Type 2, the tests the auditor ran.

US companies use it to check their suppliers. If you host data, run a platform or provide IT services to US customers, expect it in their vendor review, next to their security questionnaire.

The Trust Services Criteria

The criteria are grouped in five categories. You and your auditor agree which ones the report covers, based on your service and what your customers need.

  • Security
  • Availability
  • Processing integrity
  • Confidentiality
  • Privacy

Privacy in SOC 2 is a separate topic from GDPR. A SOC 2 report with the Privacy category doesn’t show GDPR compliance, and GDPR doesn’t ask for SOC 2. If you sell to US customers from Europe, you’ll often have both to handle.

Type 1 or Type 2

Type 1

Your system description and the design of your controls, as of a specified date.

Question answered
Are the right controls in place?
Evidence
At one date

Type 2

The same opinions, plus one on whether the controls operated effectively throughout a specified period.

Question answered
Did they work, month after month?
Evidence
For the whole period

Who issues the report

Only a CPA firm can perform a SOC 2 examination and issue the report, under the AICPA’s attestation standards (SSAE 21 applies to reports dated from 15 June 2022). A software tool can’t. When you pick a firm based outside the US, ask how it’s licensed to issue SOC 2 reports.

The report goes to specified parties who understand your system: your customers, their auditors, sometimes prospects under NDA. For a short version you can publish, the auditor issues a SOC 3 report.

What you need in place

  1. A defined scopeThe service, the systems behind it, the criteria covered.
  2. A system descriptionWhat the service does, and the systems, people and procedures behind it, written by management.
  3. Risk assessmentYour risks for that service, and how controls answer them.
  4. Policies people followSecurity, access, change management, incident response, suppliers.
  5. Access controlOnboarding, offboarding, MFA, periodic access reviews.
  6. Change managementChanges requested, reviewed, approved and traced.
  7. Monitoring and incidentsLogs reviewed, incidents recorded and handled.
  8. Evidence over timeFor Type 2: records for every month of the period.
A typical path
  1. FirstReadinessScope, gap analysis, missing controls and policies.
  2. DateType 1The auditor checks the design at one date.
  3. PeriodType 2Controls run and evidence builds up over the agreed period.
  4. ThenRenewalCustomers ask for a recent report, so the cycle repeats.

SOC 2 and ISO 27001

They cover much of the same ground: risk assessment, access control, change management, incidents, suppliers, monitoring. The AICPA has published a mapping between the Trust Services Criteria and ISO 27001 (published in 2018, before the 2022 edition of ISO 27001), so one set of controls can serve both.

The deliverables differ. ISO 27001 gives you a certificate from an accredited certification body, on a management system, valid three years with surveillance audits. SOC 2 gives you an attestation report from a CPA firm, describing your system and, for Type 2, the controls’ results over a period. Ask each customer which one they accept before you start the second.

With QoBot

Getting ready for SOC 2: who does what

What QoBot does

  • Helps you set the scope: which service, which systems, which criteria the customer needs.
  • Drafts the system description from what's true in your company today.
  • Maps your existing controls, including ISO 27001 ones, to the Trust Services Criteria and lists the gaps.
  • Writes the missing policies and procedures, and the evidence list for each control.
  • Follows the evidence through the Type 2 period and tells you what's missing before the auditor does.

What your team does

  • Management approves the scope, the system description and the assertion.
  • Your team runs the controls and keeps the records, every month of the period.
  • You choose the CPA firm and agree the period with it.
  • You answer the auditor's requests and sample tests.
Example, with a fictional company

Proposed scope for Northwind Logistics: the shipment-tracking platform, Security and Availability criteria, a Type 1 first. 31 controls mapped from your ISO 27001 system, 6 gaps. This week:

  • Claire (COO): approve the scope and the system description outline · ~20 minNeeds you
  • Tom (IT): export last quarter's access reviews and change tickets · guide ready · ~30 minYour turn

FAQ

Can a European or UK company get a SOC 2 report?

Yes. SOC 2 is about your service and your controls, wherever you're based. The report is issued by a CPA firm; ask the firm how it's licensed to issue SOC 2 reports, as the AICPA refers unlicensed firms to state boards of accountancy.

Type 1 or Type 2 first?

A Type 1 shows the design of your controls at a date, so it can come sooner. A Type 2 also shows they worked through a period, which is what many customers want. Ask your customer which one they accept, and whether a Type 1 now with a Type 2 planned is enough for the contract.

How long does it take?

It depends on your scope and on what's already in place. For a Type 2, your controls must run through the whole period before the report can cover them, and the period is agreed with your auditor. Plan in months.

We have ISO 27001. Do we still need SOC 2?

If a customer asks for it, usually yes: they're different deliverables. Much of the work overlaps, and the AICPA has published a mapping between the Trust Services Criteria and ISO 27001, so your ISO controls give you a strong start. See ISO 27001 in plain words.

Can we share our SOC 2 report publicly?

No. A SOC 2 report is for specified parties who understand your system, so it's usually shared under NDA. For a public version, auditors issue a SOC 3 report.

Can QoBot issue or sign our SOC 2 report?

No. Only a CPA firm can perform the examination and issue the report. QoBot gets you ready: scope, system description draft, controls mapped to the criteria, evidence list and follow-up.

Sources

Written from QoBot's CISO knowledge, with the sources above. · Last updated 20 October 2026
This page explains the rules in plain words. It isn't legal advice: for a borderline case, ask a lawyer. Report an error

These pages explain how, and QoBot applies it to your company.

QoBot does the routine part of the work: your policies, your questionnaires, your plan, written for your company. Your team gets short, clear next steps and keeps its days for the business.

Free desktop appYour own AImacOS, Windows, Linux