Cyber Crisis Management: From Planning to Proven Readiness

Cyber crisis management starts where incident response ends: the crisis threshold, the calls a plan can't make, and how to rehearse them.

Illustration of a cyber incident crossing the threshold into a business crisis that leaders must manage

Key Takeaways

  • A cyber crisis begins when business impact requires leadership decisions before the technical facts are complete.

  • During the 2019 Norsk Hydro attack, executives rejected the ransom, engaged external responders, and committed to public transparency.

  • ISO 22361:2022 addresses crisis leadership, decision-making, and communication and is intended for top management.

  • A cyber crisis management rehearsal should record who decided, when the decision occurred, and what information was available.

Cyber crisis management is how leaders make business decisions when a cyber incident threatens operations, reputation, legal standing, or safety. It covers what the organization discloses and when, which operations continue, who receives updates, and how the business recovers. Incident responders manage the technical response; crisis leaders manage the incident’s business consequences.

What Is Crisis Management?

Crisis management is an organization's capability to anticipate, respond to, and recover from events that threaten its people, operations, reputation, or survival. The trigger might be a fire, a product recall, a fraud, or a flood. Scale and uncertainty make it a crisis: the event outruns normal management, and the people deciding lack the full picture.

The international reference is ISO 22361:2022, published in October 2022. It guides organizations to plan, establish, maintain, review, and continually improve a strategic crisis management capability, and it is written for top management with strategic responsibility for that capability. Crisis management in cyber security applies that discipline to a trigger with different operational conditions.

What Is Cyber Crisis Management?

Cyber crisis management is the leadership discipline of making business decisions when a cyber incident threatens operations, safety, legal standing, or reputation. It applies crisis management to an event whose facts are incomplete, technical, and changing by the hour, often while an adversary remains active in the organization’s environment.

Reflex Security publishes this article and sells crisis simulations used to rehearse these decisions, so it has a commercial interest in the testing approach discussed later.

Three characteristics distinguish cyber crisis management:

  1. Leaders must make decisions before the investigation establishes the full sequence of events.

  2. Technical specialists must translate evidence into consequences that business decision-makers can evaluate.

  3. The adversary may remain active while the organization coordinates its response.

Tools alone do not resolve those challenges. Leaders prepare by rehearsing the decisions under realistic time pressure before a real incident requires them.

Crisis Management vs. Cyber Crisis Management: Key Differences

Cyber security crisis management borrows the structure of general crisis management and changes almost every input. The table compares the two on the dimensions that affect leadership decisions.

Dimension

Crisis management

Cyber crisis management

Trigger

A physical, financial, operational, or reputational event, such as a fire, recall, fraud, or severe weather

A cyber incident that crosses a defined business-impact threshold

Information certainty

The event may be visible before its full cause and consequences are understood

Scope, entry point, and data exposure often remain uncertain when the first decisions fall due

Speed of spread

Effects are commonly constrained by geography, physical systems, or supply-chain dependencies

Effects can propagate rapidly across connected systems, business units, and locations

Adversary present

An adversary may be absent, external, or no longer influencing the event

An adversary may remain active and respond to containment or communication decisions

Regulatory clocks

Deadlines depend on the event, sector, jurisdiction, and applicable reporting rules

Notification deadlines may begin at awareness or determination, before the full scope is known

Technical dependency in decisions

Leaders depend on operational, legal, safety, or subject-matter specialists for relevant evidence

Leaders depend on security, IT, and operational technology specialists to translate technical evidence into business consequences

Who leads

A designated executive crisis leader supported by the relevant business functions

The designated executive crisis leader, with the CISO or security leader serving as principal technical adviser

The bottom two rows show why technical expertise and crisis authority must remain distinct. Technical specialists should translate the evidence into business consequences, but the decisions remain with the executives accountable for those consequences.

When a Cyber Incident Becomes a Business Crisis

Cyber incident crisis management begins at the threshold where the question changes from "what happened?" to "what does the business do now?" Organizations should define that threshold in advance through observable conditions that anyone on the bridge can verify:

  • Core operations halted or degraded. Production, logistics, or customer-facing services stop or fall back to manual.

  • Safety implications. Control systems in an OT environment behave unpredictably, or people working near equipment are at risk.

  • Material data exposure. Regulated, customer, or commercially sensitive data has left your control, or plausibly has.

  • Public visibility. Customers, journalists, or social media are already talking about it.

  • Regulator or law-enforcement involvement. A notification duty starts, or police are engaged.

  • Extortion. Someone is demanding payment, and the demand carries a deadline.

Any one of them is enough. Norsk Hydro, one of the world's largest aluminum producers, crossed several in a single night. An operator found a LockerGoga ransom note at 10:45 p.m. on March 18, 2019, and at about 3 a.m. the company decided to shut down more than 23,000 PCs and 3,000 servers, according to Idaho National Laboratory's CyOTE case study. Production lines stopped at some plants while others switched to manual operations.

The attack reached all 35,000 employees across 40 countries, and the company reported it to Norway's National Criminal Investigation Service. Halvor Molland, senior vice president of media relations, named the safety stake to Microsoft: "We operate heavy machinery. If the power is lost in an uncontrolled manner, it could risk severe safety incidents for people." Torstein Gimnes Are, the corporate information security officer, later recalled the first morning: "This was a company crisis. IT had already shut down the network and servers to avoid any further spreading. But we didn't fully know what this was."

Nobody waited for certainty.

Why Cyber Crisis Management Requires More Than an Incident Response Plan

An incident response plan defines how responders contain the incident, preserve evidence, eradicate the threat, and restore services safely. CISO Cyber Incident Response Plan: Prepare, Test & Respond covers what belongs in that document, while Incident Response Management: From Detection to Crisis Recovery covers how the response operates.

Incident response focuses on restoring systems. Cyber attack crisis management governs what the business does while those systems remain unavailable. That includes whether plants operate manually, whether the organization pays an extortion demand, when it discloses the incident, and what customers, employees, and regulators hear.

Norsk Hydro's executives faced those questions at an emergency meeting on the morning of March 19. According to Microsoft's account of the attack, they made three swift decisions: pay no ransom, call in Microsoft's Detection and Response Team to help restore operations, and be fully open about the breach. Engaging the external response team was the incident response decision. Rejecting the ransom and committing to transparency were business-crisis decisions that set the company’s course with customers, investors, and the public.

Leadership then carried those decisions through. Senior staff hosted daily webcasts, executives held daily press conferences in Oslo, and the company welcomed journalists into its operations control rooms. Organizations should establish their ransomware-payment policy before an incident rather than debating it for the first time under pressure.

The Human Side of Cyber Crisis Management: Decisions, Escalation & Coordination

Most cyber crisis management programs fail in the space between what is documented and what has been practiced. Take a hypothetical copper miner. Ransomware reaches the fleet-dispatch and ore-processing control systems at a remote site overnight. The haul trucks are still moving, and the processing plant runs on whatever its operators can see.

Decisions blur under pressure. The plan says the site general manager can halt operations. It does not identify who decides whether haul trucks continue under manual radio dispatch when nobody can confirm each truck’s location. At 3 a.m. the general manager, the head of OT, and the safety lead each assume one of the others owns that call.

Escalation waits for certainty. The OT team wants to confirm whether the plant's controllers are affected before it wakes the executive team. That instinct feels professional. Meanwhile, the mine safety regulator, community liaison, and commodity buyers receive no update. Each hour of silence reduces the organization’s options with all three.

Coordination splits along language. The technical lead reports lateral movement "contained to the OT segment." The executives hear "contained." Communications drafts a community statement on that basis while the site tells the regulator something different. In the Hacker Halted simulation, two teams worked the same incident, found the same attack, and still left different coordination gaps behind.

By the second day, the people who made the first decisions have been awake for 30 hours, and the plan does not identify their replacements. ISO 22361 devotes Clause 7 to the decision-making challenges facing an active crisis team. The C-Suite Cybersecurity Tabletop Exercise Playbook covers the additional decisions involving executives and the board.

How to Test Your Cyber Crisis Management Strategy Before a Real Attack

Testing the strategy means rehearsing the calls your executives will make. Validating contact trees, decision authorities, and templates is plan work, covered in Cyber Crisis Management Plan: How to Prepare for a Cyber Crisis. Here, rehearse three calls above all: declaring the crisis, the payment decision, and the first public statement. ISO 22361 covers training, validation, and learning from crises in Clause 9. Five steps put that into practice for your leadership team:

  1. Pick a crisis-grade scenario. Choose one that crosses at least two of the thresholds above, such as an OT outage that arrives with an extortion demand. A phishing click that stays inside IT tests the SOC but does not test executive decision-making.

  2. Seat the real decision-makers. Put the people who will decide in a real attack in the chairs. If the COO sends a delegate, you have tested the delegate.

  3. Impose time pressure. Run the clock forward and let deadlines expire in the room: the extortion timer, the regulator's follow-up, the shift change at the plant.

  4. Inject external stakeholders. Add a journalist who calls back, a regulator who wants a number, and a cyber insurer asking what you have already promised. Reflex uses AI agents to play these roles, and a facilitator with a phone and a script can play them too.

  5. Review decisions, not attendance. For each of the three calls, record when it was made, who made it, and what they knew at the time. Set pass criteria before you start, because exercises with no failure condition teach you nothing about the real day.

From Tabletop Exercises to Realistic Crisis Simulation

A discussion-based tabletop does one job well. It gets leaders reading the same plan, agreeing on roles, and finding obvious gaps with relatively little setup. For an executive team that has never met as a crisis team, start there.

Its adaptability depends on the facilitator. Without active intervention, the scenario may continue unchanged after a poor decision, and external stakeholders may not respond to delays or silence. That limitation helps explain why most tabletop exercises fail to prepare teams for a real incident. A live simulation can attach consequences to each decision. That responsiveness is central to executive crisis rehearsal. Cyber Crisis Simulation: The CISO’s Guide to the Next Generation of Cyber Exercises explains the AI-driven mechanics.

How Reflex Security Tests Cyber Crisis Readiness Under Pressure

Readiness becomes demonstrable when the organization holds a recent record of how its leaders performed under pressure. That evidence is stronger than a recollection that the meeting went well.

Reflex builds a live crisis using information about the organization’s environment. AI agents can represent the adversary, reporters, regulators, executives, and other stakeholders, responding as the team makes decisions or delays them. A Reflex exercise commonly runs for about an hour, with duration configurable, making another run practical when the people in key roles change.

When the exercise ends, Reflex generates an After Action Report (AAR). Each finding traces to the moment in the simulation that produced it. That gives the cyber crisis management program evidence that can support the next board discussion. Repeated exercises allow the organization to compare findings over time. Den Jones, CEO, 909Cyber, said after a Reflex simulation: "It's not about running one big flashy tabletop a year to check a box. This lets teams run it lean, transparent, and pragmatic, the way I try to sell everything."

Reflex versus traditional tabletops sets out the difference in setup, adaptation, and evidence. Start with one crisis-grade scenario and the people who will decide on the real day. Measure the first call.

See what your team does under real pressure.

Put your readiness to the test. Sixty minutes, your real environment, no slides.

Book A demo

Frequently Asked Questions

Who should lead cyber crisis management: the CISO or the CEO?

The CEO, or an executive the CEO names in advance, should chair the crisis team, because the decisions are about the business. The CISO is the principal adviser and the bridge to the technical response. Trouble starts when the CISO ends up chairing by default because nobody else can follow the briefing. Fix the briefing first, then rehearse the handover.

How is cyber incident crisis management different from business continuity?

Business continuity keeps critical activities running through a disruption, using plans and recovery targets you set in advance, and ISO 22301 covers it separately. Cyber incident crisis management makes the calls those plans cannot anticipate: whether to pay, what to disclose, and when to restart systems you cannot yet trust. Both disciplines are necessary. The crisis team uses the continuity plan as one input to those decisions.

What is the first decision in cyber attack crisis management?

Declaring that a crisis exists. Every later call, from bringing in outside responders to the first public statement, waits on someone with authority saying the incident has crossed the threshold. Norsk Hydro's information security officer took a 4 a.m. call and immediately phoned the emergency preparedness chief to convene a meeting that morning. Agree in advance who can make that declaration on incomplete facts.

Do small organizations need a cyber security crisis management capability?

Yes, scaled to size. A small organization does not need a crisis team charter or a war room. It needs a named decision-maker, an agreed threshold, a short list of who must hear from you, and a holding statement. A facilitated discussion around a table costs nothing and will expose most early gaps. Spend money on rehearsal once those basics exist.

How often should leadership rehearse a cyber crisis?

An annual full-team exercise provides a practical baseline, with additional exercises when key roles or operating conditions change. A new CEO, general counsel, or communications lead has not yet rehearsed with the existing team. Short exercises focused on one decision, such as the first public statement, can supplement the full session. No universal cadence applies to every organization.

What standard covers crisis management in cyber security?

ISO 22361:2022 is the international guidance for crisis management, and it applies to a cyber trigger as it does to any other. For the response itself, ISO/IEC 27035-1:2023 sets out the principles and process of information security incident management. Read them as a pair: 27035 for the incident, 22361 for the leadership decisions above it.

References

Briggs, B. (2019, December 16). Hackers hit Norsk Hydro with ransomware. The company responded with transparency. Microsoft Source. https://news.microsoft.com/source/features/digital-transformation/hackers-hit-norsk-hydro-ransomware-company-responded-transparency/

Idaho National Laboratory. (2022, September 30). Precursor analysis report: LockerGoga ransomware attack on Norsk Hydro 2019 (INL/RPT-22-69758). Cybersecurity for the Operational Technology Environment (CyOTE). https://cyote.inl.gov/content/uploads/24/2025/12/CyOTE-Case-Study_Norsk-Hydro.pdf

International Organization for Standardization. (2022, October). Security and resilience — Crisis management — Guidelines (ISO Standard No. 22361:2022). ISO. https://www.iso.org/standard/50267.html

International Organization for Standardization & International Electrotechnical Commission. (2023, February). Information technology — Information security incident management — Part 1: Principles and process (ISO/IEC Standard No. 27035-1:2023). ISO. https://www.iso.org/standard/78973.html

Cite this article

Marlow Bryant.

Cyber Crisis Management: From Planning to Proven Readiness.

Reflex Security.

https://reflexsecurity.com/guides/cyber-crisis-management

Incident closed // after-action ready

Incident closed

See what your team does

under real pressure.

True cyber crisis readiness isn't built in a slide deck—it's forged in the trenches. Every team believes it’s ready. The simulation is where you find out. Sixty minutes, your real environment, no slides.

Book A demo

ReflexSecurity

AI-powered incident-response simulation platform.

AI-powered incident-response simulation platform.

© 2026 Reflex Security. All rights reserved.