Cybersecurity Tabletop

Play Today.
Respond Tomorrow.

Challenge is TALAS's flagship cybersecurity tabletop exercise. Custom-built for your organization, grounded in real threat intelligence, and designed to train the active decision-making that matters when an incident is actually unfolding.

Schedule Your Event
The Problem

The Industry
Got It Wrong.

The tabletop exercise market has drifted to two extremes. Neither reflects what actually happens during a cybersecurity incident.

Failure Mode 01
The Checkbox
Exercise

Every control works perfectly. Every process executes flawlessly. The team is commended. No issues are identified. You leave with a compliance artifact, and no real understanding of where you'd actually fail.

Builds false confidence
Failure Mode 02
The Chaos
Stress Test

Everything that can go wrong does go wrong. The exercise is designed to break the team regardless of actual readiness. Intense, but equally unrealistic, and it fails to build the decision-making capability that matters most.

Trains panic, not judgment
Reality lives
in the middle.

In a real incident, most controls work - sometimes. Teams adapt as new information emerges. The skill that matters isn't knowing the playbook. It's making sound decisions when the playbook doesn't fully apply. Challenge was built for exactly that.

Inject Types

What's
Included

Challenge uses four distinct inject types to create variety, realism, and genuine decision pressure. Every event is built from a combination of all four.

Inject Type 01
Role-Play
Injects

Participants step into a live scenario and respond in character: Fielding an inbound call, handling a media inquiry, briefing an executive under pressure. These injects test the human side of incident response: communication, composure, and judgment under the stress of a real incident.

Example Scenario

"A reporter from a regional news outlet has called the main office line. They've heard a rumor about a data breach and are asking for comment before their story goes to print. How do you respond?"

Tests Crisis CommunicationHow the team communicates under pressure, both internally and externally, especially when the facts are incomplete and the stakes are high.
Engages the Crisis WorkstreamRole-plays often pull in the leadership team: Legal, communications, executives, all replicating the parallel workstreams of a real incident.
No Right AnswerThe facilitator is playing the other character. Responses have consequences. Participants discover what they would actually say, not what they planned to.
Inject Type 02
Decision
Injects

Binary or multi-option choices that advance the scenario along different paths based on the team's selection. These are the branching points - decisions that change the game. The choice the team makes determines which version of the incident they're now managing.

Example Scenario

"You've identified suspicious activity on two systems. Do you isolate the affected machines immediately, potentially alerting the attacker - or do you continue monitoring to gather more intelligence before acting?"

Branching ConsequencesEach choice routes participants to a different path through the scenario: Different information, different challenges, different outcomes downstream.
Pre-Engineered BranchesThe decision tree is fully designed before the event. The facilitator doesn't improvise, they guide the team through a carefully constructed reality with multiple possible oucomes.
Trains Active Decision-MakingThe goal isn't to recall a procedure. It's to make a defensible call under uncertainty. Active decision making is the skill that determines how an organization actually performs during a real incident.
Inject Type 03
Statistical
Injects

Decisions where the outcome is probabilistic, determined by rolling a ten-sided die calibrated to the client's own discovery data. The die represents reality: most controls work, but not all. The roll removes the illusion of certainty.

Example Scenario

"Your culture survey shows 70% of employees know how to properly report phishing. You roll the die: 1–7, the email is reported and you have the intelligence. 8–10, no one flagged it and the attacker's campaign proceeds undetected."

Calibrated to Your DataThe die probabilities aren't generic. They're derived from the organization's actual discovery data: Culture and awareness surveys, control inventories, network design.
Outcomes Feel EarnedBecause the probabilities reflect real organizational conditions, the results are not arbitrary. A bad roll reflects a real gap, not unfair design.
Teaches Probabilistic ThinkingParticipants learn to plan for variance, not just best-case execution. This is the learned skill that separates practiced responders from those reading a playbook for the first time.
Inject Type 04
Active
Triage Injects

Participants are presented with partial information and must ask the right questions to reveal additional intelligence. The rule is simple: if you don't ask, you don't get the information. This is the inject type that most directly mirrors real incident response.

Example Scenario

"The SOC has flagged anomalous outbound traffic. You're told there is a traffic volume spike — nothing else. What do you ask? What do you need to know before you decide what to do?"

Information is GatedThe facilitator holds additional pre-planned intelligence. It's only revealed if participants ask for it explicitly. Gaps in questioning become visible in real time.
Exposes Playbook GapsTeams quickly discover whether their documented procedures prompt the right questions, or leave them making decisions with incomplete pictures.
The Most Realistic Inject TypeReal incidents don't hand you a complete dataset. Responders work from fragments. Active triage injects replicate that condition directly.
Engagement Lifecycle

How Challenge
Works

Every Challenge engagement is built from scratch — eight phases from first design session to final report, each calibrated to your organization's actual threat landscape.

01
Design Session

A co-led kickoff to establish logistics, workstream balance, and scenario guidance. Clients direct where to stress-test: Specific systems, coverage gaps, personnel. Once direction is set, TALAS takes over the build entirely.

02
Threat Model Construction

TALAS builds a proprietary threat model by selecting across five threat variables, producing a precise attacker profile that drives every downstream design decision.

The 5-Variable Framework
Choose Your Adversary

Every scenario begins with a deliberate choice across five axes. The combination produces a threat profile that is specific, plausible, and grounded in your actual risk environment.

Actor Vector Motive Goal Attack
03
Threat Intelligence Research

With the threat model established, TALAS researches real-world attackers and campaigns that match the profile, grounding the scenario in current intelligence and real-world attacks rather than hypothetical constructs.

04
Discovery

TALAS gathers client-specific data across three areas: Culture and awareness, technical controls, and network design. This data becomes the statistical foundation of the event.

d10
The Statistical Engine

Discovery data calibrates a ten-sided die. If 70% of employees know how to report phishing, a roll of 1–7 succeeds, and 8–10 represents the 30% who didn't. Outcomes feel earned, not scripted.

05
Scenario Construction

The attack is written as a full 4–6 page narrative, from the attacker's reconnaissance to the moment of breach. The exercise drops them mid-incident, after the attacker has already gained a foothold.

06
Inject Design

The scenario is broken into discrete moments "injects" each presenting a decision, a challenge, or new information. A branching decision tree routes participants to different paths based on the choices they make, replicating the non-linear nature of a real incident.

07
Event Execution

A TALAS facilitator leads participants through the live scenario across both workstreams over 2 to 6 hours, in-person or virtual. The exercise can run with both teams together, or with executives briefed mid-event by the technical team, mirroring how real incidents escalate.

Workstream 01
Technical

Detection, scoping, containment, eradication, recovery, all managed by the technical team.

Workstream 02
Crisis Management

Communications, legal, public relations, executive decision-making all managed by leadership.

08
After Action Report

TALAS delivers a formal post-event report including the complete scenario, research, and documented observations. Identifying both what worked and where gaps were identified. The report serves as the regulatory compliance artifact demonstrating a formal incident response test was conducted.

Engagement complete. Regulatory evidence delivered. Gaps documented. Your team knows exactly where they stand, and what to do about it.

Get Started

Ready to
Roll?

Schedule a conversation with TALAS to discuss your organization's incident response posture and build a Challenge event designed around your actual threat landscape.