Vigilhold documentation
Install the agent, connect your Linux servers, and use the dashboard and API.
- Add your first Linux server: Install the Vigilhold agent on a Linux server with one command and watch it come online in the dashboard, in under a minute.
- Fit Vigilhold to how your team works: Answer four questions about your team and Vigilhold sets its hours, notifications and how much it does on its own, per server group if you like.
- Review a server security alert: Find the alerts that need you, read the evidence collected on the server, and acknowledge the alert or act on it from the Vigilhold dashboard.
- Approve or reject a response: When Vigilhold wants to act outside the limits you set, it asks first. How to approve or reject a response, with a reason, in the dashboard or Slack.
- Inspect one Linux server: Everything Vigilhold knows about one server: live CPU, memory and disk, processes, security checks, services, pending updates and alert history.
- Get server alerts in Slack: Connect Vigilhold to Slack to get critical server alerts and approval requests in a channel, and answer approval requests without leaving Slack.
- Find CVEs affecting your servers: See the vulnerabilities that matter for the packages your Linux servers actually run, what fixes each one, and get told when new ones appear.
- Create an API key and act on a threat: Let a script, CI job or SOAR playbook read Vigilhold data and respond to threats with a scoped API key, under the same rules as your team.
- Write a server security rule: When something happens on the servers you choose, notify, open a ticket or respond. Rules that act prove themselves in a dry run first.
- Hosts: every Linux server at a glance: The Hosts page shows the live status of every server running the Vigilhold agent: what each status means and how to add a server.
- Server security alerts: Every rule-triggered and agent-detected alert in one place: alert types, severity levels, acknowledging, grouping and exporting alerts.
- Fleet timeline for Linux servers: All your servers on one shared time axis, so a failure that spreads from one host to the next is easy to spot. Reading the chart and filtering it.
- Journal errors, OOM kills and crashes: The Error Center collects systemd journal errors, kernel OOM kills and service crashes from every server, so you can acknowledge or fix them.
- IP bans and SSH brute-force attackers: See the IP addresses Vigilhold has banned on your Linux servers and the SSH brute-force attackers behind them, and lift a ban when you need to.
- Monitor systemd services: The state of every systemd service across your Linux servers, what each state means, and how to start, stop or restart a service from the dashboard.
- CVE scanning and exposure reports: Vulnerability scanning for the packages on your servers, exposure reports and urgency scoring, so you know which fixes to apply first.
- Automatic response playbooks: Built-in automatic responses to threats on your Linux servers that you turn on or off, how they are exported, and how to add your own.
- Incident response plans: Written runbooks for your team: what to do, and whom to contact, when a given kind of incident happens on your servers, and how they relate to rules.
- Encrypted credential vault: Store credentials encrypted in Vigilhold, readable only by your organisation's owners and admins, and see who uses each vault entry.
- Group servers with tags: Organise your Linux servers into groups with tags and see aggregated metrics for each group of servers in the Vigilhold dashboard.
- Run commands on many servers: Run a command across many Linux servers at once from the Vigilhold dashboard, with a preview of every target before you confirm.
- Server uptime dashboard: Uptime for each server, day by day, over the last 90 days: how it is calculated, what else the dashboard shows and what it does not do yet.
- CIS, SOC 2 and PCI-DSS reports: Point-in-time compliance snapshots of your Linux servers for CIS Level 1 and 2, SOC 2 and PCI-DSS, plus a SOC 2 auditor pack to hand over.
- Users, roles and invitations: Manage who can reach your Vigilhold organisation: what the Owner, Admin, Analyst and Viewer roles can do, and how to invite teammates by email.
- Audit log of every action: Every action in your Vigilhold organisation is recorded: logins, agent commands, playbook runs, invites, setting changes and IP bans, and nobody can edit it.
- Notifications, integrations and on-call: Configure notifications, alert rules, integrations, on-call rotations and maintenance windows for your servers in Vigilhold settings.
- Install the Linux security agent: Install the Vigilhold agent on a Linux server in under a minute: requirements, the one-line install, what it adds, how to verify it and remove it.
- Go live, step by step: From a new account to every server watched: start on a staging server, check the first signal, set notifications and invite your team.
- Getting started with Vigilhold: Go from zero to monitored Linux servers in five minutes: add a server, open Hosts, set up notifications and look at your first alerts.
- API quick start: Make your first Vigilhold API call in under two minutes: create an API key, send a request, and learn the base URL, rate limits and pagination.
- API authentication and key scopes: Bearer token authentication for the Vigilhold API, key scopes, least-privilege key design, key rotation and webhook signature verification.
- Servers API: List and inspect servers through the Vigilhold API, read live metrics, and filter servers by status or region. Endpoints and response shapes.
- Alerts API: List, filter and acknowledge server security alerts through the Vigilhold API, one at a time or many at once. Endpoints and response shapes.
- Webhooks and HMAC signatures: Register webhook endpoints, subscribe to Vigilhold event types with wildcards, verify HMAC signatures, and see how delivery is retried.
- Real-time event stream (SSE): A Server-Sent Events feed of alerts, metrics, IP bans and server status from Vigilhold, with filters, event types and a Python example.
- Event ingest API: Push custom events from your own systems into the Vigilhold timeline and webhook pipeline, and list past events through the API.
- Automation API: ban IPs, stop processes: Ban IP addresses, stop processes, quarantine files, run scans and lock servers down through the Vigilhold API with a scoped key.
- Docker host security agent: Install the Vigilhold agent on a Docker host with one docker run command: how it works, the container inventory, and container escape checks.
- Cortex API: plans and kill chains: Read Vigilhold Cortex response plans, MITRE ATT&CK kill chains, overrides, fleet sweeps and threat sharing through the API.
- Agent protocol: How the Vigilhold agent connects to the platform, what it sends, how commands reach it, and how signed updates are delivered to your servers.