Cybernion
← Insights

IRAP

IRAP for AWS: What the PROTECTED Assessment Covers

3 July 2026 · Updated 5 Sept 2026

AWS has had its cloud services independently assessed against the Australian Government’s Information Security Manual (ISM), with more than 160 services assessed at PROTECTED as at the 2025 assessment. That assessment covers the controls AWS owns. The system built on AWS, its configuration, identity, data and workload, is a separate scope that must be assessed under IRAP before an agency relies on it.

Building an Australian government workload on AWS raises an obvious question: if AWS is already IRAP assessed at PROTECTED, is the consumer’s system covered too? It is not. The gap between the two is where most of the assessment work lies.

Is AWS already IRAP assessed at PROTECTED?

AWS has had its cloud services independently assessed against the ISM, with services assessed up to and including PROTECTED. The 2025 assessment listed more than 160 AWS services at PROTECTED, delivered from the Australian regions, and the in scope list grows at each assessment cycle. Treat any fixed count as a snapshot and check the current IRAP package in AWS Artifact for the definitive list.

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. The Australian Signals Directorate (ASD) retired the Certified Cloud Services List in July 2020 and replaced it with ASD’s Cloud Assessment and Authorisation framework, under which a provider is assessed and each consuming agency makes its own risk based decision to use the service. The AWS assessment is an input to that decision, not the decision itself. For the wider picture, see the complete guide to IRAP assessment and what an IRAP assessment actually is.

What does the AWS IRAP assessment actually cover?

It covers the controls AWS is responsible for, including the ones AWS inherits from the suppliers of the components that support its services: the physical data centres, the hardware and the hypervisor, the network fabric, and the security controls built into the services as AWS operates them. Those controls are independently assessed against the applicable ISM controls and the result is documented. That is real assurance, and it is the part a consumer does not have to prove directly.

What it does not cover is anything the consumer configures or builds on top. The assessment shows the service can be operated securely, not that it has been operated securely. That distinction is the core of the shared responsibility model.

We’re building an AWS native application. Do we still need an IRAP assessment?

Yes. AWS describes security “of” the cloud as its responsibility and security “in” the cloud as the consumer’s. Under the ISM, the controls the consumer owns are a separate assessment scope. The split looks like this.

Layer AWS (assessed) The consumer (assessed separately)
Physical data centres and hardware Yes
Virtualisation and host infrastructure Yes
Service security controls as AWS runs them Yes
Configuration of each service Yes
Identity and access management Yes
Guest operating systems, patching and network rules the consumer sets Yes
The consumer’s data, its classification and encryption choices Yes
The consumer’s application and its logging, monitoring and backup Yes

As per ASD’s Cloud Assessment and Authorisation framework, a Commonwealth entity must have its own system on the cloud assessed under IRAP, including its responsibilities under the shared responsibility model. The consumer’s scope is where classification, boundary and evidence decisions are made, which is also where most IRAP cost lies. The same split applies when AWS underlies an MSP’s managed service.

How do we use the AWS assessment to shorten our own?

Inheritance is how to picture the relationship between an application and the platform beneath it. Where AWS owns a control and its assessment confirms it, a consumer can inherit that control and reference the AWS assessment rather than test it again. AWS publishes an IRAP documentation pack, reference architectures and consumer guidance to help map which controls are inherited and which are kept. That mapping is the single biggest lever on assessment effort. In the AWS assessments we run, a clear inheritance map is what separates a short assessment from a long one.

The practical path is to confirm the classification of the data, using the agency customer’s direction or the contract, then define the system boundary so it captures only the services and configuration the consumer owns, then map each applicable ISM control to either AWS (inherited, with evidence from its assessment) or the consumer (implemented and evidenced in the environment). What remains is the real scope the assessment examines. The same logic applies to SaaS and cloud providers building their own products on AWS.

Does AWS being assessed at PROTECTED make our workload PROTECTED?

No. PROTECTED is the common bar for government workloads, and it is set by the data, not the platform. AWS being assessed at PROTECTED does not raise the workload to PROTECTED, and it does not lower the bar if the data is at OFFICIAL: Sensitive. Confirm the classification of the information the system handles with the owning agency first, because it drives the ISM controls in scope and therefore the cost and duration of both assessments.

For a PROTECTED workload on AWS that needs the consumer side assessed independently, we provide IRAP assessments and readiness.

Frequently asked questions

Is AWS IRAP certified?

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. AWS has had its cloud services independently assessed against the ISM, with services assessed up to PROTECTED. ASD retired the Certified Cloud Services List in 2020, so no provider is IRAP certified. The assessment informs the customer’s own risk decision, it does not grant an approval.

We’re building an AWS native application. Do we still need our own IRAP assessment?

Yes. The AWS assessment covers the controls AWS owns. The application built on AWS, with its configuration, identity, data and code, is a separate scope that must be assessed under IRAP before an agency will rely on it.

How many AWS services are assessed at PROTECTED?

More than 160 services were listed at PROTECTED in the 2025 assessment, and the number changes each cycle. Check the current IRAP package in AWS Artifact for the definitive in scope list rather than relying on a fixed number.

Where do we get the AWS IRAP documentation?

The IRAP assessment report and the supporting documentation pack, including reference architectures and consumer guidance, are available to AWS customers through AWS Artifact in the AWS Management Console.

Can we reuse the AWS IRAP assessment for our own?

Yes, in part. A consumer can inherit the controls AWS owns and reference its assessment in its own, which cuts the effort. A separate IRAP assessment is still needed of the controls the consumer owns under the shared responsibility model.


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 compliance, Amazon Web Services, aws.amazon.com, 2026
  2. IRAP services in scope, AWS, aws.amazon.com, 2026
  3. Cloud assessment and authorisation, ASD, cyber.gov.au, 2025
  4. Cloud services, IRAP, ASD, cyber.gov.au, 2025
  5. Information Security Manual, cyber.gov.au, June 2026
  6. Service counts are point in time from the 2025 AWS assessment and change each cycle; the current list is in AWS Artifact

Last updated: 5 September, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.