Cybernion
← Insights

ASD Essentials

ASD Essentials for Cloud

25 Oct 2026 · Updated 25 Oct 2026

ASD Essentials for cloud is the chapter of the ASD Essentials for organisations that deliver their technology environment entirely through software-as-a-service and platform-as-a-service, and do not run their own server or network infrastructure. It uses the same principles, actions and domains model as the other chapters, and addresses the shared responsibility model directly.

Who is the cloud chapter for?

Organisations whose technology runs entirely on SaaS and PaaS. ASD designed this chapter for organisations that deliver their technology environment through cloud services and do not operate their own server or network infrastructure. In practice that is the modern cloud-native business: it consumes platforms and applications rather than running data centres or managing operating systems and networks itself. If your environment is on-premises, hybrid or infrastructure-as-a-service, where you still run the operating systems and network, the enterprise IT chapter fits instead. Most organisations end up needing both over time; which chapter do I need helps you decide where to begin.

How does it handle the shared responsibility model?

It is built around it. In SaaS and PaaS, the organisation configures and governs a service it does not operate, so security is split between customer and provider. The cloud chapter’s actions are written for exactly that situation: they focus on what the organisation controls, configuration, identity, access and governance, rather than infrastructure it cannot touch. This matters because the most common cloud failures are misconfiguration and weak identity control on the customer side, not breaches of the provider’s platform. The chapter gives organisations a clear view of which responsibilities are theirs, which is a frequent source of confusion for teams new to cloud. For related ground, see IRAP shared responsibility in the cloud and ISO 27001 for SaaS.

What does the cloud chapter contain?

The same principles, actions and domains model, tuned for cloud. Like the other chapters, it applies principles (the security outcomes to achieve), actions (what to do, mapped to adversary techniques where relevant) and domains (groupings of assets with similar risk), with six technical domains and supporting asset scoping guidance for cloud. The principles, actions and domains model is consistent across the series, so an organisation that knows one chapter can read another quickly. The specific assets inside each domain reflect a cloud environment rather than on-premises systems, and the actions account for the controls a customer can actually apply to a service it configures but does not run.

How does it relate to the Essential Eight?

It carries the threat-informed thinking of the Essential Eight into cloud, where the Essential Eight did not fit well. The Essential Eight was designed for internet-connected, Windows-based enterprise IT, so it never translated cleanly to a SaaS or PaaS environment. The cloud chapter fills that gap: it applies the same outcome-focused approach to the environment a cloud-native business actually operates. For organisations moving workloads to cloud, it pairs naturally with existing cloud assurance work such as a cloud security checklist and, for government-facing providers, IRAP for SaaS and cloud providers. Cybernion helps cloud-native organisations adopt the chapter through its Essential Eight and ASD frameworks service.

How is the cloud chapter assessed and sequenced?

By outcome, and in priority phases, like the rest of the series. The cloud chapter groups its domains into priority phases that recommend the order of work, and assessment judges whether each action achieves its intended outcome rather than scoring a maturity level. The ratings and approach follow the shared assessment process, and planning uses the implementation planning guide. Because cloud environments change quickly, the chapter’s emphasis on configuration, identity and continuous visibility is where most of the ongoing effort goes.

Frequently asked questions

Who is the cloud chapter for?

Organisations that deliver their technology environment entirely through software-as-a-service and platform-as-a-service, and do not operate their own server or network infrastructure.

How is it different from the enterprise IT chapter?

The enterprise IT chapter suits on-premises, hybrid and infrastructure-as-a-service, where you run the stack. The cloud chapter is for SaaS and PaaS environments and addresses the shared responsibility model directly.

Does it cover the shared responsibility model?

Yes. Its actions are written for environments where the organisation configures and governs a service it does not operate, so it is clear which responsibilities are yours and which are the provider’s.


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.

If your environment is cloud-native and you want help adopting the chapter, talk to us.

Sources:

  1. ASD Essentials for cloud, cyber.gov.au, October 2026
  2. Which chapter should I start with?, cyber.gov.au, 15 October 2026
  3. ASD Essentials, cyber.gov.au, October 2026

Last updated: 25 October, 2026

Talk to us about your engagement

A scoped proposal within one business day.