Playbooks

Built-in automatic responses that you turn on or off.

What is a playbook?

A playbook is one of Vigilhold's built-in responses: when a kind of threat is detected, it bans the address, locks the server down, or raises an alert. There are eleven, covering SSH brute force, port scans, malware, unknown kernel modules, canary files, file integrity changes, lateral movement, privilege escalation and three kinds of AI-agent compromise. You cannot write new playbooks or add commands to them.

Turning playbooks on and off

Admins turn each playbook on or off for the whole organization. The ban and alert playbooks start on; the lockdown playbooks start off until you turn them on. Every change is recorded in the Audit Log.

Lifecycle and export

Each playbook shows how often it has run and succeeded, and a lifecycle stage (generated, observed, validated, approved, deprecated) that admins move it through as they come to trust it. Export downloads every playbook as JSON.

Your own responses

For your own logic (other conditions, chosen servers, notifications, tickets or another response) write a rule on the Rules page. See Write a rule.

Tips

Write a rule

All Vigilhold docs · Start a 14-day free trial