Back to scenarios
Lightning storm over a city, illustrating the Connectivity Down: Severe Weather Microsimulation
Third-Party & TechnologyAlso in ItalianTeam

Connectivity Down: Severe Weather

At a glance

Connectivity Down: Severe Weather is a simulation from iluminr in the Third-Party & Technology category for Third-Party Risk, Operations and Risk. It tests how your team protects payments & customer account access, with indicative mapping to Interagency Third-Party Guidance, OCC / Fed / FDIC Sound Practices and FFIEC BCM Handbook.

Respond to severe weather-induced operational disruptions, including widespread internet outages, by verifying role responsibilities and ensuring continuity in communications and operations.

What it tests

  • Enhance awareness of the roles and responsibilities in responding to an event.
  • Confirm knowledge of first actions to take in an event.
  • Verify role alternates.

How you can run it

MicrosimulationRun as a team in a shared event room.
Full-Scale SimulationExtend it across teams, functions and partners.
Expert-FacilitatedOur team designs and runs it with you.

Questions about Connectivity Down: Severe Weather

What does Connectivity Down: Severe Weather test?

Connectivity Down: Severe Weather tests whether your team can enhance awareness of the roles and responsibilities in responding to an event, confirm knowledge of first actions to take in an event and verify role alternates.

Who should take Connectivity Down: Severe Weather?

Connectivity Down: Severe Weather is designed for Third-Party Risk, Operations, Risk, Business Continuity, Technology & Security and Executive & Board.

Which regulations and standards does Connectivity Down: Severe Weather support?

Connectivity Down: Severe Weather supports testing expectations in Interagency Third-Party Guidance, OCC / Fed / FDIC Sound Practices, FFIEC BCM Handbook, EU DORA, UK PS21/3 Operational Resilience, APRA CPS 230, OSFI E-21, ISO 22301, Basel Principles for Operational Resilience, EBA Outsourcing Guidelines, EBA ICT & Security Risk Guidelines, OSFI B-13, SEC Regulation SCI, MAS BCM Guidelines, AU SOCI Act, ISO 22316, CPMI-IOSCO PFMI, ISO 22398 and NIST SP 800-84. Mapping is indicative, so confirm scope against your own obligations.

Can Connectivity Down: Severe Weather be run individually or as a team?

It runs as a team exercise in a shared event room. It can also be extended into a full-scale simulation across teams and partners.

Can we customize Connectivity Down: Severe Weather?

Yes. You can tailor the roles, plans, critical services, injects and objectives in the iluminr builder, or have our team customize it for you.

How do we get access to Connectivity Down: Severe Weather?

Request it from this page. If you are an iluminr customer, we will set up access in your account. If not, we will contact you and either provide access or facilitate it for you.

Related scenarios

Data center servers in the dark, illustrating the Core Platform Outage: Rollback MicrosimulationThird-Party & TechnologyCore Platform Outage: RollbackA critical platform update turns into a live-fire incident as a scheduled patch unexpectedly brings down key systems. Participants must navigate real-time service degradation, mounting customer pressure, and rollback decisions under duress. This Microsimulation tests cross-functional coordination, incident escalation, and communication flow - providing vital validation of operational resilience, rollback protocols, and regulatory compliance readiness.A broken chain, illustrating the Exit Plan: Vendor Insolvency MicrosimulationThird-Party & TechnologyExit Plan: Vendor InsolvencyA critical third-party vendor has filed for insolvency, causing both operational and data losses. Can your team execute the exit plan under pressure?Ripples spreading across dark water, illustrating the Ripple Effect: Fourth-Party Fallout MicrosimulationThird-Party & TechnologyRipple Effect: Fourth-Party FalloutA critical system failure has occurred in your supply chain, creating significant operational impacts. Your third-party vendor experienced a service outage caused by a vulnerability introduced through an undetected AI-driven update in their supplier's systems. This failure has cascaded through your supplier's network, resulting in widespread service disruptions that are now affecting your business operations and customers.