Cybernion
← Insights

ASD Essentials

Which ASD Essentials Chapter Do I Need?

25 Oct 2026 · Updated 25 Oct 2026

Choose the ASD Essentials chapter that matches the technology environment you operate: enterprise IT, cloud, or operational technology. Many organisations need more than one over time, with no set order. Within each chapter, domains are grouped into priority phases that recommend the order to address them, sequencing effort toward the biggest and fastest reduction in risk.

How do I choose a chapter?

Start from what you actually operate, then weigh obligations, gaps and risk. ASD suggests four questions. First, what do you operate: a clear enough view of your technology environments, the functions they support and the assets they hold, not a full asset discovery. Second, what are you required to do: regulatory, contractual and sector obligations often point to a particular environment, though an obligation sets a floor, not the priority order. Third, where is the biggest gap between the current state and the outcomes the principles describe. Fourth, where is the greatest risk, judged by the consequence and likelihood of compromise. An organisation may find one chapter applies, several apply to different parts of its environment, or a single business function depends on assets under more than one chapter. The three chapters are enterprise IT, cloud and operational technology.

Enterprise IT or cloud: which first?

It depends on how much of the stack you operate versus consume. Where an organisation runs on-premises infrastructure, a hybrid environment or infrastructure-as-a-service, the enterprise IT chapter is the starting point: the organisation still owns the operating systems, applications, identity infrastructure and network architecture that chapter addresses, even if some of it runs on another party’s hardware. Where an organisation is predominantly on platform-as-a-service or software-as-a-service and needs clarity on which responsibilities are its own and which belong to the provider, the cloud chapter fits, because it addresses the shared responsibility model directly. Most organisations need both over time; the question is which to begin with, not which to adopt.

Why might operational technology come first?

Because OT often carries higher risk and more technical debt. Operational technology environments tend to have long asset lifecycles, with systems in service for decades, availability and safety requirements that constrain patching and change windows, and legacy protocols or unsupported platforms still in use. An organisation may find its OT risk is materially higher than its enterprise IT risk, especially where OT supports critical infrastructure that delivers essential services. A large gap on its own is not a reason to start somewhere; it is one input alongside the consequence and likelihood of compromise. But where OT underpins safety or essential services, it often deserves early attention.

What are priority phases?

They are a recommended sequence for a chapter’s domains, not a rating. Each chapter groups its domains into priority phases that set the order ASD recommends addressing them, reflecting where effort delivers the greatest and fastest reduction in risk. The order is informed by the adversary tradecraft used most often to gain and extend access, by the control gaps ASD sees most commonly exploited, and by what organisations can realistically implement quickly. Priority phases are a sequencing mechanism: they do not represent assurance over control effectiveness, compliance against a standard, or maturity against an adversary class. An organisation at an early phase is not at a lower standard than one at a later phase; it is at a different point in the same programme. This is a real departure from the Essential Eight maturity levels, which did rate maturity.

Yes, with reasons recorded. The sequence is a starting position, not a constraint. Threat intelligence may show a later domain being actively targeted and needing attention now; an obligation may require certain capabilities first; or a technology refresh may make it efficient to address a domain early. Two things hold regardless: domains later in the sequence still need to be done eventually, and domains that apply continuously across all levels should be established early, because they are the foundation for everything else. ASD advises documenting any decision to change the order, which helps when explaining the approach to executives, boards or regulators. Cybernion helps organisations choose chapters and sequence the work through its Essential Eight and ASD frameworks service.

Frequently asked questions

Do I have to use every ASD Essentials chapter?

No. Use the chapters that match the environments you operate. Many organisations need more than one over time, but there is no set order and no requirement to adopt all of them.

Should I start with enterprise IT or cloud?

On-premises, hybrid or infrastructure-as-a-service points to the enterprise IT chapter. Predominantly platform- or software-as-a-service points to the cloud chapter, which addresses shared responsibility.

What are priority phases?

They are the recommended order for addressing a chapter’s domains, based on where effort delivers the greatest and fastest risk reduction. They sequence the work; they are not a maturity rating.


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 you are not sure which chapter to begin with, talk to us.

Sources:

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

Last updated: 25 October, 2026

Talk to us about your engagement

A scoped proposal within one business day.