Back to Knowledge Hub

SOC 2 for EU tech companies: What US customers expect and how to get there

By Louis Sieg

Founder of ReadySecGoISO/IEC 27001 Lead Auditor and Implementer

7 min read

Key Takeaways

  1. US procurement checklists often list SOC 2 specifically, so an ISO 27001 certificate does not always satisfy them.
  2. Some US buyers want the report signed by a US-licensed CPA firm, while others accept a European auditor working under the international standard ISAE 3000.
  3. Much of your ISO 27001 work carries over, including policies, risk assessment, access reviews and supplier checks.
  4. What SOC 2 adds on top of your ISO 27001 system is a system description, controls written so an auditor can test them, and evidence kept across the whole period.
  5. Ask the buyer early whether they need a US-licensed CPA firm and which criteria they want covered, because that decides who can run your audit.

Summarize this article with AI:

Your ISO 27001 certification has covered every customer in Europe so far. Then a US prospect’s procurement team sends its vendor checklist, and one line says “SOC 2 Type II report”. You send your ISO 27001 certificate, and the procurement team still asks for the SOC 2 report. This guide explains why that happens, who can issue a SOC 2 report for a European company, and how to get one without starting from zero.

Why US customers ask for SOC 2

A SOC 2 report is an independent auditor’s opinion on how you protect customer data. The auditor measures your controls against the Trust Services Criteria of the AICPA (the American Institute of Certified Public Accountants), which cover five areas: Security, Availability, Confidentiality, Processing Integrity and Privacy. Security is always included. The other four are optional, and you add one when a customer contract calls for it, such as Availability for an uptime commitment. A Type I report looks at your controls on one date, and a Type II covers a period, usually three to twelve months. US buyers usually ask for a Type II. Our guide to SOC 2 Type I and Type II explains the two in detail.

In the US, SOC 2 is the standard proof a buyer asks a software supplier for. Their procurement policy often lists it, and their security team works through a vendor questionnaire such as the SIG (Standardized Information Gathering questionnaire) or the CAIQ (the Cloud Security Alliance’s Consensus Assessments Initiative Questionnaire). Both run to hundreds of questions. Many buyers still send the questionnaire once they have your report, but a large share of the questions can then be answered by pointing to it, which shortens the review.

Many US buyers accept ISO 27001 as well, and some ask for both. The difficulty is usually the checklist. The person on the buyer’s side who checks suppliers, the reviewer, usually sits in the security or procurement team and works from a list with a box labelled “SOC 2”. A certificate for a different standard means extra work for them, so they often keep asking for the SOC 2 report.

Who can sign the report

SOC 2 is a brand name owned by the AICPA. Behind it is a specific kind of audit: an independent auditor gives reasonable assurance, a high level of confidence comparable to a financial statement audit, that your controls meet the Trust Services Criteria. The criteria in use today date from 2017, with guidance updated in 2022. In the US, a SOC 2 audit follows AT-C 205, the part of the AICPA’s attestation standards that covers this type of examination, and only a CPA firm (Certified Public Accountants) licensed in a US state can work under it.

An auditor outside the US can run the same kind of audit against the same criteria under ISAE 3000, the international standard for assurance work. Several German audit firms (Wirtschaftsprüfungsgesellschaften) offer SOC 2 audits this way. The report can still carry the name SOC 2, and the auditor’s opinion states which standard the audit followed.

So the question to settle is which report your US buyer accepts. Some accept a SOC 2 report under ISAE 3000. Others expect one from a US-licensed CPA firm under AT-C 205. Ask before you choose an auditor.

Choosing a US firm does not mean flying people in. Most SOC 2 audits for European companies run remotely. Interviews happen over video, and evidence is uploaded to the auditor’s portal. Some international networks also have US-licensed member firms that can run the audit with a team in Europe.

How to check your auditor

The two routes differ in two places. The first is the AICPA’s SOC logo. A company whose SOC 2 report comes from a licensed CPA firm may show the AICPA’s “SOC for Service Organizations” logo on its website for twelve months after the report date. A report under ISAE 3000 does not qualify for it. The second is the AICPA peer review programme. US CPA firms that perform SOC 2 audits have to be enrolled in it, and other auditors regularly review their work. A European firm working under ISAE 3000 is checked by its own national oversight body instead.

If you pick a US firm, check its enrolment yourself in the AICPA’s public Peer Review Public File search. It takes a minute, and a firm that is missing from the list is a reason to look elsewhere. If you pick a European firm, ask which standard the report will follow and whether US customers have accepted its SOC 2 reports before.

What carries over from ISO 27001

If you hold ISO 27001, you have already done much of the work. Your information security policies, risk assessment, access management, supplier checks, incident process, awareness training and change management all have a counterpart in the Trust Services Criteria. The AICPA has published a mapping between the two, but it dates from 2018 and follows the older edition of ISO 27001. The examples below use the control numbers of the current 2022 edition.

For example, the quarterly access review you run for Annex A control 5.18 (access rights) is the same kind of control a SOC 2 auditor tests under CC6, the criteria on logical and physical access. Your risk assessment under Clause 6 covers most of CC3, the risk assessment criteria. Your incident process under Annex A 5.24 to 5.28 maps to CC7, the criteria on system operations.

The quickest way to see where you stand is to compare your ISO controls against the SOC 2 criteria line by line.

What SOC 2 adds

A system description you write yourself. In ISO 27001 your scope statement is a few lines. In SOC 2 you write a longer description of the system: the services, the infrastructure, the software, the people, the procedures and the data. Your management also signs a statement, called the management assertion. It confirms that the description is fair, that the controls are suitably designed and, for a Type II, that they worked throughout the period. US reviewers read the description closely, because it tells them whether the product they are buying is covered. A report that covers your main platform but leaves out the analytics add-on they want will raise questions.

The description also says where your responsibility ends and your cloud provider’s begins. If you run on AWS, Azure or Google Cloud, the provider secures the data centres and has its own SOC 2 report for that. Your report covers what you control, such as who on your team can access the production account. Auditors call this the carve-out method.

It also lists what the customer has to do on their side, for example deciding which of their employees get an account in your application. In the report these are called complementary user entity controls.

Controls written as testable statements. Each control in a SOC 2 report is a sentence the auditor can test, with an owner and a frequency. “Access to production systems is reviewed quarterly by the CTO, and removals are recorded in the ticket system” can be tested. “We manage access appropriately” cannot. Many ISO policies are written in the second style and need rewording.

Evidence across the whole period. An ISO 27001 auditor also looks at past records and can ask for a change from three months ago. The difference is how systematic the test is and where the result ends up. A SOC 2 Type II report covers a period with a fixed start and end date. For each control, the auditor asks for the full list of events in that period, such as all 300 production changes, picks a sample of perhaps 25 and checks every one. Any failed sample appears in the report as an exception, and your customers read it. An ISO nonconformity stays between you and your certification body. A change approved in a chat message and never recorded is a typical exception. US reviewers read every exception together with your management’s response, so each one needs a short explanation of what you fixed.

A worked example

Take a 40-person software company in Hamburg. It has held ISO 27001 for two years and sells a fleet scheduling platform to logistics firms. A US logistics group wants to buy and asks for a SOC 2 Type II report covering Security and Availability, because the contract includes an uptime commitment.

Weeks 1 to 3. The team compares its ISO controls against the Trust Services Criteria and finds four gaps. There is no system description. Access reviews happen in Slack and leave no record. Emergency fixes go to production without a recorded approval. And most controls read like policy text, with no owner or frequency.

Weeks 4 to 9. The team writes the system description, carves out AWS Frankfurt and lists the customer’s own duties. It moves access reviews into its ticket system, adds an approval step for emergency fixes and rewrites around 40 controls as testable statements. It also chooses a US-licensed CPA firm that audits remotely.

Weeks 10 to 14. The auditor runs the Type I examination, which checks the controls on one date. The Type I report arrives around week 14, so the buyer’s reviewer has a report to read while the longer audit runs.

Months 4 to 9. The six-month observation period for the Type II runs. The team keeps the evidence as it goes, so nobody has to rebuild records when the auditor asks.

Around month 11. The auditor tests the samples from the period and issues the Type II report, a little under a year after the buyer first asked.

None of the four gaps needed a new tool or a new policy. They needed the existing ISO work written down in the form a SOC 2 auditor tests, and good preparation for the auditor’s evidence requests made sure the records were complete from the first day of the period.

Where to start

Start with the buyer. Ask whether they need a US-licensed CPA firm or also accept a European auditor working under ISAE 3000, and which of the Trust Services Criteria they want covered. Their reply tells you which auditor to look for. If it is a US firm, check its peer review enrolment before you sign.

Then compare your ISO 27001 controls against the criteria and list the gaps. Write the system description early, because it forces you to decide what is in scope and what your cloud provider covers. Rewrite your controls as statements with an owner and a frequency. Once they are running and recorded, get a Type I report, then start the observation period and keep collecting evidence as part of normal work.

What's next?

Before you agree a report type and period with the buyer, read our guide to SOC 2 Type I and Type II, which explains why a Type I first usually pays off and how to choose your auditor.

A Type II also tests how you handled incidents across the whole period, so your incident process has to work in practice. Our guide to incident management shows how to set up a process your team follows when something goes wrong.

Explore our services