12.09 Operating the Tabletop Exercise Extra
Activate the Tabletop Exercise Extra, grant its two permissions, understand what data it exposes and how much AI it uses, and know what deactivating it removes.
Requires: Tabletop Exercise Extra
Core SimpleRisk has no tabletop exercise feature. This article covers activating and running the Extra for your organization.
Why this matters
The Extra lets users run AI-facilitated incident response tabletop exercises built from your own records. That makes two things your responsibility: who is allowed to run them, and what data they can put in front of other people.
Before you start
- An AI provider is configured under the AI settings. Without one, no scenario can be generated and the Extra's admin page says so.
- The Extra's files are in place. If they aren't, the page offers a link to purchase it.
Step-by-step
- Go to Configure, then Extras, open Tabletop Exercise Extra and select Activate. Activation creates the Extra's tables and its two permissions.
- Under user management, grant Able to Facilitate Tabletop Exercises to the people who will create and run exercises. It includes the ability to participate. Grant Able to Participate in Tabletop Exercises to everyone who will be assigned to a role.
- Tell facilitators where the entry point is: Tabletop Exercises in the left menu, which only people holding one of the two permissions see.
What the permissions expose
Neither permission gives direct access to records. But a facilitator's exercise can reach whatever that facilitator can see (narrowed to the categories they tick), and every participant sees scenario text and answers built from it. The permission descriptions in user management carry that warning. If someone should not be able to put, say, risk or audit data in front of a group, don't give them the facilitate permission. When a facilitator picks governance documents as the incident response plan, the Extra reads those documents' attached files only if the facilitator also holds Allow Access to "Governance" Menu and Able to View Documentation, the same two permissions needed to download them directly; files attached to other records, such as audit evidence, are never read.
That includes installs that use the Team Separation or Organizational Hierarchy Extras. Those Extras limit what each person can open themselves, but a question a participant asks during an exercise is answered from the facilitator's view of the records, inside the exercise's reach. A participant can therefore see details of records they couldn't open on their own if the facilitator can. Treat granting the facilitate permission, and choosing who takes part, as a decision about sharing that data.
Reach is fixed when the exercise is created, while the content stays live. If a facilitator's account is disabled or locked mid-exercise, questions that need their data access fail with a notice rather than quietly answering from nothing, and the assessment reports that as an access problem, not a documentation gap.
AI usage
Each exercise has its own ceiling: 400 AI calls and 1.5 million tokens for generation and the live session. The final assessment is exempt from the call ceiling so a heavily used exercise can still be assessed, but regenerating an assessment is limited to three attempts. Participants are limited to six questions a minute.
Encryption
Availability of encryption. In this release the Extra stores exercise content as entered. It does not use the Encrypted Database Extra, and activating that Extra does not change this. The Extra is built to use SimpleRisk's own Core encryption once that ships, and the protection described below applies from then on. Until then, treat exercise content as unencrypted in the database and its backups, and don't put secrets in it.
Once Core encryption is available, exercise content (scenario text, answers, notes, decisions and the assessment) is stored encrypted using the Core encryption key. If no key is available, the Extra refuses to store content rather than writing it in the clear.
API
All routes live under /api/v2/ttx, are available only while the Extra is active, require API authentication, and check the same two permissions. The OpenAPI documentation lists them.
Deactivating
Deactivating the Extra permanently deletes every exercise, transcript and assessment, and the confirmation says so. Export what you need first. Finalized assessments are the records most people want to keep.
Common pitfalls
- What is sent to the AI provider about earlier exercises. When a facilitator leaves Build on my previous exercises ticked, the request for new scenario ideas includes a short summary of that facilitator's five most recent finished exercises: the scenario title and threat, the objectives rated partially met or not met, and the incident response plan gaps found. Nothing from other facilitators' exercises is included, and the summary is not stored anywhere new. Facilitators who don't want it sent can untick the option when they create the exercise.
- No AI provider. Generation never starts. Check the AI settings first.
- Granting facilitate broadly. It indirectly exposes the data that person can see.
- Participants who lack the permission. They can't be assigned to a role. When the Organizational Hierarchy Extra is on, the list of people offered is limited to the facilitator's selected business unit, the same as the stakeholder field when submitting a risk.