Cybernion
← Insights

ASD Essentials

ASD Essentials: Principles, Actions and Domains

26 Oct 2026 · Updated 26 Oct 2026

The ASD Essentials uses three layers in every chapter: principles, actions and domains. Principles describe the security outcomes to achieve, drawn from the ISM and ASD’s Modern Defensible Architecture. Actions describe what to do to meet a principle, mapped to MITRE ATT&CK where relevant. Domains describe the business functions and assets an action applies to.

How do the three layers work together?

They answer a sequence: what outcome, what to do, and where. In the ASD Essentials, the principle establishes the intended security outcome, the action describes what the organisation needs to do to achieve it, and the domain establishes the assets and functions the action applies to. The layers are designed to be used together, so an action is implemented in the context of a particular domain rather than as a standalone requirement. This is the structural change from the Essential Eight, which named controls directly: the Essentials separates the enduring outcome from the environment-specific way of reaching it, which is what lets one framework cover enterprise IT, cloud and operational technology.

What are principles?

Principles are the security outcomes an organisation should achieve. They give the framework a stable foundation: the intent of a principle stays the same from one chapter to the next, even where the actions used to achieve it differ. ASD draws the principles from the cyber security principles in its Information Security Manual and aligns them with ASD’s Modern Defensible Architecture, so the Essentials is consistent with ASD’s wider guidance rather than a separate idea. Not every principle is relevant to every chapter; each chapter identifies the principles that apply to its environment. Because principles describe outcomes rather than products, they age well as threats and technology change, which is the central reason ASD moved to this model in the case for change.

What are actions, and why map them to MITRE ATT&CK?

Actions are the administrative and technical requirements that implement a principle. They can vary between chapters, because different technology environments carry different risks and constraints; ASD selects the actions for each environment against the relevant threat model, operational requirements and commercial viability. Where appropriate, an action is mapped to techniques in the MITRE ATT&CK knowledge base, which makes explicit the adversary behaviour the action is meant to counter. That mapping is useful in practice: it lets a security team trace a control back to the real attacker techniques it defends against, rather than implementing a control on faith. It also keeps the framework honest about why each action earns its place.

What are domains?

Domains are groupings of business functions and assets that share similar risk. Shared risk means comparable exposure and consequence of compromise, not that every asset carries an identical rating. A domain is a logical grouping, not a network or organisational boundary: assets in one domain may be spread across different systems, locations, suppliers or parts of the organisation. Domains are used consistently across the series, though the specific assets in a domain can vary by chapter and environment. Each chapter identifies the domains relevant to its environment and maps actions to the domains where they apply. Domains also drive how progress is sequenced and reported, through the priority phases explained in which chapter do I need.

How does this help an organisation in practice?

It focuses effort where it reduces the most risk, in the right environment. Because actions attach to domains, an organisation applies security where assets share real exposure, rather than spreading the same measures evenly across everything it owns. Because principles are environment-neutral and actions are environment-specific, a team working in cloud and in OT can aim at the same outcomes without pretending the two look alike. And because actions map to adversary techniques, the work connects to the threats described in the 2025-26 threat report. Cybernion helps organisations apply the model through its Essential Eight and ASD frameworks service and broader virtual CISO support.

Frequently asked questions

What are principles in the ASD Essentials?

Principles describe the security outcomes an organisation should achieve. They are drawn from the ISM cyber security principles and align with ASD’s Modern Defensible Architecture.

What are actions, and how do they relate to MITRE ATT&CK?

Actions are the administrative and technical requirements used to meet a principle. Where appropriate, they are mapped to MITRE ATT&CK techniques to show the adversary behaviour they address.

What is a domain?

A domain is a grouping of business functions and assets that share similar risk. It is a logical grouping, not a network or organisational boundary.


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 want help applying principles, actions and domains, talk to us.

Sources:

  1. What is the Essentials?, cyber.gov.au, 15 October 2026
  2. ASD Essentials, cyber.gov.au, October 2026
  3. Information Security Manual, cyber.gov.au, 2026

Last updated: 26 October, 2026

Talk to us about your engagement

A scoped proposal within one business day.