Cybernion
← Insights

IRAP

IRAP Common Assessment Framework Explained

3 July 2026 · Updated 3 July 2026

The IRAP Common Assessment Framework is the Australian Signals Directorate (ASD) document that sets a standard, system agnostic method for every IRAP assessment. It defines four stages, plan and prepare, define the boundary, assess the controls and produce the report, along with the rules on boundaries, sampling, evidence quality and the standardised control outcomes IRAP assessors must use. It gives no pass mark; the authorising officer decides.

Two IRAP assessors looking at the same system should reach comparable findings. The Common Assessment Framework is how ASD makes that hold. It sets the method every IRAP assessor follows regardless of whether the system is a cloud service, a gateway or an on premise build. This walks through what it covers and the four stages it defines.

What is the IRAP Common Assessment Framework?

It is a document authorised by ASD and supported through the IRAP Policy and Procedures. It provides a standardised methodology for assessing ICT systems and services irrespective of environment, so the same principles apply whether the system is a SaaS platform, a gateway or a data centre. IRAP assessors are required to follow it.

The framework is written for IRAP assessors, but consuming entities and system owners can read it to understand the process and what the assessment will expect. It draws on similar terminology to the United States NIST SP 800-53A, using assessment objects, specifications, mechanisms, activities and personnel, and the methods examine, interview and test. For the wider context, see what an IRAP assessment actually is and the complete guide to IRAP assessment.

What are the four stages of an IRAP assessment?

The framework sets four stages, and the assessment report must clearly articulate what happened in each. The table sets them out.

Stage What happens
1. Plan and prepare ASD is informed of the engagement, a conflict of interest declaration is lodged, scope, resources and methods are agreed, and the ISM version to use is confirmed
2. Define the assessment boundary With the entity’s delegate, what is in scope is fixed, exclusions are documented with justification, and shared responsibility and control inheritance are identified
3. Assess the controls Evidence is gathered by examining, interviewing and testing, then an outcome and justification is recorded for each applicable control
4. Produce the IRAP assessment report The boundary, strengths, weaknesses, control outcomes, limitations and recommendations are documented, alongside the control matrix

Two rules from stage 1 matter to anyone planning an engagement. The conflict of interest declaration must be lodged at least seven business days before the assessment begins, and the latest ISM release available before the assessment starts must be used. If two ISM releases pass during a long assessment, a delta is conducted against the current version.

How do IRAP assessors decide a control’s outcome?

The framework fixes the language. Standardised outcomes are used so every report reads the same way, and each outcome carries a written justification, including not applicable and not implemented.

  • Effective: the implementation meets the intent of the control
  • Ineffective: the implementation does not adequately meet the intent
  • Alternate control: the intent is met through a compensating control
  • Not assessed: the control has not yet been assessed
  • Not applicable: the control does not apply to the system
  • No visibility: adequate assurance could not be gained, which an authorising officer may treat as ineffective from a risk perspective
  • Not implemented: the organisation has not implemented the control, generally for a documented business or technical reason

The assessment also weighs the assessment degree, the depth and coverage of evidence, and may use sampling only to support direct assessment, not to skip components that need individual evaluation.

Does the Common Assessment Framework give a pass or fail?

No, it does not produce a pass or fail. An IRAP assessment does not rate risk, certify, accredit or recommend a system for authorisation. It describes the potential impact of a weakness and leaves the risk judgement to the authorising officer, because risk acceptance is a business decision that belongs to the consuming agency. The assessment is an input to that decision, not the decision itself.

This is also why the assessment boundary is defined carefully in stage 2. The authorisation boundary the officer signs off can be equal to or smaller than the assessment boundary, but never larger.

How do we use the IRAP Common Assessment Framework to prepare?

Read it for the documents and evidence the assessment will ask for, which is the best preparation guide there is. Stage 1 lists the documents expected under IRAP, from the System Security Plan (SSP) and annex to incident response plans, risk documents and configuration baselines. Having them accurate and approved before the assessment starts is what keeps it short. Stage 3 also governs how ISM controls are structured and selected for the system in scope, and stage 2 is where shared responsibility in the cloud is resolved and documented.

For an organisation that wants an assessment run to the framework, or readiness support before one, Cybernion provides IRAP assessments and readiness.

Frequently asked questions

What is the IRAP Common Assessment Framework?

It is the document ASD publishes that sets a standardised method for IRAP assessments across any system type, whether cloud, gateway or on premise. It defines the four assessment stages, the boundary rules, sampling, evidence quality and the standardised control outcomes assessors must use.

What are the four stages of an IRAP assessment?

Plan and prepare, define the assessment boundary, assess the controls, and produce the IRAP assessment report. All four are worked through under IRAP, informing ASD of the engagement and lodging a conflict of interest declaration before starting, then defining scope, testing controls and documenting findings.

What control outcomes does the IRAP Common Assessment Framework use?

One of effective, ineffective, alternate control, not assessed, not applicable, no visibility or not implemented is recorded for each control, each with a written justification. No visibility can be treated as ineffective from a risk perspective by an authorising officer.

Does the Common Assessment Framework give a pass or fail?

No. An IRAP assessment does not rate risk, certify or recommend a system for authorisation. It reports control effectiveness, strengths, weaknesses and recommendations. The authorising officer makes the risk based decision to authorise the system for operation.

Who does the Common Assessment Framework apply to?

It is written for IRAP assessors, who are required to follow it when conducting assessments. Consuming entities and system owners can read it to understand the process, what the assessment will ask for and how findings are produced.


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. IRAP Common Assessment Framework, Australian Signals Directorate, April 2025
  2. IRAP Consumer Guide, Australian Signals Directorate, July 2025
  3. Infosec Registered Assessors Program (IRAP), cyber.gov.au, 2026
  4. Information Security Manual, cyber.gov.au, June 2026

Last updated: 3 July, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.