Somebody Else's Incident: ICT Third-Party Failure at an EU Bank
Financial services tabletop exercise scenario · Bank Third-Party Outage
The payments platform is down — but it isn't yours. It belongs to a provider who has activated its own incident process, gone quiet behind its status page, and left your bank accountable for a service it cannot see inside. Your clients don't care whose incident it is. Neither does your regulator.
This scenario puts an EU financial entity in the situation DORA was written for: a critical ICT third-party dependency failing in real time, while classification decisions, reporting clocks, and client obligations land on you regardless of whose systems broke. Your team will confront the question at the heart of modern operational resilience — who decides, and on what information, when the failing component is somebody else's — and the scoping trap that catches teams who rank systems by business impact instead of by critical or important functions.
Designed to support organizations exercising against DORA's ICT risk-management, incident-reporting, and third-party risk expectations. Because the register of information is a document — but the third-party failure is a Tuesday.
1 hr 30 minIntermediate
Financial & InsuranceDORA
What this scenario tests
- Whether your team can classify a major ICT incident on incomplete, second-hand information
- Who in your organization decides — and on what — when the failing system belongs to a provider
- Whether your scoping reflects critical or important functions, or just revenue impact
- How your contingency arrangements hold up when switching carries its own risks
- What your provider contracts, exit strategy, and register of information look like under real pressure
Who it's for
Executive / C-Suite · IT & Security Team · Operations Team · Legal & Compliance