Major or Not: Classifying an ICT Incident Against the Clock
Financial services tabletop exercise scenario · DORA Incident Classification
An ICT service your customers and counterparties depend on is degrading, and two clocks start at once: the operational one, and the regulatory one. Because if this incident is "major," notification is measured in hours — and the classification call has to be made before anyone knows the full impact. Operations wants to fix it. The regulator's clock doesn't wait for the fix.
This scenario runs financial entities through ICT-incident classification and reporting — the part of incident response that's as much a regulatory judgment as a technical one. The work: the dual-track of containment plus structured assessment against the major-incident criteria (clients affected, duration, spread, data loss, service criticality, economic impact), the classify-it decision under incomplete information and a running clock, the staged initial/intermediate/final notifications, and the reassessment as a borderline incident tips over the line. Designed to support DORA-aligned incident-reporting readiness.
1 hr 15 minIntermediate
Financial & InsuranceDORA
What this scenario tests
- Whether you can run operational recovery and classification assessment in parallel
- Whether your team classifies against the criteria under a running clock and partial data
- How you weigh over-reporting against a late or missed major-incident notification
- Whether your staged notifications and reassessment hold as impact clarifies
Who it's for
Operations Team · Legal & Compliance · Executive / C-Suite · IT & Security Team