Skip to main content
Guide · Updated

SOC 2 vs ISO 27001: the honest comparison for Australian companies

ISO 27001 and SOC 2 answer the same question — can we trust you with our data? — for two different audiences, in two different formats. One is a certification, the other an attestation. This guide sets out what actually separates them, how much genuinely overlaps, which one your buyer is asking for, and the order to do them in if you need both.
By Harry Sidhu — ISO 27001 Lead Implementer · Director and Principal Consultant, Aegentra12 min readLast reviewed

The short answer

ISO 27001 is a certification; SOC 2 is an attestation report. Ask your buyer which one they want before you spend a dollar on either. The actual contract, tender or security questionnaire determines the requirement. Confirm uncertain acceptance conditions in writing; location alone does not decide.

The two can share controls and evidence, but the degree of reuse depends on the agreed boundaries and criteria. Their assurance structures remain distinct. ISO 27001 requires a documented ISMS with a risk assessment, a Statement of Applicability, an internal audit and a management review. SOC 2 uses its own description criteria and Trust Services Criteria; Type I and Type II address different evidence periods.

If you need both, choose the sequence from the buyer deadline, current controls, available evidence and independent assessors’ requirements. Shared work can reduce duplication; confirm the actual effort before pricing it.

Certification vs attestation — the difference that matters

This is the distinction most comparisons skip, and it changes what you can actually hand a customer.

ISO 27001 is certified. An accredited certification body with an accredited scope accepted by the buyer — for example through JASANZ or another relevant accreditor such as ANAB or IAS — audits your ISMS in two stages and issues a certificate valid for three years, with surveillance audits in years one and two. The certificate is a short, public document. Buyers can verify it on the certification body’s register.

SOC 2 is attested. A licensed CPA firm examines your controls against the AICPA Trust Services Criteria and issues a report — often 40 to 100 pages, containing the auditor’s opinion, your system description, every control tested, and any exceptions found. There is no certificate and no public register. The report is normally shared under NDA.

Practically: ISO 27001 gives you something short you can publish; SOC 2 gives you something long you send to a buyer’s security team. Neither is stronger — they are different instruments.

One produces a certificate you can publish. The other produces a report you send under NDA.

Side by side

 ISO/IEC 27001:2022SOC 2
What it isCertifiable international standardAICPA attestation engagement
What you getA certificate, valid 3 yearsA report covering a stated period
Who issues itCertification body with relevant, buyer-accepted accreditationLicensed CPA firm
Publicly verifiableYes — on the certification body registerNo — shared under NDA
Control set93 Annex A controls, 4 themes5 Trust Services Criteria; Security mandatory
Management system requiredYes — ISMS, risk assessment, SoA, internal audit, management reviewNo
CycleStage 1 + 2, then surveillance yrs 1–2, re-cert yr 3Annual, to keep the report current
Point-in-time vs periodOngoing certificationType I = point in time · Type II = period
Buyer requirementConfirm certificate scope and accreditationConfirm report type, criteria, system and period

How much overlap is there really?

Map the requirements to the same underlying controls where appropriate, and test whether existing evidence meets both scopes. Reuse does not guarantee a fixed saving.

What genuinely carries across:

  • Access control, joiner-mover-leaver, and privileged access
  • Change management and secure development
  • Logging, monitoring and incident response
  • Vendor and third-party risk management
  • Backup, recovery and business continuity
  • Physical and environmental controls
  • Security awareness training and screening

What does not carry across, and catches people out:

  • —The ISMS itself — scope, risk assessment method, Statement of Applicability, risk treatment plan
  • —Clause 9 obligations — internal audit programme and management review, both mandatory for ISO 27001 and absent from SOC 2
  • —The SOC 2 system description — a detailed narrative of your service that ISO 27001 never asks for
  • —Trust Services Criteria beyond Security, which you select based on what you promise customers

Which one does your buyer want?

Do not guess this. Read the security questionnaire or the tender schedule. If the required assurance or accepted alternatives are unclear, obtain written buyer clarification.

Requirement to clarifyEvidence to requestWhy
Named assurance formatCertificate or SOC 2 reportDo not infer it from country or industry
Entity and serviceExact scope and system descriptionCheck the service being purchased is covered
SOC 2 period and criteriaRequired type, criteria and periodA Type I report may not answer a Type II requirement
ISO accreditationAccepted accreditor and current scopeConfirm any equivalence provision with the buyer
Other obligationsApplicable contract and regulatory termsNeither assurance instrument establishes all legal compliance
Deadline and gapsDue date, owner and buyer confirmationAgree which evidence can be supplied and when

What each one costs in Australia

Build a scope-specific budget. Readiness is what you pay a consultancy; the audit or examination fee is paid separately to the certification body or CPA firm.

CostISO 27001SOC 2
Readiness / implementationCurrent scoped ISO 27001 service offerCurrent scoped SOC 2 readiness offer
Audit or examinationSeparate certification-body quoteSeparate CPA-firm quote
OngoingMaintenance and surveillance quoted separatelyControl operation and agreed report period
RenewalRecertification under the agreed programmeNext examination to meet buyer requirements

Compare the complete programme, including internal effort, tools and external fees. The scope-based budgeting approach is explained in the ISO 27001 certification guide for Australia.

Doing both, in the right order

The following is one possible sequence for an organisation that needs both. A buyer deadline or an existing control environment may justify a different order.

  1. Build the ISMS. Scope, risk assessment, Statement of Applicability, controls, internal audit, management review. Map governance work to the separate SOC 2 criteria where relevant.
  2. Certify to ISO 27001. Stage 1 and Stage 2 with an accredited body. You now have a publishable certificate.
  3. Map across to the Trust Services Criteria. Select which criteria beyond Security you commit to, and write the system description.
  4. Run the SOC 2 observation window and examination. Type II over three to twelve months, performed by a licensed CPA firm.

Confirm the proposed sequence with the buyer and independent assessor. A Type I report should only be treated as an interim step if the buyer accepts it.

The credentials behind each

Frameworks are certified at the organisation level; people are certified separately. If you are the person who will own this work, these are the individual pathways.

Check each course page for the selected format, exam inclusion, retake conditions and credential requirements. An exam pass is separate from an individual credential award. For the organisation-level work, see ISO 27001 readiness and SOC 2 readiness. Aegentra does not issue SOC 2 reports or ISO 27001 certificates — those come from a licensed CPA firm and an accredited certification body respectively.

FAQs

Is SOC 2 the same as ISO 27001?

No. ISO/IEC 27001 is a certifiable international standard — an accredited certification body audits your Information Security Management System and issues a certificate valid for three years. SOC 2 is an attestation: a licensed CPA firm examines your controls against the AICPA Trust Services Criteria and issues a report, not a certificate. ISO 27001 tells a buyer you run a governed security programme; SOC 2 gives them an auditor’s opinion with the detailed evidence attached.

Which is better for an Australian company, SOC 2 or ISO 27001?

Read the actual customer contract, tender or questionnaire. Confirm the required assurance format, scope, reporting period, accreditation and acceptance criteria. Geography can prompt questions but does not establish the requirement, and selling across regions does not automatically mean you need both.

How much do ISO 27001 and SOC 2 overlap?

Some controls and evidence can be reused, including access, change management, incident response and supplier oversight. The amount depends on the ISMS scope, SOC 2 system boundary, selected criteria and evidence periods. Map each requirement and gap explicitly; no universal percentage or saving is established.

What is the difference between SOC 2 Type I and Type II?

Type I addresses design at a specified date; Type II also addresses operating effectiveness over a specified period. Confirm the required type and period with the buyer and CPA firm. A Type I report should not be assumed to satisfy a Type II requirement.

Can Aegentra issue a SOC 2 report?

No, and neither can any consultancy. Only a licensed CPA firm can perform a SOC 2 examination and issue the report. Aegentra does SOC 2 readiness — scoping the Trust Services Criteria, building and evidencing the controls inside your Microsoft 365 tenant, and preparing you for the examination — then works alongside the CPA firm that performs it. The same separation applies to ISO 27001: certification audits are performed by accredited certification bodies, not by Aegentra.

Does SOC 2 expire?

A SOC 2 report covers a specified date or period. Its acceptance and freshness depend on the buyer’s requirements. Confirm the next reporting period and any bridging information with the CPA firm. ISO certification follows its own surveillance and recertification programme; compare the full ongoing obligations.

Which is cheaper?

Compare written quotes for the same scope, evidence period and responsibilities. Separate readiness consulting, internal effort, remediation, tools and the independent certification or examination fee. Aegentra’s current service pages state its scoped offers; external providers quote their own work. Neither framework is universally cheaper.

Readiness for either, or both

Get audit-ready without guessing which framework you need

Aegentra builds and evidences the controls inside your Microsoft 365 tenant. Certification is handed to an accredited body; SOC 2 examinations to a licensed CPA firm.