• +1 (602) 922-5990
  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • Mon - Fri 8:00a - 5:00p AZ
Leadership team in silhouette at a command table facing screens with network and world maps, titled Testing the Decisions That Matter.

Testing the Decisions That Matter: Connecting Technical Response with Executive Action

Most organizations test their technology. They run vulnerability scans, penetration tests, backup restores, and failover drills. Far fewer test the decisions that determine how a serious cyber incident unfolds: when to disconnect a business unit, whether to take a customer-facing service offline, who determines whether an incident is material, what to tell customers and regulators, and when it is safe to resume. Those decisions are made by executives, often with incomplete information and under intense time pressure. When they have never been rehearsed, even a strong technical response can be undermined by delay, confusion, or conflicting instructions.

This article explains how to design exercises that connect technical response with executive action, so that leaders practice the decisions that matter before they face them for real. It is written for CISOs, crisis and continuity leaders, and the executives who would sit at the table.

Why this matters

Cyber incidents escalate quickly from technical events into business crises. Within hours, an incident that began as an alert in a security operations center can involve legal counsel, communications, customer operations, finance, the executive team, and the board. The quality of the organization's response then depends on how well those groups share information, make decisions, and act on them together.

Public guidance recognizes this. NIST SP 800-61 Revision 3, the agency's incident response recommendations published in April 2025 as a Cybersecurity Framework (CSF) 2.0 Community Profile, emphasizes that many individuals, teams, and third parties hold roles in incident response, and that incident response should be integrated across organizational operations. CISA offers a library of Tabletop Exercise Packages (CTEPs), including cyber scenarios, to help organizations exercise their plans and decision-making. In financial services, DORA requires in-scope EU entities to maintain a digital operational resilience testing program and to test critical or important functions.

Disclosure obligations add another dimension. In the United States, the SEC's 2023 rules require public companies to disclose material cybersecurity incidents on Form 8-K, generally within four business days after determining that an incident is material, and to make that determination without unreasonable delay after discovery. Whatever an organization's specific obligations, the lesson is the same: some of the most consequential incident decisions are made by executives, on deadlines, and they can be practiced.

The business challenge

Exercises often fall short of testing executive decisions for several reasons.

  • Technical and executive exercises are run separately. The security team runs a technical simulation; the leadership team runs a tabletop months later. Neither tests the handoff between them, which is where many real problems occur.
  • Scenarios are generic. A scenario that could apply to any organization rarely forces the specific trade-offs a leadership team would face, such as taking down a revenue-generating service or delaying a product launch.
  • Exercises focus on the plan, not the decision. Participants walk through the incident response plan step by step and confirm that it exists, rather than being asked to make and justify decisions with imperfect information.
  • Information is too clean. Real incidents produce conflicting reports, partial data, and changing facts. Exercises that hand executives a tidy briefing do not test how they handle uncertainty.
  • Outcomes are not tracked. After-action reports list observations, but improvement actions lack owners and deadlines, and the same gaps appear in the next exercise.

Key concept: design exercises around decisions

An exercise that connects technical response with executive action starts by identifying the decisions it needs to test, then builds the scenario, information flow, and evaluation around them.

1. Identify the decisions that matter

For a cyber scenario, executive decisions typically include:

  • Activating the crisis management team and setting the response structure.
  • Isolating systems or disconnecting from partners, accepting operational impact to contain the threat.
  • Moving critical services to degraded or manual operations.
  • Determining whether the incident triggers legal, regulatory, contractual, or disclosure obligations, and who makes that determination.
  • Approving external communications to customers, employees, regulators, and the media.
  • Engaging law enforcement, insurers, and external specialists.
  • Approving the order and timing of service restoration.
  • Deciding when to stand down and declare recovery.

Choose a small number of these as the focus of each exercise. Trying to test everything at once usually means testing nothing well.

2. Build a scenario that forces trade-offs

A good scenario is severe but plausible, specific to the organization's critical services and dependencies, and designed so that the decisions in focus are genuinely difficult. It should present competing pressures, such as the security team recommending isolation while business leaders warn of customer harm, so that executives must weigh options rather than follow a script.

3. Connect the technical and executive tiers

The most realistic design runs two connected tiers. A technical tier, made up of security, infrastructure, and application teams, works through detection, investigation, and containment. An executive tier receives information as it would in a real incident: through the escalation path, in the formats the organization actually uses, with the delays and gaps that would naturally occur. Decisions made by executives flow back to the technical tier and change what happens next. This structure tests the handoffs, the quality of situational reporting, and the speed with which decisions reach the people who must carry them out.

Where a full two-tier exercise is not practical, a facilitated tabletop can simulate the technical tier through prepared injects, provided those injects reflect realistic technical detail and uncertainty.

4. Introduce uncertainty and time pressure

Injects should include incomplete or conflicting information, new facts that change earlier assumptions, and external pressures such as a media inquiry or a customer escalation. Time compression, where an hour of exercise represents a longer period of the incident, helps simulate the pressure of real deadlines.

5. Evaluate decisions, not just compliance with the plan

Observers should record when each focus decision was made, what information it was based on, who made it, whether the right people were involved, and how it was communicated. The goal is not to judge whether executives chose the "right" answer, since many incident decisions involve reasonable trade-offs, but to see whether the organization has the information, authority, and process to decide well and quickly.

6. Turn findings into tracked improvements

FEMA's Homeland Security Exercise and Evaluation Program (HSEEP) provides a widely used model: an after-action report paired with an improvement plan that assigns each corrective action to a responsible owner with a completion date. Applying the same discipline to cyber exercises ensures that findings lead to change, and that the next exercise can confirm whether it worked.

Choosing the right format

Exercise formats range from discussion-based to operations-based, and each tests different things. NIST SP 800-84, the agency's guide to test, training, and exercise programs for IT plans and capabilities, distinguishes tabletop exercises, which are discussion-based sessions where participants talk through their roles and responses, from functional exercises, which let personnel perform their duties in a simulated operational environment.

  • Executive tabletop: best for clarifying decision rights, escalation, and communication approvals. It requires relatively little preparation and minimal disruption.
  • Connected two-tier exercise: best for testing handoffs and information flow between technical teams and executives. It requires more coordination but produces the most realistic picture of how decisions reach the people executing them.
  • Functional or technical exercise: best for validating recovery procedures and timings, such as restoring a critical service in an isolated environment, with executive decisions simulated by a facilitator.

A mature program uses all three over time, choosing the format that best fits the decisions and capabilities in focus.

An illustration

Imagine a scenario in which suspicious activity is detected on systems supporting an online customer service, and investigation suggests an attacker has had access for some time. The technical tier works to scope the intrusion. Meanwhile, the executive tier receives a first situation report that is incomplete and partly wrong. Over the next exercise hour, the executive team must decide whether to take the service offline, how to communicate with customers who cannot log in, and whether the facts known so far warrant escalation to legal counsel for an assessment of notification obligations. Midway through, a journalist calls the press office. Observers note that the decision to take the service offline waited for a senior leader who was unreachable, and that the communications team did not know who could approve a holding statement. Both findings become improvement actions with owners and dates. Nothing in the plan was wrong on paper; the gaps were in decision rights and information flow.

What organizations should do

A practical approach to testing executive decisions follows these steps.

  1. Agree the exercise objectives with an executive sponsor. Identify the decisions to test and what the organization wants to learn.
  2. Base the scenario on critical services. Use business impact analysis and dependency mapping to choose systems and services that would make the scenario meaningful.
  3. Design the information flow. Decide how information will reach executives and in what form, mirroring real escalation paths and reporting templates.
  4. Prepare injects with realistic uncertainty. Include conflicting reports, evolving facts, and external pressures relevant to the focus decisions.
  5. Assign trained observers. Give them a structured way to capture decision timing, inputs, participants, and communication.
  6. Hold a structured debrief immediately. Capture participants' views while they are fresh, then follow up with a fuller analysis.
  7. Produce an after-action report and improvement plan. Assign every corrective action an owner and a date.
  8. Track progress and retest. Review improvement actions at the executive level and design the next exercise to confirm that key gaps were closed.
  9. Build a multi-year exercise program. Vary scenarios, decision focus, and participants over time, and include key third parties where possible.

Leadership considerations

Executives can do a great deal to make these exercises valuable.

  • Participate personally. Delegating attendance to deputies tests the deputies, not the people who would make the decisions.
  • Welcome discomfort. A well-designed exercise should expose gaps. An exercise in which everything goes smoothly probably was not challenging enough.
  • Clarify decision rights beforehand, then test them. If no one is sure who can approve taking a service offline, the exercise will reveal it, but it is better to resolve the question and then confirm the answer works.
  • Involve the board appropriately. Directors do not need to participate in every exercise, but they should understand how the organization would escalate to them and what decisions they might be asked to make.
  • Ask for improvement, not reports. The value of an exercise is measured by what changes afterward.

How OpResONE can help

OpResONE designs and facilitates exercises that connect technical response with executive decision-making. Our Cyber Resilience and Scenario Testing advisory work can include:

  • Identifying the executive decisions most important to test, based on critical services and dependencies.
  • Designing severe but plausible cyber scenarios with realistic injects and information flows.
  • Facilitating executive tabletops and connected technical and executive exercises.
  • Providing structured observation, debriefs, after-action reports, and improvement plans.
  • Helping build a multi-year exercise program that tracks improvement over time.

For leaders who want to deepen their crisis and incident capability, OpResONE is an authorized PECB training partner and offers training courses that prepare candidates for PECB credentials such as Lead Crisis Manager and ISO 27035 Lead Incident Manager. PECB awards the credentials.

Related resources

Schedule a strategy call

If your leadership team has never practiced the decisions a major cyber incident would demand, now is the time. Schedule a strategy call with OpResONE to discuss which decisions to test first and how to design an exercise that produces real improvement.

Schedule a Strategy Call

Sources