How To Run A Cybersecurity Tabletop Exercise At A Houston Business

Before you simulate anything, agree on the numbers that define an acceptable recovery.

Recovery metrics are the targets that decide how much data loss and downtime your business can survive. Four of them drive nearly every decision in an incident: RPO, RTO, WRT, and MTD.

Most teams discover during an exercise that they have never actually agreed on these numbers. That disagreement is the point. It is far better to have the argument about acceptable data loss in a planning room than at 2 a.m. while systems are down.

Set these first, and every later decision in the exercise has a yardstick. Skip them, and the discussion drifts into opinion.

A cyber incident is a business crisis, not just a technical one, so the room needs more than IT.

A tabletop exercise needs decision-makers who can commit the business, not just the staff who run the tools.

Technical teams drive the response, but the hardest calls in a real incident are not technical. Executive leadership decides whether to pay a ransom or halt operations. Legal counsel owns regulatory reporting and disclosure timelines. Communications keeps stakeholders informed without adding risk. Finance weighs both the immediate response cost and the longer business impact. Practicing together is how these people learn each other's constraints before a crisis forces the lesson.

Core decision-makers:

• Executive leadership
• IT and security teams
• Legal counsel
• Communications and PR
• Finance representatives

Supporting participants: department heads, HR, key vendors and partners, technical subject-matter experts, and a documentation specialist.

Three exercise roles keep the session honest and worth the time: a facilitator who guides discussion and introduces new twists, an observer who documents decisions and process gaps, and a timekeeper who protects the schedule so every phase gets real discussion.

The scenario changes from one exercise to the next; the structure stays the same.

Every effective tabletop exercise moves through five phases: brief, respond, escalate, respond again, and debrief.

• 1. Initial briefing - review the objectives, set ground rules, and introduce the opening scenario so everyone starts from the same picture.
• 2. Response phase - the team works the initial incident, documents the decisions and actions it takes, and names the resources it needs.
• 3. Scenario evolution - the facilitator introduces a complication that breaks an assumption, and the team adapts the plan in real time.
• 4. Second response - the team handles the escalation, coordinates across departments, and captures the revised approach.
• 5. Debrief - review the key decisions, identify the gaps, and write down the lessons and specific fixes while they are fresh.

The best scenarios are the ones your business would actually face.

A scenario earns its place when it maps to a threat your business is genuinely exposed to, and the strongest ones stack a second problem on top of the first.

Three scenarios cover most of what small and mid-sized businesses need to rehearse:

• Ransomware plus extortion - ransomware hits the finance department, then the attacker threatens to leak stolen customer data even after you restore from backups.
• Supply-chain compromise - a critical vendor reports a breach, and your own monitoring starts showing signs of internal compromise.
• Business email compromise - an executive's email account is taken over, and fraudulent wire transfers surface across multiple regions.

Here is the Houston-specific twist we build into most exercises: run a ransomware scenario during hurricane season, with a regional power or connectivity loss happening at the same time. Attackers time campaigns to disruption, and a plan that quietly assumes clean power and a full staff falls apart fast when neither is true. Gulf Coast businesses that skip this end up testing it live in August.

In one exercise we facilitated, a team decided not to pay after restoring from backups, and then the "attacker" revealed they had taken snapshots of the cloud environment and threatened to release them. The room went quiet. That single twist rewrote the team's entire data-handling and disclosure playbook. Real incidents rarely arrive one problem at a time.

If the session ends with "that went well," it failed.

A tabletop exercise that ends with applause failed; a good one ends with a written, prioritized list of things to fix.

The value is not in completing the scenario. It is in the specific, documented improvements that come out of it, plus the proof of readiness you can hand to an auditor, a regulator, or a cyber-insurance underwriter. A well-run exercise should deliver:

• Validated incident response procedures, and the gaps where they broke
• Clear roles and decision authority under pressure
• Better coordination between technical and business teams
• Documented lessons learned with named owners
• A prioritized list of specific improvement actions
• Audit-ready evidence that your organization tests its response

CinchOps is a managed IT services provider based in Katy, Texas, serving small and mid-sized businesses across the Houston metro area. CinchOps specializes in cybersecurity, network security, managed IT support, VoIP, and SD-WAN for businesses with 10 to 200 employees.

• Through cybersecurity services, we design custom scenarios, facilitate the session, and document every decision in real time.
• With business continuity and disaster recovery planning, we turn exercise findings into tested RPO and RTO targets.
• Backed by managed IT support and Houston IT support, we help you close the gaps the exercise surfaces.

Most businesses do not fail an incident because they lacked a plan. They fail because the plan had never been tested, and the first time anyone read it closely was during the breach. If your incident response plan has sat untouched since the day it was written, that is the gap worth closing this quarter. Talk to CinchOps about running your first tabletop exercise.