Cybernion
← Insights

Security

How the IRAP Assessment Process Works

5 June 2026 · Updated 21 June 2026

An IRAP assessment follows four stages from the IRAP Common Assessment Framework: plan and prepare, define the assessment boundary, assess the controls against the ISM, and produce the report and control matrix. The assessment leads each stage, and the organisation’s role is access, documentation, evidence and people.

The assessment leads every stage. The organisation’s job is to make access, documentation, evidence and the right people available when each stage calls for them. The four stages are not ambiguous, and knowing what each one demands is the difference between engaging with the process and reacting to it.

By the opening session the preparation should be done: the documentation package handed over, system access provisioned, and the agreed boundary in writing. The practical question at that point is what actually happens now.

Stage What the assessment does What the organisation contributes
1. Plan and prepare Submits the Assessment Record and Conflict of Interest declaration to ASD, confirms timelines and methods, identifies the applicable frameworks Agree the schedule, name the people, provision access
2. Define the boundary Documents and validates the boundary, maps the shared responsibility model, records inclusions and exclusions Confirm the boundary through its delegate
3. Assess the controls Examines, interviews and tests each applicable ISM control and assigns an implementation outcome Make documentation, evidence and people available
4. Produce the report Writes the Security Assessment Report and Controls Matrix with findings, recommendations and justifications Review the draft, prepare to use it for authorisation

Four stages of IRAP Assessment

What happens in IRAP Stage 1, plan and prepare?

Planning happens before any assessment work, and it sets how the rest will run. The Assessment Record and Conflict of Interest declaration are submitted to ASD via the ACSC Partner Portal at least seven business days before the assessment starts.

During planning the assessment confirms timelines, milestones and access requirements with the organisation. It identifies the frameworks and policies that apply to the system, including the Information Security Manual (ISM), the Protective Security Policy Framework (PSPF) and any other relevant guidance such as the Hosting Certification Framework. It settles which assessment methods will be used, how evidence will be collected and protected, and whether any managed service providers need to be brought into the process. An assessment plan may be produced to formalise this and shared with the organisation. Where a security assessment team is involved, team composition and responsibilities are set here. Good preparation before this point shortens everything that follows.

In practice, Stage 1 confirms the agreed boundary in writing, sets a check-in cadence such as weekly, and names the system administrators and security personnel who will be available for interviews during Stage 3.

What happens in IRAP Stage 2, define the assessment boundary?

The assessment boundary is defined in agreement with the organisation’s delegate. The boundary is set in detail before the assessment, but within the process itself Stage 2 is where it is formally documented and validated before any control assessment begins.

Stage 2 reviews the system architecture, identifies the components in scope, maps the shared responsibility model with any third party providers, and confirms the boundary is complete and appropriate. Inclusions and exclusions are both documented. The boundary is reviewed and validated again as the assessment progresses if new information emerges.

What happens in IRAP Stage 3, assess the controls?

This is the substantive work of the assessment and the longest stage, and it places the most demand on the organisation’s people. Evidence is collected and reviewed to determine whether each applicable ISM control is operating effectively within the boundary, using three methods.

Examine means reviewing documents, configurations, system designs, policies and procedures. This is where the SSP-A, architectural diagrams and configuration exports are used directly. Interview means discussions with people across the organisation, including system owners, system administrators, security operations staff and end users, to understand how controls work in practice and to locate further evidence. Test means exercising controls under defined conditions to compare actual behaviour against expected behaviour, such as attempting access with an account that should be blocked, testing backup restoration, or verifying that a cryptographic configuration enforces the expected protocol.

For each control the assessment assigns one of seven standardised implementation outcomes.

Outcome What it means
Effective The control meets the intent of the ISM control objective
Ineffective The control does not adequately meet the intent of the control objective
Alternate control The objective is met through a different control than the one specified
Not assessed The control has not yet been assessed
Not applicable The control does not apply to the system within the boundary
No visibility The evidence available did not allow the control to be confirmed, equivalent to ineffective
Not implemented The control has not been put in place, generally for a documented business or technical reason

IRAP Implementation Statuses

Every outcome, including not applicable and not implemented, carries a written justification. The assessment does not rate risks. It describes what it found and the impact a weakness or gap may have; the risk rating and the authorisation decision belong to the system authoriser. The assessment only covers what is implemented at the time of the assessment. Programs of work underway may be noted in the report but are not assessed.

Stage 3 commonly runs across three weeks. The SSP-A and configuration documentation are examined in the first week, the system administrators and security lead are interviewed in the second, and technical testing and log review are completed in the third. A control will rate no visibility where the only evidence available is a policy document that restates the control rather than demonstrates it. Any such gap is raised during the assessment, not sprung as a surprise in the final report.

What happens in IRAP Stage 4, produce the report?

Once control assessment is complete, the Security Assessment Report and the Controls Matrix are produced. The report documents the assessment boundary, an overview of the system and environments assessed, the security strengths and weaknesses, any limitations that affected evidence gathering or testing, and the outcome of each control with its justification and supporting evidence.

The report includes recommendations. IRAP recommendations are descriptive: they explain the issue and its implications, giving the organisation enough context to decide how to address it, without prescribing a specific solution or dictating how a recommendation must be implemented. The report does not recommend whether the system should be authorised. That decision is for the authorising officer.

Before the report is finalised it is reviewed internally and by the organisation’s stakeholders. The final report and Controls Matrix are provided to the assessed entity and a copy is submitted to ASD. The draft report commonly reaches the organisation around two weeks after Stage 3 concludes. Working through the findings before it is finalised turns the report into the foundation for the authorisation package. Cybernion runs independent IRAP assessments end to end, and the complete IRAP guide sets the process in context.

Two deliverables of an IRAP assessment


Frequently Asked Questions

How long does an IRAP assessment take?

It varies with system complexity, scope size, evidence availability and how familiar the assessment team is with the environment. Thorough preparation before the assessment starts is the most effective way to reduce the overall timeline.

What are the seven IRAP implementation outcomes?

Effective, Ineffective, Alternate Control, Not Assessed, Not Applicable, No Visibility, and Not Implemented. Every outcome must carry a written justification. Not Implemented is distinct from Ineffective: Not Implemented means the control has not been put in place, usually for a documented business or technical reason.

Does the IRAP assessment tell us which findings are highest priority?

The IRAP assessment describes the potential impact of each weakness or gap but does not rate risks on behalf of the organisation or the consuming agency. Key vulnerabilities should be identified clearly in the report so the authorising officer and the organisation can prioritise them, but the risk rating itself is the organisation’s responsibility.

Can we fix issues found during the IRAP assessment before the report is finalised?

The IRAP assessment covers what is implemented at the time of assessment. Remediations completed after the assessment period may be noted as programs of work underway but cannot be assessed as implemented unless there is time and evidence to verify the change within the assessment timeframe. Raise it during the assessment if a finding is identified early in the process.

Who receives the final IRAP assessment report?

The assessed entity receives the report and controls matrix. A copy also goes to ASD as part of the quality assurance process. The assessed entity then uses the report as the basis for the authorisation package submitted to the system authoriser.


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

Last updated: 21 June, 2026

Talk to us about your engagement

A scoped proposal within one business day.