Cybernion
← Insights

IRAP

IRAP Assessment: The Complete Australian Guide

21 June 2026 · Updated 7 Nov 2026

IRAP, the Infosec Registered Assessors Program, is run by the Australian Signals Directorate. Under IRAP, a specific system is independently assessed against the Information Security Manual and its strengths, weaknesses and residual risks are reported. It is an assessment, not a certification, and the agency that consumes the system makes the decision to authorise it.

This guide works through the questions providers and agencies ask about IRAP, in the order they usually come up: whether an assessment is needed, what it produces, what it costs and how long it takes, how it compares with ISO 27001, and what happens from scoping through to the authorisation decision and beyond. Each section gives the short answer and links to the detailed article where there is more to say.

Do we need an IRAP assessment?

An assessment is needed when two things are true at once: the system stores, processes or transmits classified Australian Government information, and the agency that owns that information requires the system to be assessed before it goes live. One without the other is not enough. For cloud and SaaS providers the bar is firmer, because PSPF requirement 0109 expects an IRAP assessment within the previous 24 months before an agency uses the service. The trigger is the buyer and the data, not the size of the company, so a small SaaS vendor handling PROTECTED data carries the same obligation as a hyperscaler. The full decision path, including layered assessments and subcontractor cases, is in Do you need IRAP to sell to government.

Source: ASD IRAP Consumer Guide, July 2025; PSPF requirement 0109.

What is an IRAP assessment, and what is it not?

It is an independent, point in time assessment of one system against the ISM, carried out under IRAP by ASD endorsed assessors. It produces two documents, the assessment report and the control matrix. It is not a certification, there is no pass mark, and a clean assessment does not by itself approve anything. ASD stopped certifying systems in 2020, and the authorising officer in the consuming agency now reads the report, weighs the residual risks, and decides whether to authorise the system to operate under PSPF requirement 0086. IRAP assessors are often described as “ASD accredited”, although they are endorsed, and they assess and report rather than approve or certify. The detail is in What an IRAP assessment is, and what it is not.

IRAP at a glance
What it is An independent, point in time assessment of a system against the ISM
Who runs the program The Australian Signals Directorate (ASD)
Who assesses ASD endorsed IRAP assessors, independent of the system
Classifications OFFICIAL: Sensitive, PROTECTED, SECRET
What is produced The IRAP assessment report and the controls (cloud controls) matrix
Who decides The consuming agency’s authorising officer (PSPF requirement 0086)
How current Within 24 months for cloud (PSPF requirement 0109), plus on material change

If our cloud provider is already IRAP assessed, do we still need an IRAP assessment?

Yes. An IRAP assessment of Microsoft, Amazon Web Services or Google Cloud covers their infrastructure layer only. Under the shared responsibility model, the customer’s configuration, application logic and data handling fall above that line and are assessed separately, so inheriting a provider’s controls is not the same as having the system itself assessed. This is where we see teams most often misjudge scope, and it is usually the first gap the assessment finds. More on how this works for software providers is in IRAP for SaaS and cloud providers.

What classification level applies to an IRAP assessment?

The agency that owns the data sets its classification, not the provider, and it has to be confirmed before any scoping decision is made. The ISM control set is the same at OFFICIAL: Sensitive and PROTECTED. What changes are the physical security, personnel clearance and network obligations, which grow at PROTECTED and add to the evidence reviewed under the assessment. Getting this wrong is expensive, because the classification drives both the scope and the cost.

How much does an IRAP assessment cost?

As a rough budgeting guide, an IRAP assessment usually falls into these ranges:

  1. A simple OFFICIAL: Sensitive or PROTECTED system: $30,000 to $40,000
  2. A moderately complex OFFICIAL: Sensitive or PROTECTED system: $40,000 to $60,000
  3. A highly complex OFFICIAL: Sensitive or PROTECTED system: $60,000 to $100,000 or more
  4. A SECRET system: roughly $10,000 to $20,000 above the equivalent range above, depending on complexity

Four factors determine the $ figure: the information classification, the systems in scope, how mature the relevant documentation and processes are, and the level of support available during the assessment. Treat these as indicative only; the accurate figure always comes from a scoped quote.

The drivers are broken down in IRAP assessment cost.

How long does an IRAP assessment take, and how often is it needed?

ASD publishes no fixed duration, because the IRAP Common Assessment Framework defines the stages rather than a number of weeks. As an indicative figure, a moderately complex assessment usually runs 12 to 16 weeks from engagement to final report, often with 6 to 8 weeks of readiness work beforehand, assuming evidence is ready, scope is clear and the right people are available throughout. Poorly defined scope, unclear shared responsibility and late architectural changes are the usual causes of delay. The authorisation that follows is not permanent. Cloud providers reassess within 24 months under PSPF requirement 0109, against the ISM current at the time of assessment. The clock runs from the assessment date, and while an older report is not automatically invalid, an agency can rely on it less as it ages, so 24 months is the outer limit agencies work to. Any material change to the system can trigger an earlier review.

IRAP or ISO 27001: which do we need?

They are complementary, not interchangeable. ISO 27001 certifies an information security management system and is recognised internationally; IRAP assesses one specific system against the ISM for Australian Government use. There is meaningful overlap, often put at around 60 to 70 per cent at the control intent level, so a mature ISO 27001 program is genuine preparation for IRAP. What an organisation cannot do is substitute the certificate for the assessment, and the same applies to a SOC 2 report, which can supply reusable evidence but does not replace an independent assessment of the ISM controls. The comparison, and what evidence can be reused, is in IRAP vs ISO 27001.

How do we choose an IRAP assessor, and what is the independence rule?

Start with the ASD register of endorsed assessors, but treat it as a starting point, not a selection criterion. Every registered assessor meets ASD’s minimum bar; what varies is technical depth, familiarity with the environment, independence and availability. Independence is not optional. IRAP assessors cannot have contributed to the design, build or documentation of the system they assess, and a conflict of interest declaration is lodged with ASD at least seven business days before the assessment begins. How to choose well is in How to choose an IRAP assessor.

How do we define the IRAP assessment boundary?

The boundary is the set of systems, people, processes and technologies that will be assessed. It is defined and agreed with the provider before substantive work begins. A tight, well defined boundary keeps the control count and the cost down; a broad one inflates both, which is why the boundary is the single biggest lever the organisation controls. See How to define the IRAP assessment boundary.

How do we prepare for an IRAP assessment?

Preparation is the work done before the assessment starts: current documentation, gathered evidence, and the right people available. Expect to have a System Security Plan and SSP annex, a Security Risk Management Plan, a continuous monitoring plan and an incident response plan in place. Organisations that arrive without this groundwork stretch the timeline and create evidence gaps that have to be recorded as constraints. An IRAP readiness review finds and closes ISM gaps before the assessment clock starts, and the IRAP readiness checklist sets out what to have in place.

What are the four stages of the IRAP assessment process?

The assessment runs in four stages from the IRAP Common Assessment Framework: plan and prepare, define the boundary, assess the controls against the ISM, and produce the report. IRAP assessors lead each stage, while the organisation provides access, documentation, evidence and people. This is the work a Cybernion IRAP assessment follows from scoping to the final report. The stage by stage detail is in How the IRAP assessment process works.

What is in the IRAP report and the control matrix?

The assessment produces two documents. The assessment report sets out the system’s strengths, weaknesses and residual risks for the authorising officer. The control matrix, a derivative of the System Security Plan annex, records the implementation status of each applicable ISM control with the justification. Together they give the agency what it needs to make a risk based decision. See Understanding the IRAP report and the control matrix.

What is in the IRAP authorisation package, and who decides?

The authorisation package is the set of documents the authorising officer uses to decide whether to approve the system to operate. The assessment report is central to it, but it is not the whole package. The officer weighs the residual risks against the organisation’s risk appetite, and can decline to authorise a system that has completed an assessment. See Preparing the IRAP authorisation package.

What happens after an IRAP assessment: managing risk and holding posture?

Findings become a plan of action and milestones, which records what was found, what has been decided about each item, who owns it and by when. The assessment is point in time, while the system, the ISM and the threat environment keep moving. Holding posture between assessments, rather than treating authorisation as a finish line, is what makes the next 24 month cycle an update instead of a rebuild. See IRAP POAM and risk management and Maintaining IRAP posture between assessments.

IRAP assessment: frequently asked questions

What does an IRAP assessment produce?

Two documents: the IRAP assessment report, written for authorising officers and risk owners, and the controls matrix (the cloud controls matrix for cloud systems), written for the technical teams integrating the system. The matrix is a derivative of the System Security Plan annex.

In an IRAP assessment, are the ISM controls the same at OFFICIAL: Sensitive and PROTECTED?

Yes. The ISM control set is the same at both classifications. What changes between them is the physical security, personnel clearance and network obligations, not the control catalogue.

Who owns the risk in an IRAP assessment?

The consuming agency. Its authorising officer accepts the residual risk and makes the decision to operate under PSPF requirement 0086. An IRAP assessment is an independent assessment, not an approval.

Can an IRAP assessment be sped up?

Yes, through the parts the organisation controls: a tight, well defined boundary, confirmed data classification, mature controls, and evidence ready before the assessment starts. In our experience preparation is the cheapest part of an IRAP engagement.

What causes IRAP assessments to run late?

Poorly defined scope, unclear shared responsibility, incomplete documentation or evidence, and architectural changes made during the assessment.

Does ISO 27001 or SOC 2 replace an IRAP assessment?

No. ISO 27001 certifies a management system and SOC 2 reports on controls against the Trust Services Criteria. Both can provide reusable evidence, but the ISM controls still have to be independently assessed under IRAP for Australian Government use.

Does a TOP SECRET system go through commercial IRAP?

No. TOP SECRET systems are handled inside accredited government environments and assessed by ASD assessors or their delegates, not through the normal commercial cloud IRAP route.


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. We aren’t always chasing a transaction.

Sources:

  1. ASD IRAP Consumer Guide, July 2025
  2. IRAP Common Assessment Framework, April 2025
  3. Information Security Manual, June 2026
  4. Protective Security Policy Framework, including Table 21 and requirements 0086 and 0109, 2024
  5. Cloud assessment and authorisation, Australian Signals Directorate, 2024

Last updated: 7 November, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.