Under IRAP, the ISM controls split across the cloud stack. A provider is assessed for the controls it owns, and the consumer built on it is assessed for the controls it configures and runs. The Cloud Controls Matrix records who owns each control and which the consumer inherits versus implements. Inheritance reduces the consumer’s scope, but it is assessed, not assumed.
Building on a cloud platform that is already IRAP assessed does not make the system on top of it assessed. The reason is shared responsibility: the controls are divided between the provider and the consumer, and each side is assessed for its own. The Cloud Controls Matrix is where that split is written down.
What is shared responsibility under IRAP?
Shared responsibility is the division of Information Security Manual (ISM) controls between the cloud provider and the consumer built on top of it. The provider owns and is assessed for the controls it operates, the physical data centres, the platform, the service security as the provider runs it. The consumer owns and is assessed for the controls it configures and runs, its identity, its data, its application, its configuration of each service.
Neither party’s assessment covers the other’s controls. A provider’s assessment says the service can be operated securely; it does not say a consumer has operated it securely. That distinction is the whole of shared responsibility, and it is why an assessed platform does not make your workload assessed. The same logic holds on Azure and Google Cloud. For the wider picture, see the complete guide to IRAP assessment.
In an IRAP assessment, who owns which ISM controls?
The split follows who operates the control. The table sets out the common division, though the exact line moves with how a service is configured.
| Control area | Provider (assessed) | Consumer (assessed separately) |
|---|---|---|
| Physical data centres and hardware | Yes | |
| Virtualisation and platform infrastructure | Yes | |
| Service security controls as the provider runs them | Yes | |
| The consumer’s configuration of each service | Yes | |
| Identity, credential and access management | Yes | |
| The consumer’s data, its classification and encryption choices | Yes | |
| The consumer’s application, its logging, monitoring and backup | Yes |
The line is not fixed. A managed service or a more abstracted platform shifts more controls to the provider; a raw infrastructure service leaves more with the consumer. This is why the split is assessed for the specific system rather than read off a generic diagram, and why defining the boundary so it captures only what the consumer owns is central to keeping scope proportionate.
What is the IRAP Cloud Controls Matrix (CCM)?
The Cloud Controls Matrix, or CCM, is the artefact used under IRAP to record the implementation and effectiveness of ISM controls for a cloud service. It captures which controls the provider implements and which the consumer is responsible for configuring in accordance with the ISM, and it provides indicative guidance on scoping a cloud assessment and on inheritance under a shared responsibility model.
That guidance is indicative, not definitive. It is interpreted under IRAP in the context of the assessed system, because two consumers using the same service can end up with different responsibilities depending on how they configure it. The CCM is the cloud specific form of the control matrix that accompanies every IRAP assessment report, and it is read by the technical staff who integrate the service.
How does IRAP control inheritance work in the cloud?
Inheritance is where a consumer relies on a control the provider owns and has been assessed for, rather than implementing and evidencing it itself. It is the biggest lever on a consumer’s scope, because every inherited control is one it does not have to test. Where the provider owns a control and its assessment confirms it, the consumer references that assessment in its own.
Inheritance is assessed, not assumed. The assessment checks how far a control has actually been inherited, because a modified inherited control may no longer be effective. And a consumer does not automatically inherit every control a provider makes available; it inherits the ones it actually relies on and leaves the ones it implements differently for its own assessment. The layered model means each layer, provider then consumer, references the layer below it so the authorising officer sees the full picture.
How do we use shared responsibility to plan an IRAP assessment?
Confirm the classification of the data, define the boundary so it captures only the controls the consumer owns, then map each applicable ISM control to either the provider, inherited with evidence from its assessment, or the consumer, implemented and evidenced in its environment. What remains is the real scope the assessment examines, and it is where most of the effort and cost lies.
The same logic applies to a consuming agency, a SaaS provider building on a platform or a managed service provider in the middle of the stack. To have the consumer side of a shared responsibility split assessed, we provide IRAP assessments and readiness.
Frequently asked questions
What is shared responsibility in an IRAP assessment?
Shared responsibility is the split of ISM controls between a cloud provider and the consumer built on it. The provider owns and is assessed for the controls it operates, and the consumer owns and is assessed for the controls it configures and runs. Neither party’s assessment covers the other’s controls.
What is the IRAP Cloud Controls Matrix (CCM)?
The Cloud Controls Matrix, or CCM, is the artefact used under IRAP to record the implementation and effectiveness of ISM controls for a cloud service. It captures which controls a provider implements and which a consumer is responsible for configuring, and it gives indicative guidance on scoping and inheritance.
What is IRAP control inheritance in the cloud?
Control inheritance is where a consumer relies on a control a cloud provider owns and has been assessed for, rather than implementing and evidencing it themselves. Inheritance reduces the consumer’s scope, but it is assessed not assumed, because a modified inherited control may no longer be effective.
Does our cloud provider’s IRAP assessment cover our system?
No. The provider’s assessment covers the controls the provider owns. The consumer’s system built on the platform, its configuration, identity, data and workload, is a separate scope that must be assessed. The provider’s assessment reduces the controls the consumer must demonstrate, not the need for its own assessment.
Who decides which party owns each ISM control in an IRAP assessment?
It is worked out under IRAP with the assessed entity’s delegate and recorded in the Cloud Controls Matrix. The CCM’s guidance on inheritance is indicative and must be interpreted in the context of the specific system, because how a service is configured changes who is responsible for what.
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.
Sources:
- Cloud services, IRAP, ASD, cyber.gov.au, 2026
- Cloud assessment and authorisation, ASD, cyber.gov.au, 2026
- IRAP Common Assessment Framework, Australian Signals Directorate, April 2025
- Information Security Manual, cyber.gov.au, June 2026
Last updated: 3 July, 2026
