Home  /  Insights  /  ISO 27001 vs SOC 2: which does your business need?
Insights

ISO 27001 vs SOC 2: which does your business need?

Both prove your security to customers, but they come from different places and suit different buyers. Here's how they differ, where they overlap, which one to do first and how to add the other without starting again.

Cyber Veda

Quick answer: ISO 27001 is an international standard that ends in a certificate from an accredited certification body. SOC 2 is an American attestation that ends in a report from a CPA firm. Choose ISO 27001 if you sell to Australian, Asian, European or government buyers, and SOC 2 if your customers are mainly in the US. The controls overlap heavily, so you can do one first and add the other with far less effort.

The short version

ISO 27001SOC 2
What it isInternational standard for an information security management system (ISMS)AICPA attestation against the Trust Services Criteria
Current versionISO/IEC 27001:2022 (with Amendment 1:2024)2017 Trust Services Criteria, with revised points of focus (2022)
Who auditsAn accredited certification body (JAS-ANZ accredited in Australia)A licensed CPA firm
What you getA certificate, valid three years with annual surveillance auditsA report, usually renewed every year
OutcomeCertified or not, based on conformity with the standardThe auditor’s opinion, plus (for Type 2) the tests performed and any exceptions
Who asks for itAustralian government and enterprise, Asia-Pacific, UK and EuropeUS customers and US-headquartered enterprises
ScopeThe ISMS: risk management plus the Annex A controls you selectYour system, against Security plus any of Availability, Confidentiality, Processing Integrity and Privacy
Can you share it?Yes, the certificate can be shown to anyone and verified with the certification bodyThe report is shared under NDA; a SOC 3 is a separate general-use report you can publish

What each one actually is

ISO 27001

ISO/IEC 27001 is a management system standard. Clauses 4 to 10 set out how you run information security as a business process: define the scope, understand your context and interested parties, assess and treat risk, set objectives, run an internal audit and a management review, and fix what goes wrong. Annex A lists 93 controls in four themes, and you decide which apply in your Statement of Applicability. An accredited certification body audits you in two stages, issues a certificate and then returns every year. See the ISO 27001 audit cycle for how the three years run.

SOC 2

SOC 2 is a reporting framework from the American Institute of CPAs (AICPA). A CPA firm examines a defined system, such as your SaaS platform and the people, processes and infrastructure behind it, against the Trust Services Criteria. Security (the common criteria, CC1 to CC9) is always in scope; Availability, Confidentiality, Processing Integrity and Privacy are optional. The result is a report containing your management’s assertion, a description of your system and the auditor’s opinion. A Type 1 report looks at control design on one date; a Type 2 also tests whether controls operated across a period. Our SOC 2 Type 1 vs Type 2 guide covers the difference in full.

The AICPA released an exposure draft of revised Trust Services Criteria in October 2026. Until it is finalised and takes effect, examinations use the 2017 criteria; SOC 2 in Australia explains what the proposal means for timing.

Certificate vs report: what your customer actually receives

This is the difference buyers feel most. With ISO 27001, your customer gets a certificate showing your scope, the standard and the certification body, which they can verify on the body’s register. If they want more, you can share your Statement of Applicability or a summary of your risk approach under NDA. The certificate says you passed; it doesn’t list what the auditor tested.

With SOC 2, your customer gets a detailed report, shared under NDA. A Type 2 report lists each control, how the auditor tested it and whether any exceptions were found. That detail is why many US enterprise security teams and internal auditors prefer it: they can read exactly how access reviews, change approvals and backups performed. It is also why SOC 2 exceptions matter. A few minor ones are read in context, but they are visible to every customer who reads the report.

The report also tells customers what they are responsible for (complementary user entity controls) and which cloud providers and other subservice organisations your system relies on. ISO 27001 handles the same ideas through scope, supplier controls and risk treatment, but doesn’t publish them in the same way.

Who asks for which

BuyerWhat they usually ask forNotes
Australian federal and state governmentISO 27001Often alongside the Essential Eight; see ISO 27001 for government tenders
Australian enterpriseISO 27001, sometimes eitherQuestionnaires frequently name ISO 27001 first
Banks, insurers and super funds (APRA-regulated)EitherCPS 234 drives the supplier assessment; some US-owned institutions prefer SOC 2 Type 2. See ISO 27001 for fintechs
US customers and US-headquartered enterprisesSOC 2, usually Type 2A certificate alone often doesn’t satisfy procurement
Asia-Pacific, UK and EuropeISO 27001The internationally recognised certificate
Investors and acquirersEitherMainly checking that a working program exists

How to choose

Start with the question your customers are asking. If tenders, procurement teams or security questionnaires name ISO 27001, do ISO 27001. If a US prospect asks for “your SOC 2 report”, a certificate usually won't satisfy them. When both come up, start with the one tied to your biggest near-term deal. SaaS vendors should also read ISO 27001 for SaaS companies.

If this describes youStart with
Selling mainly in Australia, NZ or Asia, including governmentISO 27001
A named US deal is waiting on a SOC 2 report this quarterSOC 2 Type 1, then Type 2
Mostly US customers, no urgent dealSOC 2 Type 2
A mix of Australian and US enterprise customersISO 27001, with SOC 2 mapped from the same controls
You want a certificate you can publish on your websiteISO 27001

For Australian businesses, ISO 27001 is usually the better first step. It's recognised across government and enterprise, the certificate can be shown to anyone, and it gives you the management system the SOC 2 controls sit inside.

Where they overlap

Most of the work is shared: risk assessment, access control, change management, supplier management, incident response, logging, backups and security awareness. If you build those properly once, you can map them to both frameworks. Compliance platforms like Vanta show the overlap control by control.

Where ISO 27001 and SOC 2 overlapBuild the shared controls once and map them to both

ISO 27001 only

  • Context and scope (clause 4)
  • Leadership and ISMS policy
  • Statement of Applicability
  • Internal audit programme
  • Management review
  • Continual improvement

Shared

  • Risk assessment
  • Access control and MFA
  • Change management
  • Supplier management
  • Incident response
  • Logging and monitoring
  • Backups and recovery
  • Security awareness training

SOC 2 only

  • System description
  • Trust Services Criteria mapping
  • Management assertion
  • Observation period (Type 2)
  • CPA firm report

Illustrative, not exhaustive. Most of the work sits in the middle column.

The differences are in the wrapper. ISO 27001 needs the management system clauses (context, leadership, internal audit, management review and continual improvement) and a Statement of Applicability. SOC 2 needs a system description and, for a Type 2 report, evidence that controls worked across an observation period.

How the work differs in practice

ISO 27001SOC 2
Starting pointScope and a documented risk assessment that drives control selectionChoice of system, criteria and report type
Main documentsISMS scope, policies, risk assessment and treatment plan, Statement of ApplicabilityPolicies, system description, management assertion
Before the external auditAn internal audit and a management review are requiredNo internal audit required; a readiness assessment is common practice
What the auditor checksThat the ISMS conforms to clauses 4 to 10 and the selected controls are implementedThat controls meet the criteria, as designed (Type 1) or operating over time (Type 2)
FindingsMajor and minor nonconformities, closed with corrective actionExceptions in the report, with management’s response
Ongoing rhythmSurveillance audits in years two and three, recertification in year threeA new report each year, ideally with back-to-back periods

Effort for either depends far more on your starting point and scope than on the framework. Our ISO 27001 timeline and ISO 27001 cost guide explain what drives it; the same drivers (systems in scope, people, existing controls, deadline) apply to SOC 2.

Doing both without doing it twice

  • Design controls once. Write each control so it satisfies the stricter of the two requirements. A quarterly access review with recorded sign-off, for example, satisfies both.
  • Keep one control set. Maintain a single list of controls mapped to Annex A and to the Trust Services Criteria, rather than two programs owned by different people.
  • Collect evidence once. The same access review, backup test or onboarding record serves both audits.
  • Line up the audits. Time your SOC 2 observation period to overlap your ISO 27001 surveillance year, so one evidence cycle feeds both auditors.
  • Reuse the risk assessment. SOC 2 also requires risk assessment (CC3); your ISO 27001 risk process covers it if the SOC 2 system sits inside your ISMS scope.

If you hold ISO 27001 first, adding SOC 2 is mostly a mapping exercise, a system description and closing a handful of gaps. If you have SOC 2 first, adding ISO 27001 means building the management system around controls you already run: scope, risk treatment, Statement of Applicability, internal audit and management review.

Common mistakes

  • Choosing by reputation instead of by customer. The right framework is the one in your contracts and questionnaires.
  • Mismatched scopes. An ISO 27001 scope that excludes the product your SOC 2 covers means two sets of evidence.
  • Treating SOC 2 as a checklist. Type 2 tests whether controls ran every time, not whether a policy exists.
  • Calling SOC 2 a certification in sales material. Buyers who know the difference notice.

Not sure which you need?

Tell us who you sell to and what they're asking for, and we'll tell you straight. One certified security expert runs the work from first call to report or certificate, and builds one control set for both if you need it. See our ISO 27001 and SOC 2 pages, or book a free 30-minute consultation.

FAQ

Common questions

Is ISO 27001 or SOC 2 better?

Neither is better. They answer the same question (can we trust your security?) for different audiences. ISO 27001 is the global default and the usual ask in Australian government and enterprise tenders. SOC 2 is what most US customers expect. Pick the one your customers ask for, and plan to reuse the work if you need the other later.

Can we get SOC 2 if we already have ISO 27001?

Yes, and it’s much faster the second time. Most of the policies, risk management and controls carry over. The extra work is mapping to the Trust Services Criteria, filling a few gaps, writing the system description and, for Type 2, running the controls through an observation period.

Will a US customer accept ISO 27001 instead of SOC 2?

Sometimes. Some US buyers accept an ISO 27001 certificate plus their own questionnaire, especially for smaller contracts. Many enterprise procurement and internal audit teams insist on a SOC 2 Type 2 report because it shows the auditor’s test results. Ask before you assume either way.

Does SOC 2 apply to Australian companies?

SOC 2 is an American (AICPA) framework, but any company can get a SOC 2 report from a licensed CPA firm. Australian companies usually pursue it because they sell to US customers or US-headquartered enterprises.

Is SOC 2 a certification?

Strictly, no. SOC 2 is an attestation: a CPA firm issues a report giving its opinion on your controls. ISO 27001 is a certification: an accredited certification body issues a certificate. In conversation people often call both “certification”.

Which is quicker to get, ISO 27001 or SOC 2?

A SOC 2 Type 1 can be the quickest independent report, because it looks at a single date. ISO 27001 takes longer to reach a certificate because it needs a working management system, an internal audit and a two-stage external audit. A SOC 2 Type 2 is usually the slowest first time, because the observation period has to run before the report can be issued.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.