Who decides,
who isolates, who notifies?
A playbook answers that per incident type — as a tested sequence, from the decision through to communication. We write playbooks for your real systems and responsibilities, with the notification deadlines under NIS2, GDPR and DORA built in, and test them in a tabletop exercise before they go into the binder.
What is included.
So that nobody has to improvise in an incident.
Incident taxonomy
Which incident types are relevant to you, and how they are detected and classified.
Playbook per type
Roles, decision points, technical steps, communication, notification duties with deadlines, evidence preservation.
Interfaces
Providers, insurer, law firm, authorities — contacts, contracts, escalation paths.
Test and maintenance
A tabletop run per playbook; a maintenance process with an owner and a review cadence.
Five steps,
one deliverable.
Taxonomy
Define incident types and severity levels.
Draft
Write the playbook per type with the people involved.
Alignment
With IT, legal, communications and management.
Test
Tabletop run and adjustment.
Handover
Versioned playbooks, maintenance process, training.