SIMEX26: the cloud outage drill that redraws board-level resilience duties
The Bank of England and UK Finance ran a sector-wide simulation of a global cloud services disruption involving the 38 largest and most systemically important banks and market infrastructure operators. The exercise sets a clear expectation that firms now act on the findings, raising the bar for how boards govern third-party concentration risk.
The Cross-Market Operational Resilience Group completed SIMEX26 on 8 October 2026, a biennial exercise built this year around a global cloud services disruption, with the 38 largest and most systemically important banks and market infrastructure operators in the room (Bank of England). The signal to senior leaders is unambiguous: the Bank now expects firms to take action off the back of the exercise to strengthen resilience against severe operational and cyber scenarios (Bank of England).
From tabletop to supervisory expectation
Previous SIMEX rounds in 2022 and 2024 rehearsed cyber-attacks against a major bank and critical infrastructure disruption outside the sector (Bank of England). Pivoting the 2026 scenario to cloud services is pointed. It aligns with the Financial Policy Committee's September record, which placed interconnected technology risks firmly on the stability agenda, and it tells boards that reliance on a small number of hyperscale providers is no longer a theoretical worry. Katharine Braddick, Deputy Governor of Prudential Regulation and PRA CEO, framed preparedness as "essential to safeguarding financial stability" (Bank of England). That language matters: financial stability framings tend to precede firmer rules, not softer ones.
Governance implications for boards
The participation list makes clear who owns the response. CMORG is chaired jointly by the Bank and UK Finance, with HM Treasury and the FCA at the table, and the exercise was opened by the Economic Secretary to the Treasury and hosted by the London Stock Exchange Group (Bank of England). Boards should expect their next supervisory conversations to probe three things: whether exit and substitution plans for cloud providers are credible under a severe scenario, whether critical third-party dependencies have been mapped to important business services, and whether the firm's crisis governance mirrors the Cross Market Business Continuity Group's model of strategic coordination. David Postings of UK Finance tied the exercise directly to "confidence, stability, and growth" (Bank of England), framing resilience as a competitive, not just defensive, attribute.
The accountability question
For Senior Managers, the exercise effectively creates an evidentiary baseline. If a cloud-driven disruption occurs in the next supervisory cycle, firms that participated and failed to act on the lessons will have a thin defence. Expect internal audit and the second line to be asked for structured post-SIMEX remediation plans, with dated commitments. Risk committees should press for a candid read-out of where the firm's playbooks held and where they broke, not a sanitised summary. The exercise also tested the authorities' own coordination, which means supervisory tolerance for firms that treat cloud resilience as a vendor management problem is likely to narrow.
The cloud question has moved from procurement to prudential. Boards that treat SIMEX26 as a compliance footnote will find themselves out of step with where the Bank, Treasury and FCA have now anchored the debate.
What this reveals
SIMEX26 exposes a governance gap most boards haven't closed: third-party cloud dependency has quietly migrated from a procurement and IT concern to a financial stability issue, and the assumption that existing operational resilience frameworks already cover it is unlikely to survive supervisory challenge. Many leadership teams will believe their important business service mapping and exit plans are credible because they were signed off, not because they have been tested against a severe, plausible scenario involving a hyperscaler. The deeper issue is that regulatory expectations have moved faster than internal confidence has been recalibrated, and the Bank has now made clear it expects evidence of action, not just awareness. This matters beyond the 38 firms in the room because supervisory bars set at the top of the sector reliably cascade.
Questions accountable leaders should ask
- 01If our primary cloud provider suffered a multi-day regional or global outage tomorrow, could we evidence to a supervisor that our substitution and exit plans are executable, not just documented?
- 02Have we mapped every important business service to its underlying third-party and sub-processor dependencies, including the concentrations hidden inside SaaS layers we don't directly contract with?
- 03Does our board actually understand where cloud concentration risk sits in the firm, or is it being briefed in a form that reassures rather than informs?
- 04When did we last test our crisis governance against a scenario we did not design ourselves, and would the people named in the playbook actually be the ones making decisions?
- 05What specific actions will we be able to show the regulator we took as a result of SIMEX26 findings, and who owns delivering them?
What accountable leaders should do now
- 1Commission an honest internal read, within 30 days, of where the firm's current third-party resilience posture would fall short against the SIMEX26 scenario, separating what is documented from what is demonstrably executable.
- 2Put cloud concentration risk on the next board agenda as a financial stability and SMCR accountability item, not a technology update, and name the Senior Manager who owns the response.
- 3Pressure-test exit and substitution plans for the two or three most critical cloud-dependent important business services using an external challenger, not the team that wrote them.
- 4Build a short, dated action log tied to SIMEX26 lessons that can be shown to supervisors in the next cycle, with clear owners, milestones and board oversight points.
- 5Review whether crisis governance arrangements genuinely reflect how decisions would be made in a cross-sector cloud event, including dependencies on counterparties, FMIs and the same providers your peers are also calling.
Explore the practical guide
This guide sets out how to build an operational resilience self-assessment that holds up to FCA and PRA impact tolerance scrutiny. After reading, senior leaders will know how to sequence evidence, frame judgements, and pre-empt the challenges supervisors are most likely to raise.
Read the guideWhere internal confidence may exceed external evidence
Polar Insight helps leadership teams test critical assumptions against stakeholder, market, regulatory, and operational reality before risk compounds.
Explore Stakeholder ProximityRelated insights
Agentic finance arrives: the FCA signals testing over consultation
Jessica Rusu's 19 October speech confirms the FCA will embed six of the seven Mills Review recommendations into live supervisory work rather than consult further, as 86% of surveyed firms now use AI. Senior leaders should expect direct engagement, assurance testing and surveillance on AI deployments, not another rulebook.
FCA's AI guidance: no new rules, but nowhere to hide
The FCA has published good and poor practice guidance for AI in financial services, clarifying how existing frameworks apply rather than creating new ones. For senior leaders, the message is that accountability for AI outcomes already sits with them under rules they know well.
Money markets stay calm as QT, leverage reform and ECP shift the plumbing
The Bank of England's Money Markets Committee reports stable funding and ample liquidity even as Quantitative Tightening, leverage ratio reform and growing European Commercial Paper issuance reshape the sterling funding mix. For treasurers, CFOs and ALCO chairs, the calm surface hides structural changes that demand repositioning now rather than at the next quarter-end.
Stakeholder Signals
Consequential developments in financial services and other regulated markets, with one implication for accountable leaders.
