Choose a scenario linked to a real service
Start with the organisation's critical services, their dependencies and credible disruptive events. Ransomware affecting identity systems, a hosting provider outage or data corruption may expose different weaknesses. Define the scope and assumptions so participants are not arguing about an undefined incident.
A useful scenario forces decisions about actual services, staffing and suppliers. Avoid introducing so many simulated events that participants cannot explain their choices or record evidence of the decisions.
Assign decision-makers and observers
Include incident response, operations, business continuity, communications, legal and management representatives as appropriate. The facilitator presents information; observers record response times, unresolved responsibilities and factual assumptions. Assign deputies where the exercise would otherwise rely on one individual.
Participants should know whether they are testing escalation, recovery, public communication, regulatory notification or several connected processes. Make each objective explicit before the exercise begins.
Exercise the difficult decisions
Introduce realistic uncertainties: conflicting incident reports, unavailable communications, a supplier that cannot confirm restoration, and a service owner who questions recovery priority. Ask who declares a crisis, authorises alternate operations and decides when recovered services are trustworthy.
Where the scenario may qualify as a significant incident, test the process for recognising and escalating the Article 23 reporting question. The exercise must distinguish the 24-hour early warning and subsequent notification requirements from ordinary internal status updates.
Evaluate evidence rather than performance
Record decision points, escalation paths used, information gaps, communications and the rationale for recovery priorities. Compare outcomes with the organisation's approved plans and objectives. A well-run discussion can still uncover an inadequate contact list or unworkable approval process.
Do not report a successful resilience test merely because attendees completed a meeting. Identify which capabilities were actually exercised and which technical processes still require functional verification.
Close actions and plan a retest
Assign a named owner and due date to each material issue. Update playbooks, contacts, supplier arrangements and delegated authority as necessary. Review repeated weaknesses with the management body and retest critical changes.
Tabletop records may support evidence of effectiveness assessment under Article 21(2)(f). Confirm applicable Member State requirements and, for specific digital and ICT provider categories, the additional requirements in Implementing Regulation (EU) 2024/2690.
Questions on the text
Does NIS2 require every entity to run the same tabletop exercise?
No. The general Directive calls for proportionate risk-management and effectiveness measures rather than one standard exercise for every entity.
Can a tabletop replace a recovery test?
No. Discussion exercises evaluate decisions and coordination; technical restoration tests establish whether systems and data can actually be recovered.