Cybernion
← Insights

IRAP

IRAP for SaaS and Cloud Providers: What You Need to Know

21 June 2026 · Updated 3 July 2026

IRAP for SaaS and cloud providers is an independent assessment of a cloud service against the Information Security Manual (ISM), where the controls are assessed by IRAP assessors. It checks the controls the provider owns under the shared responsibility model, not the hyperscaler infrastructure beneath it. It is an assessment, not a certification, and there is no pass mark.

Do SaaS and cloud providers need an IRAP assessment?

If a service stores, processes or communicates Australian Government information at OFFICIAL: Sensitive or above, an agency cannot use it until it has been IRAP assessed. The trigger is the data and the buyer, not the provider’s size. The Protective Security Policy Framework, in its Table 21, requires outsourced IT and cloud services that handle OFFICIAL: Sensitive, PROTECTED and SECRET information to be IRAP assessed before they hold government data. A startup with ten staff and a single hyperscaler tenancy is in the same position as a large vendor. What changes is the boundary and the volume of evidence, not the obligation. Plenty of founders assume IRAP is only for the AWS and Azure tier. It is not. Building on a hyperscaler means its own assessment gives a head start on the controls it owns, and the provider assesses the rest: see IRAP for AWS, Microsoft Azure and Google Cloud. Where the requirement itself is still in question, start with whether an IRAP assessment is needed and how the classification of the data is set.

What does an IRAP assessment cover in a cloud service?

It covers the controls the provider is responsible for under the ISM, captured in the Cloud Controls Matrix. ASD’s Cloud Controls Matrix records the implementation status of each applicable control and marks where the cloud consumer, not the provider, configures the service to meet the ISM. The output is the assessment report and that control matrix. In practice the assessment looks at the provider’s configuration, application logic, data handling, identity, access and logging, and the operational practices around them. It does not re-assess the physical data centre or the hypervisor the hyperscaler already had assessed. The point is to show an agency exactly which controls the provider implements and how, which is the same evidence base described in what an IRAP assessment is.

How does the shared responsibility model work for IRAP?

This is where most cloud IRAP work goes wrong. The hyperscaler’s IRAP assessment covers its infrastructure layer only. Everything built on top of it is a separate scope. AWS or Azure being assessed at PROTECTED does not make a SaaS built on it PROTECTED. The provider inherits the controls the platform implements, then owns and must evidence the rest, which is what the provider’s own IRAP assessment exists to check. ASD’s cloud guidance is explicit that the IRAP report sets out the shared responsibility model, and that a consuming agency must also have its own system, built on that service, assessed, with TOP SECRET the exception. The table below shows where the line falls.

Layer Who is responsible Who assesses it
Physical data centre, hardware, hypervisor Hyperscaler (infrastructure provider) The hyperscaler’s own IRAP assessment
Platform and managed service configuration Shared: provider defaults, consumer settings The provider’s IRAP assessment, via the Cloud Controls Matrix
The provider’s application, data handling, identity, logging The SaaS or cloud provider The provider’s IRAP assessment
The system the agency builds on the service The consuming agency The agency’s own IRAP assessment

What classification should a cloud provider be assessed at?

The classification is set by the government information the service will hold, and the owning agency decides it, not the provider. The common levels are OFFICIAL: Sensitive, PROTECTED and SECRET. The ISM control set is the same at OFFICIAL: Sensitive and PROTECTED; what changes are the physical security, personnel clearance and network obligations, and those step up sharply at SECRET. Assess at the level the buyers actually need. Being assessed at PROTECTED when customers only handle OFFICIAL: Sensitive adds cost and clearance overhead a provider may never recover. For the full picture across cost, process and timelines, see the IRAP assessment guide.

How often does a cloud provider need an IRAP reassessment?

A cloud provider needs reassessment at least every 24 months, and sooner on material change. PSPF requirement 0109 expects cloud services to have had an IRAP assessment within the previous 24 months against the latest ISM at the time of assessment, and ASD’s cloud guidance says the same: reassess at least every two years, or when an event changes the security posture. An IRAP assessment is point in time. The authorisation that follows is not. Treat the gap between assessments as continuous work, because the ISM updates through the year and the platform does not stand still. The detail on how long an assessment takes and on maintaining posture between assessments both matter here.

What do SaaS providers get wrong about IRAP?

SaaS providers get three things wrong, repeatedly. They call the result a certification. It is not; ASD ceased certifying systems in 2020 and there is no pass mark, so the “IRAP certified” label on a website is wrong, and assessors notice, which is why it helps to be clear on whether IRAP is a certification. They assume the hyperscaler’s assessment covers them. It covers the infrastructure, not their tenancy. And they scope the whole platform when only one product or environment touches government data, which inflates the control count and the bill. A tight boundary is the cheapest decision a provider makes, and it is set early in how the assessment process works.

Is an IRAP assessment of a cloud service a certification?

No. IRAP is an independent assessment against the Information Security Manual, not a certification, and there is no pass mark. ASD ceased certifying systems in 2020. The consuming agency’s authorising officer makes the decision to operate.

Does our hyperscaler’s IRAP assessment cover our SaaS product?

No. A hyperscaler’s IRAP assessment covers its own infrastructure layer. A provider’s configuration, application, identity and data handling are above that line and are a separate scope that must be assessed.

Can a small SaaS company get an IRAP assessment?

Yes. The obligation is driven by the government data the service handles and the agency buying it, not by the provider’s size. A tight assessment boundary keeps the control count and cost manageable for a smaller provider.

How long is a cloud IRAP assessment valid for?

There is no formal expiry, but PSPF requirement 0109 expects cloud services to have been assessed within the previous 24 months against the latest ISM, so providers reassess at least every two years or on material change.


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. ASD, Cloud assessment and authorisation, 2025
  2. ASD, IRAP cloud services and the Cloud Controls Matrix, 2025
  3. ASD, IRAP Consumer Guide, July 2025
  4. Protective Security Policy Framework, requirements 0086 and 0109 and Table 21, 2025
  5. ASD, Information Security Manual, June 2026

Last updated: 21 June, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.