Essentials for OT
IDE-06 Resilience requirement identification
Your safety functions may rely on links to outside alarm systems. Find and record the communication and alert systems that carry them. Make sure those paths stay reliable when communications are degraded or down.
Reviewed 18 October 2026 · Current to ASD's Essentials for OT, published 15 October 2026
The principle
Resilience requirements for systems (infrastructure, operating systems, applications and data) are identified and documented.
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 document the communication and alerting infrastructure that carries safety functions to external alarm systems, and assure the reliability of those paths where communication services are degraded or unavailable.
In plain English: Find and record the communication and alert systems carrying safety functions to outside alarm systems. Make sure those paths stay reliable when communications are degraded or down.
- Domains
- Critical processes and services
- Boundary services
- MITRE ATT&CK
- Loss of safety
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.
MITRE ATT&CK® technique names and IDs: © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. See MITRE's ATT&CK terms of use.
Everything else on this page is written by Control Stack.