TRUST ATLAS WORKSHEET
Escalation tree
NIS2 · Step 3 · Build significant incident workflows- Who prepares it
- Incident response + legal
- When to prepare it
- At incident and in exercises
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Event or activity
- Unusual activity detected in support export portal
- First action and owner
- On-call engineer opens a restricted incident case and preserves logs.
- Decision owner and backup
- Privacy lead or legal duty contact will determine reporting.
- Handoff and clock
- Send incident ID, UTC timestamp and known scope immediately.
- Validation
- Exercise completed and backup contact reached.
Gather first
- Named roles, on-call contacts and authority
- Realistic use cases and deadlines
- Service and vendor dependencies
How to prepare it
- Start with the event or decision and identify who acts first, who has approval authority and who covers absences.
- Write the sequence of handoffs and the information each recipient needs. Name the channel, timing and escalation if no one responds.
- Rehearse a case and record what broke. Fix missing contacts, duplicate ownership or gaps before approving the playbook or role map.
Review
Every decision has one accountable person, a backup and a practical route to reach them.
Handoff
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.