Cybernion
← Insights

IRAP

IRAP for Google Cloud: What's Assessed and What's Yours

3 July 2026 · Updated 5 Sept 2026

Google Cloud and Google Workspace have been independently assessed against the Australian Government’s Information Security Manual (ISM) at OFFICIAL and PROTECTED. That assessment covers the controls Google owns. The system built on Google Cloud, its configuration, identity, data and workload, is a separate scope that must be assessed under IRAP before an agency relies on it.

When an Australian government workload is deployed on Google Cloud, the platform’s IRAP assessment gives a foundation to build on, not a finished result. The useful question is which controls are inherited from Google and which still have to be proven.

Is Google Cloud already IRAP assessed at PROTECTED?

Yes. Google Cloud and Google Workspace have been independently assessed against OFFICIAL and PROTECTED ISM controls and found strongly aligned with the PROTECTED level requirements, spanning security roles, incident detection and management, physical and personnel security, system hardening, networking and cryptography. The services are delivered from the Australian regions, and the in scope list changes over time, so check Google’s current compliance documentation rather than treating any list as fixed.

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. In July 2020 the Australian Signals Directorate (ASD) retired the Certified Cloud Services List and released 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. Google’s assessment is an input to that decision. For the basics, see what an IRAP assessment is and the complete guide to IRAP assessment.

What does the Google Cloud IRAP assessment cover?

It covers the controls Google is responsible for: the physical data centres, the underlying infrastructure, network and cryptographic controls, and the operational security behind the in scope services. Those controls are independently assessed against the applicable ISM controls. That is the assurance a consumer inherits rather than reproduces.

It does not cover how the platform is used. The project and organisation configuration, the identity and access model, which services are enabled, how data is classified and protected, and how the workload is monitored are all the consumer’s, and that is where the consumer’s own assessment focuses. This is the same shared responsibility split that applies across all assessed cloud providers.

We’re deploying on Google Cloud. Do we still need our own IRAP assessment?

Yes. Google frames it as its responsibility for the infrastructure and the consumer’s for what runs on it. Under the ISM the consumer’s controls form a separate assessment scope.

Layer Google (assessed) The consumer (assessed separately)
Physical data centres and hardware Yes
Underlying infrastructure and virtualisation Yes
Service security controls as Google runs them Yes
The consumer’s project and organisation configuration Yes
Identity and access management Yes
Guest operating systems and patching the consumer manages Yes
The consumer’s data, its classification and encryption choices Yes
The consumer’s application, 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. Google’s capabilities such as Assured Workloads help enforce data residency and control constraints, but they support the consumer’s posture rather than replace the assessment.

How do we use Google Cloud’s IRAP assessment to shorten our own?

Inheritance is the method, and it is the same across providers. Confirm the data classification, define the assessment boundary so it captures only what the consumer owns, then map each applicable ISM control to Google (inherited, evidenced from its assessment) or the consumer (implemented and evidenced in the environment). The compliance documents in Audit Manager help draw that line for the services in use.

What remains after inheritance is the real scope, and using the platform assessment well keeps it smaller and cheaper than assessing a system built from bare infrastructure. In the Google Cloud assessments we run, much of that residual scope is identity and configuration rather than infrastructure. The same approach helps SaaS vendors building on Google Cloud and anyone gauging readiness first. Where a workload runs across multiple providers, the same inheritance logic applies on AWS and Azure.

Does Google Cloud being assessed at PROTECTED make our workload PROTECTED?

No. PROTECTED is the common bar and it is set by the data, confirmed with the owning agency, not by the platform. Google Cloud being assessed at PROTECTED does not lift the workload to PROTECTED, and it does not lower the bar if the data is OFFICIAL: Sensitive. Confirm the classification first, because it decides the ISM controls in the scope and therefore the cost and duration.

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

Frequently asked questions

Is Google Cloud IRAP certified?

There is no IRAP certificate, there is only an IRAP assessment leading to an IRAP report. Google Cloud and Google Workspace have been independently assessed against the ISM at OFFICIAL and PROTECTED. ASD retired the Certified Cloud Services List in 2020, so no provider is IRAP certified. The assessment supports the customer’s own risk decision, it does not grant an approval.

Is Google Workspace covered as well as Google Cloud?

Yes. Google Cloud and Google Workspace were both assessed against OFFICIAL and PROTECTED ISM controls. Check Google’s current documentation for the specific services in scope, as coverage changes over time.

Where do we get the Google Cloud IRAP documents?

Google Cloud provides its IRAP PROTECTED compliance documents through Audit Manager and the Compliance Reports Manager in the Google Cloud console.

We’re deploying on Google Cloud. Do we still need our own IRAP assessment?

Yes. Google’s assessment covers the controls Google owns. The system built on Google Cloud, its configuration, identity, data and workload, is a separate scope that must be assessed under IRAP before an agency relies on it.

What are Google Cloud Assured Workloads and do they replace an IRAP assessment?

Assured Workloads is a Google Cloud capability that helps enforce data residency and control constraints for regulated workloads. It supports a consumer’s compliance posture but it is not an IRAP assessment of the system and does not replace one.


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, Google Cloud, cloud.google.com, 2026
  2. Google Cloud IRAP assessment announcement, cloud.google.com, 2024
  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

Last updated: 5 September, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.