← Back to blog

Copyable incident response tabletop agenda with sample injects (UK)

October 2, 2026
Copyable incident response tabletop agenda with sample injects (UK)

An incident response tabletop exercise is a discussion-based simulation where key staff talk through a simulated cyber incident to test decisions, roles and plans, without touching live systems. Run well, it validates whether your team can actually make the calls a real breach demands and ends with an actionable post-exercise report. Resources like NCSC Exercise in a Box and providers such as Solusec can help you build and facilitate it.

Solusec
solusec.co.uk
Test Your Incident Response Plans
Solusec provides expert-led penetration testing and practical cybersecurity advice to help organisations identify vulnerabilities and strengthen their security posture.
Get a Pentest Quote

Key Takeaways

A well-run tabletop exercise effectively tests an organization’s decision-making, roles, and plans during a simulated cyber incident without impacting live systems.

PointDetails
Decision-making under pressureTabletop exercises evaluate how teams respond to time-sensitive decisions during cyber incidents.
Clear role definitionThey clarify who is authorized to make critical decisions, such as shutting down systems or paying ransoms.
Inter-team coordinationThese exercises reveal how well legal, communications, and IT teams work together before real incidents occur.
Cost-effective testingConducting discussions instead of live systems saves money while identifying response gaps.
Solusec's supportSolusec offers expert facilitation and actionable reports to improve incident response plans.

Table of Contents

What a tabletop exercise is and why organisations run them

A tabletop exercise differs from a live-play simulation or a technical penetration test in one key way: nobody touches a keyboard. Participants talk through a scenario, referencing plans and making decisions out loud, while a facilitator steers the discussion and observers capture what happens. Live-play exercises inject real technical artefacts; penetration tests probe systems directly. Tabletops test people and process.

That focus is exactly why organisations run them. The benefits show up quickly:

  • Decision-making gets tested under time pressure, not assumed to work.
  • Roles and authority become clear, including who actually signs off a ransomware payment or a system shutdown.
  • Interdependencies between teams, such as legal, communications and IT, surface before a real incident exposes them.
  • Governance and compliance obligations get a practical check against the written plan.

NCSC guidance on effective steps to cyber exercise creation frames exercising as one of the more cost-effective ways to find these gaps, since a discussion costs far less than a live incident.

Who should attend and how roles map to the exercise

Attendance should mirror your real incident response chain, not just fill a room with security staff. That means a mix of strategic decision-makers, tactical coordinators and operational specialists, each playing the role they would hold in a genuine incident.

  • Strategic (gold): executives who approve major decisions such as ransom payments, public statements or regulatory disclosure.
  • Tactical (silver): incident managers coordinating the response and translating strategy into action.
  • Operational (bronze): technical and communications staff handling the detail on the ground.
  • Observers and scribes: people who capture decisions, timings and gaps without joining the discussion.

NCSC's guidance on effective steps to cyber exercise creation recommends confirming the availability of these gold, silver and bronze roles before you fix a date. External stakeholders, such as insurers, regulators or key suppliers, are worth including only when the scenario genuinely touches their remit.

Pro Tip: Keep the observer separate from the facilitator. One person cannot referee the room and take an accurate record at the same time.

Planning and preparation before the exercise

Good preparation starts with objectives, not scenarios. Decide what you are testing (communication speed, decision authority, plan usability) and how you will know if it worked.

  1. Set two or three measurable objectives, such as "confirm who can authorise system isolation within 30 minutes."
  2. Choose a scope: a single team, a cross-functional group, or a full organisational drill.
  3. Select a scenario that matches a real risk to your organisation, rather than a generic template.
  4. Send a participant brief a few days ahead explaining the format, ground rules and expected time commitment.
  5. Prepare a participant directory, reference copies of the cyber incident response plan (CIRP), and any supporting materials.
  6. Confirm logistics: room or video link, timings, and who is facilitating versus observing.

NCSC's exercise creation guidance sets out this sequence, from objective-setting through to distributing preparatory guidance, as the core planning path most organisations should follow.

Scenario examples and sample injects to adapt

Scenarios work best when they stay discussion-focused: describe what is happening and ask "what do you do now", rather than asking participants to diagnose technical detail.

  • Ransomware after phishing: an employee opens an attachment, files begin encrypting overnight. Inject: a ransom note appears demanding payment within 48 hours.
  • Supply chain compromise: a key software vendor reports a breach that may have exposed your data. Inject: the vendor cannot confirm which customers were affected.
  • Insider misuse: a departing employee is suspected of exporting customer data before their last day. Inject: legal asks whether you can suspend access without evidence.
  • BYOD or remote-working compromise: a personal device with company access is reported stolen. Inject: the device had cached credentials to a shared drive.
  • Third-party phishing escalation: a customer reports receiving fraudulent invoices that appear to come from you. Inject: a journalist calls asking for comment.

NCSC's Exercise in a Box tabletop catalogue covers several of these scenario types, including ransomware, third-party compromise and supply chain incidents, with ready-made injects you can adapt. Escalation points, such as a deadline or a media enquiry, force participants to decide rather than just describe.

Running the session: facilitation and agenda template

A facilitator's job is to keep the discussion moving without dictating the answers. Too much prompting turns the exercise into a lecture; too little leaves participants stuck. NCSC guidance on using cyber security scenarios describes this as a balance every facilitator has to manage deliberately, stepping in only when the discussion stalls.

A half-day agenda works for most single-scenario exercises:

  1. Introduction and ground rules (15 minutes).
  2. Scenario briefing and initial reactions (20 minutes).
  3. First inject and discussion (45 minutes).
  4. Second inject, escalation and decision points (45 minutes).
  5. Final inject and resolution discussion (30 minutes).
  6. Hot debrief and initial observations (30 minutes).

Observers should log decisions, timings and any moment where participants disagreed on authority or process, since these are usually the richest findings. Unexpected reactions, such as a participant refusing to make a call without more information, are worth recording rather than smoothing over: that hesitation is often the real-world gap the exercise exists to find.

Pro Tip: Timebox each inject strictly. Running over on one scenario stage is the most common way half-day exercises overrun.

Running the session: facilitation and agenda template — overview diagram

Turning the debrief into an improvement plan

The exercise itself is only half the value; the report is what makes it worth running. NCSC guidance is direct that a strong post-exercise report matters more than the session, and should record observations, lessons identified, recommendations and named owners for each action.

A useful report structure includes:

  • A summary of what was tested and against which objectives.
  • Key observations, including where decision authority was unclear or delayed.
  • Lessons identified, distinct from raw observations, framed as changes needed.
  • Recommendations with assigned owners and realistic deadlines.
  • A note on how findings will update the cyber incident response plan.

Actions should feed into existing governance, with deadlines tracked the same way as any other risk item, so they do not quietly stall. Capturing timings and decision points during the exercise gives you concrete evidence to prioritise which gaps get fixed first, rather than relying on impressions after the fact.

Official NCSC resources and the CIE scheme

Two NCSC resources cover most organisations' needs, whether you are running an exercise yourselves or commissioning one.

  • Exercise in a Box is a free NCSC resource offering 20 exercises across 12 topics, including ready-made tabletop scenarios and materials for organisations to run themselves.
  • The Cyber Incident Exercising (CIE) scheme assures that commissioned providers meet NCSC's technical standard for delivering exercises, covering Category 3 to 5 incidents on the UK's cyber attack categorisation system.
  • Together they map to the exercise lifecycle: Exercise in a Box supports the plan and run stages for self-service exercises, while CIE assurance supports organisations choosing a provider for the run, report and improve stages when they want independent facilitation.

These resources sit well alongside supplier obligations covered in the Cyber Resilience Pledge for organisations building supply chain scenarios.

Solusec's support for tabletop and incident response planning

Running a tabletop well takes a facilitator who can hold the room, ask the right follow-up questions and write a report that leadership actually acts on. The provider is CREST-accredited and works directly with the people running the exercise, not through a sales layer, which keeps scoping conversations practical rather than generic.

Solusec

A typical engagement starts with a short scoping call to agree objectives and scenario, moves through a facilitated session with an experienced practitioner running the injects, and ends with a written post-exercise report setting out prioritised actions and owners. Organisations that find control gaps during the exercise can also follow up with Cyber Essentials certification or a fuller penetration test to close them.

If you want expert facilitation and a report you can act on, visit Solusec's incident response page to discuss scope and availability.

FAQ

What are the 7 steps of incident response?

Definitions vary by framework, but most incident response models cover preparation, identification, containment, eradication, recovery, and lessons learned, with some splitting these into further stages. A tabletop exercise is one of the most practical ways to test whether your team can actually execute these steps under pressure.

Can you give me some examples of tabletop exercises?

Common scenarios include ransomware triggered by a phishing email, a supply chain compromise through a third-party vendor, an insider data theft case, and a compromised remote-working or BYOD device. NCSC's Exercise in a Box tabletop catalogue provides ready-made versions of several of these you can adapt.

What is a BCM tabletop exercise?

A business continuity management (BCM) tabletop exercise tests an organisation's continuity plans, focusing on how the business keeps operating during disruption rather than purely on the cyber incident response. It often overlaps with an incident response tabletop when the disruption is caused by a cyber event, since both test decision-making and plan usability under pressure.

What are the 5 steps to incident response?

Some shorter frameworks compress incident response into preparation, detection and analysis, containment and eradication, recovery, and post-incident review. Whichever version your organisation follows, a tabletop exercise is designed to validate that each step works in practice, not just on paper, and to feed findings back into the cyber incident response plan.

This article was created with assistance of AI. We never use AI with your data unless given explicit permission.