Lesson 15 Capstone — Multi-Vector Cyber-Kinetic Crisis
Theme:

Facilitator Notes & Model Responses — Lesson 15

For instructors · Strong plays, common mistakes, and model hotwash

Model responses by inject

InjectStrong playCommon mistake
1 · Urgent callRefuse the channel; verify on an independent number + code word; default "no" if unverifiedPaying, or "asking a question only they'd know" — both defeated by a prepared clone
2 · Inside signalReversible restriction + monitoring; evidence vs inference; no public accusationPublicly accusing the staffer, or freezing entirely while the intrusion spreads
3 · Lock-outDirect not do; contain vs preserve; pay/no-pay by policy, backups, legal/sanctionsImprovising the pay decision on the ransom amount or the board's instinct
4 · AbroadAssume compromise; quarantine/rotate; PACE fallback; weigh personal safetyAssuming "probably fine"; having no alternate channel to the principal
5 · Story breaksCalibrated uncertainty: known / unknown / being done; no premature attributionNaming a state under pressure, or saying nothing at all

Why the two poll answers are C

Model hotwash

A strong debrief concludes that the teams which coped best were not the cleverest in the moment but the ones carrying prior decisions: a verification rule, a pay/no-pay policy, a PACE plan, tested backups, and a real crisis roster. It ends with three concrete, owned, dated actions — typically closing the exact gaps the injects exposed. Keep it blame-free; the goal is a better next incident, not a verdict on this exercise.

Homework — what good looks like

Task 1

Honest reviews identify a specific moment where preparation (or its absence) was decisive, not a general "we did okay."

Task 2

The best submissions convert felt discomfort into three specific, owned, dated fixes.

Task 3

A real date and facilitator turn "we should rehearse" into a scheduled control.