Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are ISAE 3402 and SOC 1?

ISAE 3402 and SOC 1 are assurance reports on a service organisation’s controls over client financial reporting, issued under international and American standards respectively.

Illustration for the cybersecurity term ISAE 3402 and SOC 1
Home / Blog / Cybersecurity Terms / What Are ISAE 3402 and SOC 1?
17 November 2026

What Are ISAE 3402 and SOC 1?

What Are ISAE 3402 and SOC 1?

When a company outsources payroll, custody, fund administration, or transaction processing, its own auditors face an awkward gap: part of the control environment behind the financial statements now sits in someone else’s building. ISAE 3402 and SOC 1 exist to close that gap. They are reports in which an independent auditor describes a service organisation’s controls and gives an opinion on them, so that the client’s auditor can rely on the work instead of visiting the supplier.

The two are close siblings. ISAE 3402 is the international standard, issued by the International Auditing and Assurance Standards Board in 2009. SOC 1 is the American framework, performed under SSAE 18 attestation standard AT-C 320. The subject matter is the same, and large providers often publish both.

What They Actually Cover

Only controls relevant to the user entity’s internal control over financial reporting. That boundary is the single most misunderstood point in supplier due diligence.

A payroll bureau’s controls over calculating and paying salaries correctly are in scope. The same bureau’s controls over whether employee personal data is encrypted are not, unless they bear on financial reporting. Security, availability, and privacy belong in SOC 2, which exists precisely because SOC 1 was being misused as a security report.

Typical in-scope controls include transaction processing accuracy and completeness, authorisation of inputs, reconciliation, change management for financial systems, logical access to those systems, and data transmission integrity.

Type 1 and Type 2

Client auditors almost always need a Type 2, because audit reliance depends on evidence that controls operated throughout the period under audit. A Type 1 is usually a first-year report or a stopgap during a service launch.

Reading One Properly

The structure follows a predictable pattern: the independent auditor’s report containing the opinion, management’s assertion, management’s description of the system, and then the control objectives with the auditor’s tests and results. The last section is where the information is.

Four things to check.

  1. Period and gap. Does the period cover your financial year, and how long ago did it end? A bridge letter covers a short gap but is unaudited.
  2. Scope. Which services, which systems, which locations. A report covering the supplier’s core platform may exclude the module you use.
  3. Exceptions. Deviations noted against any control objective, and whether management’s response addresses a root cause.
  4. Subservice organisations. Under the carve-out method those providers are excluded and you need separate assurance; under the inclusive method they are tested as part of the engagement.

Then extract the complementary user entity controls. These are the things the auditor assumed you do at your end, such as reviewing output reports, authorising users, and reconciling balances. Until each one has an owner in your organisation, the supplier’s clean opinion does not transfer any comfort to you.

Which One Should a UK Provider Obtain?

ISAE 3402 is the natural choice for a UK service organisation whose clients and their auditors are UK or European. SOC 1 suits providers with a substantial American client base, since US auditors are familiar with its presentation. The ICAEW publishes guidance for UK practitioners performing these engagements, and a UK variant, ISAE 3402 reported under the standard adopted by the Financial Reporting Council, is common in practice.

Providers with international client bases sometimes obtain both, or a single report prepared to satisfy both frameworks, which auditors generally accept where the standards are cited explicitly.

Where It Fits Alongside Other Reports

For a security team the practical hierarchy is simple. SOC 1 or ISAE 3402 answers your finance function’s question. SOC 2 or ISAE 3000 answers yours. ISO 27001 certification answers whether a management system exists and was independently certified. PCI DSS answers cardholder data questions specifically.

Asking a supplier for a SOC 1 when what you want is security assurance wastes everyone’s time, and accepting one as evidence of security is a common and avoidable error in third-party risk assessment. Our regulation and compliance services help organisations work out which assurance they actually need from a supplier, and what the report they received does and does not cover.

FAQ – Frequently Asked Questions

What Is the Difference Between SOC 1 and SOC 2?

SOC 1 covers controls relevant to the client’s internal control over financial reporting and is used by financial auditors. SOC 2 covers the Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy, and is used by security and procurement teams. They are not interchangeable, and a SOC 1 is not evidence of security controls.

Is ISAE 3402 the Same as SOC 1?

They are equivalent in subject matter and structure, but issued under different standards. ISAE 3402 is the international standard from the International Auditing and Assurance Standards Board; SOC 1 is the American framework performed under SSAE 18. Large providers often publish both. UK and European client auditors generally expect ISAE 3402.

Do We Need a Type 1 or a Type 2 Report?

A Type 2 in almost all cases. Type 1 only confirms that controls were suitably designed at a point in time, while Type 2 tests whether they operated effectively over a period and reports the results. Your client’s auditors need operating evidence covering the financial year, so a Type 1 rarely supports audit reliance.

What Are Complementary User Entity Controls?

Controls the service auditor assumed the client performs, without which the supplier’s control objectives are not achieved. Typical examples include authorising and reviewing user access, checking output reports, and reconciling balances. They are listed in the report and should be assigned owners in your organisation, because the supplier’s opinion does not cover them.

Related Terms

You May Be Interested In These

What Is Master File Table Analysis?

Cybersecurity Terms

17 November 2026

What Is Master File Table Analysis?

Read More
What Is a BDDK Information Systems Audit?

Cybersecurity Terms

17 November 2026

What Is a BDDK Information Systems Audit?

Read More