Cybernion
← Insights

IRAP

IRAP vs SOC 2: Which Assurance Do You Need?

3 July 2026 · Updated 3 July 2026

IRAP is an independent assessment of one system against the Australian Government Information Security Manual (ISM), written up as a report with no pass mark, so an agency can decide whether to use it. SOC 2 is a licensed CPA firm’s report on your controls against the AICPA Trust Services Criteria (TSC). IRAP is for Australian Government work; SOC 2 is asked for by customers whose own risk or procurement process expects it, in any country and any sector.

Providers selling cloud or SaaS in Australia often hold a SOC 2 for their customers, then meet a government tender asking for IRAP and wonder whether the SOC 2 covers it. It does not, because the two are different assurances for different buyers, owned by different bodies and asked for by different customers.

What is the difference between IRAP and SOC 2?

They answer to different owners and different buyers. IRAP is run by the Australian Signals Directorate (ASD). An ASD endorsed IRAP assessor examines one specific system against the Information Security Manual (ISM) and writes a report on its strengths, weaknesses and residual risks. There is no certificate and no pass mark, because the decision to accept the residual risk belongs to a government authorising officer.

SOC 2 is a United States standard maintained by the American Institute of Certified Public Accountants (AICPA) and used by customers worldwide. A licensed Certified Public Accountant (CPA) firm examines a provider’s controls against the Trust Services Criteria (TSC) and writes an opinion. It is an attestation report, not a certificate, produced under the SSAE 18 attestation standard. Security, the common criteria, is mandatory, while Availability, Processing Integrity, Confidentiality and Privacy are added where the provider makes commitments. One assurance is built for Australian Government risk decisions, the other for the buyers who ask for a trust report. The complete guide to IRAP assessment covers how the IRAP side works end to end.

Do we need IRAP or SOC 2?

The buyer and the data decide, not the brand. A provider that sells, or wants to sell, cloud or SaaS that stores, processes or transmits Australian Government information at OFFICIAL: Sensitive or above will almost certainly need an IRAP assessment, because the Protective Security Policy Framework (PSPF) requires outsourced IT and cloud services holding government data to be IRAP assessed against the ISM before an agency uses them.

Where customers ask for a SOC 2 as part of their own risk or procurement process, that is SOC 2, and the trigger is their requirement and the system in question, not the provider’s country or whether the buyer is government or private. A short test: a government agency handing over PROTECTED data points to IRAP, while a customer whose security review requires a trust report points to SOC 2. Many providers serving both need both.

How do IRAP and SOC 2 compare at a glance?

Dimension IRAP SOC 2
Owner Australian Signals Directorate (ASD) AICPA (United States)
What is assessed One system against the ISM Controls against the Trust Services Criteria
Where it applies Australia, government context US origin standard, used by customers worldwide
Outcome An assessment report and control matrix A CPA firm’s attestation report and opinion
Pass or fail No; the agency makes a risk based decision No; the auditor gives an opinion, no pass mark
Who decides The government authorising officer The buyer reads the report and decides
Typical trigger Selling cloud or SaaS to the Australian Government A customer’s risk or procurement requirement
Validity Reassess within 24 months for cloud providers Type II observes a period, commonly renewed annually

Can we reuse SOC 2 work for IRAP?

In part. A working SOC 2 control set, with its policies, access reviews, change management, monitoring and incident response, is real preparation for IRAP, because the same controls appear in the ISM and a mature evidence habit means less waiting on documentation, which is where most IRAP cost lies. What cannot be done is swap the report for the assessment.

The IRAP assessment still runs, against the ISM, on the provider’s specific system, and the agency still makes its own authorisation decision. The ISM control set is more prescriptive than the Trust Services Criteria, it is revised through the year, and it carries Australian Government requirements SOC 2 does not address. Cybernion provides independent IRAP assessments and readiness and SOC 2 readiness for Australian providers.

Frequently asked questions

Is IRAP the same kind of thing as SOC 2?

No. IRAP is an independent assessment of one system against the Australian Government Information Security Manual (ISM), ending in a report with no pass mark. SOC 2 is a licensed CPA firm’s attestation against the AICPA Trust Services Criteria. Different owners, different audiences.

Can SOC 2 replace an IRAP assessment for government work?

Usually not. Selling cloud or SaaS to the Australian Government at OFFICIAL Sensitive and above points to IRAP against the ISM. A SOC 2 report is useful assurance for many buyers, but it may not satisfy a government requirement that calls for IRAP.

Do we need both IRAP and SOC 2?

Often, where a provider sells to both audiences. IRAP is what allows sales into the Australian Government at higher classifications. SOC 2 is asked for by customers whose own risk or procurement process requires it. They answer to different buyers and can reinforce each other.

Is IRAP or SOC 2 easier to prepare for?

They differ in approach. IRAP assesses one system deeply against a prescriptive Australian control set that ASD revises through the year. SOC 2 tests the controls a provider commits to against chosen Trust Services categories over a period. Neither has a pass or fail in the IRAP sense.

Does SOC 2 work help with IRAP preparation?

In part. SOC 2 control evidence, policies and monitoring reduce IRAP preparation effort, which is where most IRAP cost lies. It does not remove the assessment itself, which still runs against the ISM on the provider’s specific system.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Infosec Registered Assessors Program (IRAP), ASD, cyber.gov.au, 2026
  2. Protective Security Policy Framework, protectivesecurity.gov.au, 2024
  3. Information Security Manual, cyber.gov.au, June 2026
  4. AICPA, 2017 Trust Services Criteria (with Revised Points of Focus, 2022), TSP section 100, aicpa-cima.com, 2022
  5. AICPA, SOC suite of services, aicpa-cima.com, accessed July 2026

Last updated: 3 July, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.