ASD Essentials for OT: Moving On From the Essential Eight

In October 2026 the Australian Signals Directorate published ASD Essentials, the evolution of the Essential Eight, with a chapter written for operational technology. I help critical infrastructure operators measure their OT against it and plan the uplift. I'm based in Brisbane and work Australia-wide.

What ASD Essentials Is

ASD Essentials, published on 15 October 2026, is the Australian Signals Directorate's evolution of the Essential Eight. Instead of one set of eight mitigation strategies for enterprise IT, it is a series of chapters for different environments. The first three are Essentials for enterprise IT (the direct successor to the Essential Eight), Essentials for OT, and Essentials for cloud.

Every chapter has the same three layers: principles, the security outcomes to achieve, drawn from ASD's Information Security Manual; actions, what must be done to achieve them, in technology-agnostic terms; and domains, the groups of systems the actions apply to. Priority phases set the order in which the domains are tackled. There are no maturity levels: an assessment rates each action in each domain as not assessed, not effective, partially effective or fully effective.

What the OT Chapter Asks For

Essentials for OT is written for operators of complex control, automation and safety systems in critical service sectors such as power, water and wastewater, transport and large-scale industry. It introduces vital OT: the critical systems it is unacceptable to have offline for an extended period. Many of its actions are about keeping vital OT running safely when something around it is compromised, for example:

  • Being able to isolate vital OT and keep operating safely for a defined period, and exercising that isolation regularly
  • Making the services vital OT depends on, such as credentials, storage and policy, independent of systems outside the OT environment
  • Ending all remote access in the OT DMZ rather than routing it directly into OT, with phishing-resistant MFA for anyone authenticating across the perimeter
  • A register of assets that cannot or will not be patched, with the compensating protections and the residual risk accepted for each
  • Firmware, configuration, logic and project backups held per site, and the ability to recover vital systems without supplier support
  • Safety systems segmented from the rest of OT at a network boundary, not by device configuration alone

The chapter has eight domains: two capability domains that apply throughout (governance and culture, and visibility and response) and six technical ones. For OT, ASD sequences the technical domains to put safe operation first:

Priority phase 1

Boundary services, and critical processes and services: the pathways into OT from less trusted networks, and the systems whose compromise would have the most serious safety, operational, environmental or service consequences.

Priority phase 2

Privileged environments and identity services: administrative and privileged access to OT, where an initial compromise would otherwise escalate. In OT, every device inside a privileged environment counts as privileged.

Priority phase 3

Business systems: the enterprise functions that support operations, addressed after the domains that protect critical operations so they cannot become a pathway to them.

The sixth technical domain, user devices, is a warning rather than a target: ASD says typically configured desktops and laptops should not be used in OT environments at all.

Moving From the Essential Eight

Essential Eight maturity levels don't convert into Essentials ratings, because the two assess different things. ASD's transition guidance is to use existing implementation and assessment evidence as the starting point for a gap analysis, and organisations part-way through an Essential Eight uplift can start moving across without discarding that work. ASD is maintaining both frameworks during the transition period.

The Essential Eight was designed for internet-connected enterprise IT, and ASD has said it may not suit operational technology. For control systems, the OT chapter is the better yardstick. Many of its actions, such as DMZs at the OT perimeter, segmentation between sites and safety systems, and controlled remote access, are the controls an IEC 62443 zone and conduit design specifies, so work done to IEC 62443 counts towards both.

Essentials and the SOCI Act CIRMP

The CIRMP rules still name the Essential Eight Maturity Model: Maturity Level One under the baseline rules and Maturity Level Two under the enhanced rules. They haven't been updated for the Essentials series yet. The Cyber and Infrastructure Security Centre's CIRMP guidance, though, says the Essentials series published by ASD, implemented in full, is considered an equivalent cyber security framework for the purposes of sections 8(5) and 8A(4) of the rules, and encourages responsible entities to consider transitioning to it.

ASD's own advice is to keep meeting your current regulatory obligations until regulators communicate any change. See SOCI Act compliance for OT for the wider obligations.

How I Help

Gap analysis against Essentials for OT

Agreeing the scope, then rating each action against your OT assets in each domain, with the evidence behind every rating and the specific gaps for anything short of fully effective. Existing Essential Eight, AESCSF and IEC 62443 evidence is reused wherever it is still current.

Identifying vital OT

Working out which systems cannot be offline for long, what they depend on, including services outside the OT environment, and where isolation would be enacted.

Uplift roadmap in priority-phase order

Prioritised actions to close the gaps, starting with boundary services and critical processes, then privileged and identity services, then business systems, and sequenced around outages, projects and budget cycles.

Isolation planning

Designing how vital OT is isolated and kept running for the period your continuity plans require, documenting the procedure, and setting up the regular isolation exercises the chapter calls for.

One control set

Mapping the same OT controls to Essentials, your SOCI Act CIRMP, the AESCSF and IEC 62443, so the work counts once across all of them.

This page summarises ASD's Essentials announcement, the Essentials for OT chapter and its transition guidance, and the CISC's CIRMP guidance. It is not legal advice; confirm your obligations with your advisers or the CISC.Last reviewed November 2026.

Frequently Asked Questions

Is the Essential Eight being retired?

ASD published ASD Essentials in October 2026 as the evolution of the Essential Eight, and is maintaining both frameworks on cyber.gov.au during a transition period. Its announcement gives no retirement date. Keep meeting any regulatory or contractual obligation that names the Essential Eight until it changes.

Does the Essential Eight apply to OT?

It was designed for internet-connected enterprise IT networks, and ASD has said it may not suit operational technology. Essentials for OT is the chapter of the new series written specifically for operational technology and the operators of critical infrastructure.

Do Essential Eight maturity levels carry over?

No. Essentials has no maturity levels: each action is rated not assessed, not effective, partially effective or fully effective in each domain it applies to. Existing Essential Eight evidence is still useful as the starting point for a gap analysis.

Can we use Essentials for our SOCI Act CIRMP?

The CIRMP rules haven't been updated and still name the Essential Eight, but the CISC's CIRMP guidance says the Essentials series, implemented in full, is considered an equivalent cyber security framework under sections 8(5) and 8A(4). Confirm your position with your advisers or the CISC.

Is your gap analysis an official ASD assessment?

No. I'm an independent consultant, not part of ASD. ASD's assessment process guide is written for organisations assessing their own environment, and my gap analysis follows it.