制定安全事件桌面演练方案
围绕模拟安全事件安排角色、议程和分阶段决策情境,形成主持指南与行动复盘模板。
完整提示词
<context>
A tabletop exercise walks people through a simulated incident by discussion, with no changes to live systems. It finds the gaps that only show up under pressure: nobody knows who can authorise taking a system offline, the contact list is out of date, legal hears about the incident on day three, or the backups everyone relies on were never tested. Exercises fail when the scenario is implausible for the organisation, when injects all arrive at once, when the facilitator lets it turn into a technical deep dive, or when nothing is written down afterwards. A good exercise has two to four clear objectives, a scenario that escalates in stages, injects that force decisions, and an after-action report with owned actions.
</context>
<task>
Plan a {{minutes}}-minute tabletop on: {{scenario}}
<participants>
{{participants}}
</participants>
{{#objectives}}
<objectives>
{{objectives}}
</objectives>
{{/objectives}}
1. If the participants are not described well enough to know who decides what (for example no one from leadership for a scenario that needs a business decision), say which role is missing and whether to proceed without it.
2. Objectives: use the given ones or propose two to four that are testable (for example "the team decides within 30 simulated minutes whether to isolate the finance network, and knows who authorises it").
3. Format and ground rules: no-fault, decisions are made as in real life, unknowns are answered by the facilitator, a parking lot for technical deep dives, and no live systems touched.
4. Roles: facilitator, scribe, optional observers, and which participant plays which real role.
5. Agenda: timed blocks that fit {{minutes}} minutes, with about a fifth of the time reserved for the hotwash.
6. Scenario and injects: a short starting situation, then five to eight injects that escalate (first signal, confirmation, spread, outside pressure such as media or a customer call, a complication such as a key person unavailable or backups partly affected, recovery choice). For each inject: simulated time, what is delivered and to whom, the discussion questions, the decision point, and what good looks like.
7. Facilitator guide: how to keep time, prompts for quiet participants, how to handle "we would just restore from backup" with a follow-up question, and optional curveballs if the group moves fast.
8. Hotwash questions and the after-action report template: what went well, gaps found, actions with owner and due date, and playbook updates.
9. Before answering, check the inject timings add up to the agenda and that every objective is exercised by at least one decision point.
</task>
<constraints>
- If the scenario or the participants are missing, ask for them in one message and stop.
- Keep the scenario plausible for the organisation described; do not name real companies or real threat groups as the attacker.
- Discussion only: no injects that require touching production systems or real phishing of participants.
- Avoid technical detail beyond what the participants can act on; route deep dives to the parking lot.
- Treat legal, regulatory and insurance questions as decision points for the right people, not as answers the exercise supplies.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown document with the sections in the output contract. Agenda as a table: Time | Block | Purpose. Injects as numbered sections with Simulated time, Delivered to, Inject text, Questions, Decision point, What good looks like. After-action template as a fill-in table: Finding | Impact | Action | Owner | Due.
</output_format>可替换内容
- {{minutes}}
- {{scenario}}
- {{participants}}
- {{#objectives}}
- {{objectives}}
- {{/objectives}}
- {{> output/uncertainty}}
分类与标签
办公效率、桌面演练、事件响应、团队协作、演练复盘