An MSP handling Australian Government data at OFFICIAL: Sensitive or above needs its own IRAP assessment of the services it manages, scoped to its side of the shared responsibility model. It inherits assessed controls from any underlying cloud provider, is assessed for the controls it owns, and leaves the customer’s retained controls to a separate scope. The boundary is set to the MSP’s responsibilities.
A Managed Service Provider (MSP) is in the middle of the stack: on top of a cloud or infrastructure provider, underneath the customer that consumes the service. That position decides what an MSP’s IRAP assessment covers and where its boundary falls. This explains when an MSP needs an assessment, what it covers, and how shared responsibility works across the layers.
Does an MSP need an IRAP assessment?
If the MSP stores, processes or communicates Australian Government data at OFFICIAL: Sensitive or above, then yes, the services it manages should be assessed. The Protective Security Policy Framework (PSPF) requires outsourced information technology and cloud services holding government data to be IRAP assessed against the Information Security Manual (ISM) before an agency relies on them, and a managed service is outsourced IT in exactly that sense.
The assessment covers what the MSP is responsible for, not the whole of its customer’s environment. An MSP does not get assessed for controls its cloud provider owns, nor for controls the customer retains. It gets assessed for the services it manages and the way it administers and secures them. For the wider picture, see the complete guide to IRAP assessment and what an IRAP assessment actually is.
How does IRAP shared responsibility work for managed services?
IRAP takes a layered approach, and an MSP is usually the middle layer. The shared responsibility model splits the ISM controls across the parties, and each layer’s assessment references the layers below it.
| Layer | Who is assessed | For what |
|---|---|---|
| Infrastructure or cloud provider | The underlying provider | The infrastructure and platform controls it owns |
| Managed service | The MSP | The services it manages, configures and administers on top |
| Consumer | The consuming agency | The controls the agency retains on its side |
The MSP’s assessment should reference the underlying provider’s assessment for the controls it inherits and specify the responsibilities it carries, so the consuming agency’s authorising officer can see the full picture across the layers. Where the MSP manages the customer’s use of a cloud service, its assessment covers the aspects it is responsible for designing, configuring or managing.
What does an MSP’s IRAP assessment cover?
An MSP’s IRAP assessment covers the controls the MSP owns. In practice that means the services it manages, how it configures them, how it administers them, and the security controls it operates. Secure administration is central here, because an MSP’s privileged access into customer environments is one of the most sensitive parts of the arrangement. The assessment looks closely at how administration is performed, segmented and monitored, including the end user computing devices used for privileged activity, since a jump server does not on its own protect the exposure of the underlying device.
The MSP’s corporate network may itself come into scope depending on how administration is performed and how well it is segmented from the managed environment. That is a boundary judgement made under IRAP with the MSP’s delegate, not something the MSP declares unilaterally.
Can an MSP inherit its cloud provider’s IRAP assessment?
In part, and inheritance is the biggest lever on scope. Where the underlying cloud provider owns a control and has been assessed for it, the MSP can inherit that control and reference the provider’s assessment rather than re testing it. That is the point of the layered model.
Inheritance is not automatic, though. The assessment checks whether the MSP has modified an inherited control or implemented its own version, because a modified inherited control may no longer be as effective as the provider’s assessment suggests. Third parties do not automatically inherit every control a provider makes available; they inherit what they actually rely on and implement. Mapping which controls are inherited, which the MSP implements and which the customer retains is where the assessment effort concentrates, much as it does for SaaS and cloud providers. If the underlying platform is AWS, Azure or Google Cloud, each has its own IRAP assessment the MSP can reference for the controls it inherits.
Who sets the boundary for an MSP’s IRAP assessment?
The assessment boundary is set under IRAP in agreement with the MSP’s delegate, and getting it right is what keeps the layers from overlapping or leaving gaps. It should capture the services the MSP manages and its administration practices, and document clearly what the underlying provider owns and what the customer retains. Confirm the classification of the data in scope with the customer first, because it drives the applicable controls and therefore the cost and duration of the assessment.
For an MSP handling government data that needs the services it manages assessed, Cybernion provides IRAP assessments and readiness.
Frequently asked questions
Does an MSP need an IRAP assessment?
If a managed service provider stores, processes or communicates Australian Government data at OFFICIAL: Sensitive or above, the services it manages fall to be IRAP assessed as outsourced IT services under the PSPF. The assessment covers the controls the MSP owns, not the whole of its customer’s environment.
What does an MSP’s IRAP assessment cover?
It covers the controls the MSP is responsible for under the shared responsibility model, the services it manages and how it configures, administers and secures them. Controls owned by an underlying cloud provider are inherited, and controls the customer retains are a separate scope. The boundary is set to the MSP’s responsibilities.
How does IRAP shared responsibility work for managed services?
IRAP takes a layered approach. An underlying infrastructure or cloud provider is assessed for its layer, the MSP is assessed for the services it manages on top, and the consuming agency is assessed for what it retains. Each layer references the layers below it, and control inheritance is assessed rather than assumed.
Can an MSP inherit its cloud provider’s IRAP assessment?
In part. Where the underlying provider owns and has been assessed for a control, the MSP can inherit it and reference that assessment. Inheritance is not automatic, the assessment checks whether the MSP has modified an inherited control or implemented its own, because that changes the control’s effectiveness.
Who owns the boundary for an MSP IRAP assessment?
The assessment boundary is defined under IRAP in agreement with the MSP’s delegate. It should capture the services the MSP manages and its administration practices, and clearly document what the underlying provider owns and what the customer retains, so the layers do not overlap or leave gaps.
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:
- IRAP Common Assessment Framework, Australian Signals Directorate, April 2025
- IRAP Consumer Guide, Australian Signals Directorate, July 2025
- Cloud assessment and authorisation, ASD, cyber.gov.au, 2026
- Protective Security Policy Framework, protectivesecurity.gov.au, 2025
Last updated: 3 July, 2026
