Skip to content
Frameworks
ASD Essentials

ASD Essentials for enterprise IT actions

ASD Essentials for enterprise IT: 58 actions under 28 principles, applied across 8 domains, with technical domains sequenced in 3 priority phases.

Reviewed 16 October 2026 · Current to ASD Essentials for enterprise IT, October 2026 · 58 actions across 28 principles

At a glance

Published by
Australian Signals Directorate (ASD)
Who it applies to
Enterprise IT environments. ASD publishes separate chapters for cloud services and for operational technology.
Structure
58 actions under 28 principles in 5 functions, applied across 8 domains.
Where to start
Start with the Phase 1 domains, Boundary services and Identity services. ASD's phases order the domains, not the actions.What's in each domain?

How it is structured

  1. 5functions
  2. 28principles
  3. 58actions
  4. 8domains

Actions per function

  • Govern8
  • Identify3
  • Protect34
  • Detect9
  • Respond4

Actions by principle

Every action in ASD's order, grouped by function and principle. ASD recommends working through the domains phase by phase: choose a domain to see the actions that apply to it.

What's in each domain?

ASD places an asset by the role it performs, not by who owns or runs it, and an asset belongs in every domain that describes it. Include development, testing and staging environments too.

Phase 1
  • Boundary services “Does it broker connectivity or data flows across a boundary between environments?”
  • Identity services “Does it anchor decisions about who and what to trust through authentication, authorisation or identity lifecycle functions?”
Phase 2
  • Critical processes and services “Does it directly deliver a primary organisational outcome or contribute to the health or safety of personnel or the community?”
  • Privileged environments “Does it enable, broker or govern elevated control over other systems?”
Phase 3
  • Business systems “Does it support day-to-day operations without being individually critical?”
  • User devices “Does it provide the general workforce with direct access to the environment?”
All phases
  • Governance and culture includes cyber security strategies, policies and procedures, awareness and training programs, security roadmaps and risk registers.
  • Visibility and response includes asset registers, incident response plans and procedures, and detection and response platforms.

Quoted as published in ASD's Implementation planning guide.

Domain
Phase 1
Phase 2
Phase 3
All phases

Showing all 58 actions

Govern

Identify

Protect

Detect

Respond

Guides and tools

Frequently asked questions

What is ASD Essentials for enterprise IT?

It is the enterprise IT chapter of the ASD Essentials series, which the Australian Signals Directorate published on 15 October 2026 and describes as an evolution of the Essential Eight. It sets out 58 actions that achieve 28 cyber security principles, grouped in five functions: Govern, Identify, Protect, Detect and Respond. Control Stack explains each action in plain English, with implementation tips, audit tips and mappings.

What are domains and priority phases?

Each action applies in one or more of eight domains. The six technical domains are sequenced in three priority phases: Boundary services and Identity services first, then Critical processes and services and Privileged environments, then Business systems and User devices. ASD calls the phases "a sequencing mechanism, not a rating". The two capability domains, Governance and culture and Visibility and response, apply in every phase. Because the phases order domains rather than actions, an action that applies in several domains comes up in each of their phases.

Does it cover cloud services?

This is ASD's enterprise IT chapter. ASD publishes a separate cloud chapter for environments delivered through software-as-a-service (SaaS) and platform-as-a-service (PaaS), and a chapter for operational technology (OT), and expects most organisations to need both the enterprise IT and cloud chapters over time. Control Stack covers the enterprise IT chapter.

Why do the principles have ISM identifiers?

The principles come from ASD's Information Security Manual and keep their ISM identifiers, such as GOV-01, for traceability. The numbers are not an order of work.