Essentials for OT
IDE-04 Security risk identification
Map how your OT could be attacked, so you understand its security risks. Find and analyse every way in, the security boundaries and connections, and the points where OT could be fully isolated. Keep this under continuous review.
Reviewed 18 October 2026 · Current to ASD's Essentials for OT, published 15 October 2026
The principle
Security risks for an organisation and their systems (infrastructure, operating systems, applications and data) are identified, including by using current strategic and sector-specific cyber threat intelligence and threat modelling, and are documented along with any associated risk management decisions.
The action
ASD's actions are quoted as published in Essentials for OT. ASD has not given them IDs, so they are numbered by position.
Action 1 of 1
Identify and analyse the OT attack surface, security boundaries and connectivity, including the points through which complete isolation can be enacted, and review these inputs on a continuous basis.
In plain English: Find and analyse OT's attack surface (the ways an attacker could get in), security boundaries and connections, including where OT could be fully isolated. Review them continuously.
- Domains
- Visibility and response
See all 34 principles in Essentials for OT, or read our OT guide.
Sources
The ASD publications this page quotes.
Quoted ASD material © Commonwealth of Australia 2026, licensed under CC BY 4.0.
Everything else on this page is written by Control Stack.





