Why tabletop exercises matter
Incidents are rarely lost because of a missing technical control. They are lost in the first hours, when nobody is sure who can authorise taking a system offline, whether a regulator must be told, what to say to customers, or how to reach a key supplier at 2am.
A tabletop exercise rehearses those decisions in a safe setting. Regulators increasingly expect it: DORA requires financial entities to test their ICT business continuity and response plans, NIS2 requires business continuity and crisis management, and the Reserve Bank of Zimbabwe's DFS guidelines anticipate regular sector tabletop exercises.
Know your reporting clocks
Many scenarios hinge on reporting deadlines. Make sure participants know which ones apply:
| NIS2 (EU) | Early warning within 24 hours, notification within 72 hours, final report within one month |
|---|---|
| DORA (EU financial) | Initial notification within 4 hours of classifying as major and no later than 24 hours from awareness, intermediate within 72 hours, final within one month |
| GDPR (EU) | Notify the supervisory authority within 72 hours of becoming aware of a personal data breach, where feasible |
| POPIA (South Africa) | Notify the Information Regulator and data subjects as soon as reasonably possible, via the eServices portal |
| RBZ DFS (Zimbabwe) | Escalate major DFS incidents to the Reserve Bank within 3 hours |
| EU Cyber Resilience Act | Manufacturers: early warning within 24 hours of actively exploited vulnerabilities and severe incidents, since 11 September 2026 |
Designing a useful exercise
Choose a relevant scenario
Base it on your real threat profile: ransomware affecting core systems, payment or mobile-money disruption, compromise of a cloud tenant, failure or breach at a critical supplier, or a large personal-data exposure. Use intelligence from your own exposure validation results to make the initial compromise realistic.
Invite the right people
Include technology and security, legal and compliance, communications, operations, finance, HR and executive decision-makers. For board-level exercises, run a shorter session focused on strategic decisions.
Inject pressure
Release information in stages through "injects": a ransom note, a journalist's call, a regulator query, a supplier that cannot be reached, social media posts from customers. Each inject should force a decision.
Test specific objectives
- Are incident severity and notification thresholds clear, and who decides?
- Can the team meet the applicable reporting clocks?
- Are customer, staff and media communications prepared and approved quickly?
- Is evidence preserved for forensics and insurance?
- Are recovery priorities agreed, and do backups actually restore?
- Can critical suppliers be escalated out of hours?
After the exercise
The value lies in what changes afterwards. Within a week, issue a short report covering what worked, what did not, and a list of dated remediation actions, each with an owner and verification criteria. Update playbooks, contact lists and decision authorities. Then schedule the next exercise, ideally with a different scenario, and check that previous actions were closed.
Common mistakes to avoid
- Choosing a generic scenario that does not reflect your real systems or threats
- Inviting only IT, so legal, communications and executive decisions are never tested
- Scripting the outcome so participants never face genuine uncertainty
- Ignoring reporting clocks until late in the scenario
- Producing an attendance record instead of a dated action plan
Frequently asked questions
How long should a tabletop exercise last?
Most technical or management exercises run for two to four hours. Executive and board sessions are often shorter, around 60 to 90 minutes, and focus on strategic decisions.
How often should we run tabletop exercises?
At least annually, and after major changes such as a new core system, acquisition or key supplier. Many regulated organisations run several smaller exercises each year with different scenarios and audiences.
Should the board take part?
Yes, at least annually. Board members need to understand their role in major incidents, such as approving disclosure, engaging regulators or deciding on ransom demands, before an incident happens.
What is the difference between a tabletop and a live exercise?
A tabletop is discussion-based and tests decisions and coordination. Live or functional exercises test technical response and recovery, such as restoring systems from backup or failing over to an alternate site.
The useful output of a tabletop exercise is a resilience improvement plan, not an attendance record.
SecuriCentrix designs and facilitates technical, executive and board tabletop exercises aligned to NIS2, DORA, POPIA and RBZ requirements.
Free readiness checklists
Work through the checks with your team, then talk to us about any gaps.
DORA Compliance Checklist
21 checks · Regulation (EU) 2022/2554
Get the free checklistIreland and EUNIS2 Readiness Checklist
25 checks · Directive (EU) 2022/2555
Get the free checklistSouth AfricaJS2 Cyber Resilience Readiness Checklist
21 checks · Joint Standard 2 of 2024
Get the free checklistRelated reading
Sources
- Directive (EU) 2022/2555 (NIS2), Article 23
- Regulation (EU) 2022/2554 (DORA)
- Information Regulator: POPIA FAQs
- Reserve Bank of Zimbabwe: Guidelines on DFS Security (July 2026)
- European Commission: CRA reporting obligations
This article is general guidance, not legal advice.
