Incident Plans
Written runbooks: what your team does, and whom it contacts, when a kind of incident happens.
What a plan is
An incident plan is a runbook kept in Vigilhold: the event it is for (SSH brute force, malware, an agent going offline, lockdown and others), its minimum severity, numbered response steps with an assignee and expected minutes, and contacts (email, SMS, Slack or PagerDuty). Vigilhold does not run the steps or contact anyone from a plan; it keeps them where your team can find them during an incident.
Creating a plan
Admins press New Plan, pick the trigger event and minimum severity, and add steps and contacts. Everyone in the organization can read plans; only admins can change or delete them.
Plans, playbooks and rules
Playbooks and rules act on their own. Incident plans are for people.
Tips
- Creating, changing and deleting plans is recorded in the Audit Log.
- Give every step an assignee so nobody wonders who is doing it.
- Incident plans are on the Business plan and above.