Trigger: specific threat of harm to a named executive, with indicators of capability or proximity. Includes on-site and travel contexts.
Security Playbooks
Pre-built responses so no one improvises the hardest minutes.
In an incident, people reach for whatever they remember. Playbooks make sure what they remember is aligned with legal, risk, and security—not adrenaline and guesswork.
Our playbooks are written to be executed by real people, under stress, with lawyers and leadership in mind. They’re the bridge between intelligence, operations, and documentation.
The elements below are illustrative. A real engagement would adapt them to your jurisdictions, risk profile, and internal policies.
How different roles see playbooks
Playbooks mean different things to different people. Use the selector to flip perspectives between Legal, Security, and Operations.
Legal and risk perspective
For Legal, playbooks are proof that the organization didn’t improvise. They show that specific threats were anticipated, that responses were pre-agreed, and that documentation was built into the workflow.
- Make it easy to reconstruct who knew what, when, and what they did.
- Align with internal policies, insurance positions, and regulator guidance.
- Clarify where outside counsel and investigators are brought into the loop.
Example playbook catalog
Filter by category and severity to see how different playbooks might be grouped. All examples are generic and for illustration only.
Trigger: repeated harassment, stalking behavior, or unwanted contact directed at executives or high-risk staff, online or offline, without explicit threat of violence.
Trigger: credible planning for protest or demonstration at or near a facility, with no current indicators of forced entry or targeted violence.
Trigger: confirmed or strongly suspected attempt to enter a site with weapons or clear intent to harm staff or visitors.
Trigger: impersonation or brand abuse accounts impersonating the organization without targeted threats of physical harm.
Trigger: digital incident that exposes routes, floor plans, or staff rosters in a way that may increase physical targeting risk.
Compose a playbook stack
Use this quick composer to sketch what a bundle of playbooks would look like for your environment. The summary updates as you toggle elements on and off.
In a live deployment this becomes a register of which playbooks exist, who owns them, and how often they are rehearsed and updated.
Foundational playbook stack
A foundational stack typically includes playbooks for executive threats and harassment, facility disruption, and digital incidents with physical implications. These provide coverage for the most common and visible risks.