How well do ransomware tabletop exercises prepare you for the real thing?

November 18, 2026 5 answers
Asked by c.83~mivlano

We run quarterly tabletop exercises, but I wonder how much they prepare a sysadmin team for the uncertainty and disruption of a ransomware incident. What should we be testing beyond the response plan itself?

Answers

Kivo

Take a key person out of the scenario. Make the director or the person who knows a critical system unavailable, then see whether the team can make decisions and keep moving without them.

That can expose both knowledge gaps and approval bottlenecks. A written plan is less useful if nobody else knows how to carry it out or who can authorize the next step.

_p.6+zeldruno:

It also gives you a concrete cross-training list instead of just noting that someone is a single point of failure.

Reply to this answer
_q62!veltruni.8

Build uncertainty into the exercise. The first affected system may not be the only one, and restoring it doesn't necessarily close the route the attacker used to get in.

Ask the team what evidence they need to understand the scope, how they would investigate the entry point, and what has to be checked before restored systems reconnect. You won't have perfect answers in a tabletop, but you can find out where the investigation depends on tools, logs, or expertise you may not have ready.

c.83~mivlano:

That sounds like a useful change from treating the first alert as the whole incident.

Reply to this answer
_h8~draxelo

Practice the communication side too. Everyone wants an update, but the technical team still needs uninterrupted time to investigate and recover.

Give someone responsibility for collecting updates and passing them on. In the exercise, decide who needs to know what, how often they'll hear from you, and how people communicate if the usual systems are down.

Vani:

A useful test is whether the update can honestly be that the scope is still unknown, without pulling the whole team into another meeting.

Reply to this answer
Orvi

Don't stop at deciding to restore from backup. Walk through which services come back first, what people can do while they're unavailable, and whether the team knows how to restore the less obvious dependencies.

A tabletop can expose assumptions, but it doesn't prove a backup works. Pair it with actual restore testing when you can.

Reply to this answer
9z+pixelcanoe_374

Plan for people getting tired. Long days, constant questions, and too many meetings can grind down a response. Work out who can cover critical roles and how handoffs will work, rather than assuming the same few people can stay sharp indefinitely.

Also, chaos isn't the only possible shape of an incident. It might start as a slow realization and then become a long list of focused tasks.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions