Essentials for OT
RES-01 Cyber security incident planning
Plan for incidents so OT and the business can keep going. Update continuity plans for the impact of isolation, and respond with tested and approved OT procedures. Keep key documents, emergency secrets and contacts at each site in a form that works without the affected systems.
Reviewed 18 October 2026 · Current to ASD's Essentials for OT, published 15 October 2026
The principle
Cyber security incident response, business continuity and disaster recovery plans for systems (infrastructure, operating systems, applications and data) support continued business operations during cyber security incidents, and the resumption of normal business operations following cyber security incidents.
The three actions
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 3
Update business and operational continuity plans to reflect the impact that isolation will have on business and operational processes.
In plain English: Update your business and operational continuity plans. Show how isolating OT will affect the way the business and operations run.
- Domains
- Visibility and response
Action 2 of 3
Use documented, tested and approved OT incident response procedures when responding to cyber security incidents, covering situations such as safety events, setting out who participates in response and recovery, including third parties, loss of visibility, and workstation compromise.
In plain English: Use written, tested, approved OT incident response procedures, covering situations such as safety events, lost visibility and a hacked workstation. Name who responds and recovers, including third parties.
- Domains
- Visibility and response
Action 3 of 3
Establish and maintain a document management capability for system documentation, and retain per-site copies of playbooks, drawings, installation, reset and configuration instructions, break-glass secrets and keys, and emergency contact information in a form that does not depend on the systems being recovered.
In plain English: Set up and keep system document management. Keep per-site copies of playbooks, drawings, installation, reset and configuration instructions, emergency secrets, keys and contacts, usable without the affected systems.
- 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.





