ASD Essentials for operational technology is the chapter of the ASD Essentials for operational technology (OT) environments. It gives baseline cyber security guidance that can be applied progressively, covering process automation, instrumentation, cyber-physical operations and industrial control systems for operators responsible for control, automation and safety across critical service sectors.
What does the OT chapter cover?
Operational technology, the systems that run physical processes. ASD defines the OT covered here broadly: process automation, instrumentation, cyber-physical operations and industrial control systems (ICS). The chapter is written for operators of OT responsible for complex systems control, automation and safety across critical service sectors, the organisations whose technology keeps water, energy, transport, manufacturing and similar services running. It provides baseline guidance intended to be applied progressively, so an operator can improve security posture over time rather than all at once. This is a different audience and environment from the enterprise IT chapter, and the Essentials treats it as its own chapter for that reason.
Why does OT need its own chapter?
Because OT environments carry constraints enterprise IT does not. OT often has significant technical debt: long asset lifecycles mean systems stay in service for decades, availability and safety requirements constrain when and how systems can be patched or changed, and legacy protocols and unsupported platforms frequently remain in operation because replacing them needs capital and planned downtime. A control that is routine in enterprise IT, such as frequent patching or rebooting, can be unsafe or impossible in a plant that must run continuously. The Essentials handles this through its model: the principle, the security outcome, stays the same, while the actions are selected for the OT environment’s threat model, operational requirements and safety constraints. This is the core argument in the case for change.
Why might OT be the place to start?
Because its risk is often higher, given what it controls. An organisation may find its OT environment carries materially higher risk than its enterprise IT, because OT underpins critical infrastructure that supplies essential services to the public, where the consequence of compromise can be physical harm or loss of an essential service. ASD is clear that a large gap alone is not a reason to start somewhere; it is one input alongside the consequence and likelihood of compromise. But where OT supports safety or essential services, it often deserves early attention. For organisations captured by critical infrastructure obligations, this connects to the SOCI Act and a CIRMP risk management program.
How does the OT chapter relate to the Essential Eight?
It applies the Essentials approach where the Essential Eight never fit. The Essential Eight was built for internet-connected, Windows-based enterprise IT and was never designed for operational technology, a gap ASD acknowledged for years. The OT chapter closes it by bringing the outcome-based, threat-informed model to OT directly, rather than forcing enterprise IT controls onto plant equipment. It uses the same principles, actions and domains structure as the other chapters, with the specifics tuned to OT. For sector context, see cyber security for energy and utilities, manufacturing and mining and resources.
How is the OT chapter assessed and sequenced?
By outcome, in priority phases, with safety front of mind. Like the rest of the series, the OT chapter groups 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, following the shared assessment process. The progressive, baseline framing matters here: operators are expected to improve posture over time within the constraints of safety and availability, not to make sweeping changes that could endanger operations. Cybernion helps OT operators adopt the chapter and align it with critical infrastructure obligations through its Essential Eight and ASD frameworks service.
Frequently asked questions
What does the OT chapter cover?
Operational technology, including process automation, instrumentation, cyber-physical operations and industrial control systems, for operators responsible for control, automation and safety across critical service sectors.
Why is OT treated separately from enterprise IT?
OT has different constraints: long asset lifecycles, safety and availability requirements that limit patching and change, and legacy protocols and platforms. The same security outcome has to be achieved in a very different environment.
Does the Essential Eight apply to OT?
The Essential Eight was designed for Windows-based enterprise IT, not OT. The OT chapter applies the Essentials’ outcome-based approach to operational technology directly.
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 operate OT and want help adopting the chapter, talk to us.
Sources:
- ASD Essentials for operational technology, cyber.gov.au, October 2026
- Which chapter should I start with?, cyber.gov.au, 15 October 2026
- The case for change, cyber.gov.au, 15 October 2026
Last updated: 25 October, 2026
