Rehearse the hard calls
Tabletop
Exercises
We run a realistic incident scenario with your leadership and response team around a table, injects and all, and watch where decisions stall. Who approves taking systems offline? Who calls the insurer? What do you tell customers? You leave with answers, and with a list of what to fix in the plan.
How an exercise runs
Find the gaps
in a conference room.
Exercises follow NIST SP 800-84 for design, conduct and evaluation. Scenarios are built from your environment and from real attacker behavior mapped to MITRE ATT&CK. A senior practitioner designs and runs the exercise, and decisions are recorded as they happen so the room can focus on the scenario.
Phase 01 · Objectives
Decide what the exercise needs to prove.
Agreed objectives and a participant list, approved by the exercise sponsor.
- Agree goals with the sponsor: plan validation, executive decisions, or a specific threat.
- Pick participants, from the response team to the executive committee.
- Review the current incident response plan and contact lists.
Phase 02 · Scenario design
Build a scenario that fits your business.
A scenario and inject set grounded in your systems, your vendors and real attacker behavior.
- Base the scenario on threats relevant to your sector, mapped to MITRE ATT&CK.
- Write injects that force decisions: ransom notes, press calls, regulator questions.
- Keep every detail plausible for your environment.
Phase 03 · Run the exercise
Run the exercise and let the pressure build.
A record of every decision made, who made it, and what information they had at the time.
- Lead the scenario in stages, releasing injects as it unfolds.
- Push on decisions that get deferred or assumed.
- Capture decisions, gaps and open questions as they surface.
Phase 04 · Hot wash
Talk it through while it is fresh.
Participant views on what worked and what did not, captured before people leave the room.
- Run a structured debrief straight after the exercise.
- Ask each function what slowed them down.
- Agree the top issues while everyone is present.
Phase 05 · After action report
Hand over the findings and the fix list.
An after action report with findings, owners and the plan changes they require.
- Write findings against the exercise objectives.
- Recommend plan, playbook and contact changes, each with an owner.
- Suggest the next scenario worth testing.
Decide what the exercise needs to prove.
Agreed objectives and a participant list, approved by the exercise sponsor.
- Agree goals with the sponsor: plan validation, executive decisions, or a specific threat.
- Pick participants, from the response team to the executive committee.
- Review the current incident response plan and contact lists.
Build a scenario that fits your business.
A scenario and inject set grounded in your systems, your vendors and real attacker behavior.
- Base the scenario on threats relevant to your sector, mapped to MITRE ATT&CK.
- Write injects that force decisions: ransom notes, press calls, regulator questions.
- Keep every detail plausible for your environment.
Run the exercise and let the pressure build.
A record of every decision made, who made it, and what information they had at the time.
- Lead the scenario in stages, releasing injects as it unfolds.
- Push on decisions that get deferred or assumed.
- Capture decisions, gaps and open questions as they surface.
Talk it through while it is fresh.
Participant views on what worked and what did not, captured before people leave the room.
- Run a structured debrief straight after the exercise.
- Ask each function what slowed them down.
- Agree the top issues while everyone is present.
Hand over the findings and the fix list.
An after action report with findings, owners and the plan changes they require.
- Write findings against the exercise objectives.
- Recommend plan, playbook and contact changes, each with an owner.
- Suggest the next scenario worth testing.
Key benefits
Make the hard decisions once, in practice.
Ransom, shutdown and disclosure decisions belong to executives, not IT. A tabletop puts those choices in front of them while the stakes are hypothetical and every question can be asked out loud.
No generic script. The scenario uses your systems, your vendors and the attacks your sector sees, so the gaps it finds are the gaps you actually have.
Auditors and insurers often ask whether your response plan has been tested. The after action report, built to NIST SP 800-84, is the document you hand them.
What you get
What lands on
your desk.
The exercise ends with a record of what happened and a plan for what changes.
The document
The after action report
Objectives, a scenario summary, the decisions made and when, the gaps that surfaced, and specific recommendations for the plan, the playbooks and the contact lists, each with an owner.
The working file
The improvement tracker
Each finding as a row with owner, priority and status, so changes to the plan actually get made and the next exercise can check that they were.
The conversation
The exercise and hot wash
The exercise itself, led by the senior practitioner who designed it, followed by a structured debrief with everyone in the room while the decisions and frustrations are still fresh.
Client case studies
Real engagements.
Documented outcomes.
In their words
"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
In their words
"ForgePath has become a trusted security partner for YHB. Beyond helping us comply with FTC Safeguards requirements, they provide the governance, oversight, and guidance we rely on to protect our firm and our clients’ data. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."
Trusted by industry leaders.
Before the exercise
What teams
want to know.
Straight answers from the practitioners who do the work. If yours is not here, ask us directly.
That depends on the objective. Executive exercises need the CEO or a delegate, legal, communications and finance. Technical exercises need IT, security and your major vendors. We help you choose, and keep the group small enough that everyone takes part.
No. A tabletop is a discussion, and nothing runs against your network. If you want to test technical detection and response under live conditions, a red team assessment is the better fit.
Yes, though in person tends to work better for executive exercises because people speak more freely in the room. Hybrid works if some participants cannot travel. We agree the format during scoping.
An exercise without a plan still shows you who decides what, which is useful on its own. The findings are easier to act on once a plan exists, though. If you have none, we can build it first through our Incident Response Plan Development & Review service.
As realistic as your objectives call for. We base it on your environment and on documented attacker behavior mapped to MITRE ATT&CK, and we write injects that look like the real thing: ransom notes, reporter emails, a regulator's question.
Ready?
Bring us
the problem.
One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.








