Skip to main content

Multi-Endpoint Setup

In a distributed deployment, multiple Guard agents on different machines report to a centralized Manager server. The Manager provides fleet-wide visibility, cross-agent threat correlation, and centralized policy distribution.

Architecture


Deploy the Manager

1

Generate an Authentication Token

Create a secure token for Manager-Agent communication:
Store this token securely. Every Guard agent needs it to register with the Manager.
2

Start the Manager Server

The Manager accepts connections from Guard agents and provides:
  • Agent Registry — Tracks up to 500 registered agents
  • Threat Aggregator — Correlates threats across agents by source IP, malware hash, and attack pattern
  • Policy Engine — Distributes centralized rules and configuration
  • SSE Stream — Real-time event stream for the admin dashboard
3

Verify the Manager is Running


Deploy Guard Agents

On each endpoint machine:
1

Install Panguard

2

Start Guard with Manager Connection

The agent will:
  1. Register with the Manager on startup
  2. Send heartbeats every 30 seconds
  3. Report detected threats in real-time
  4. Poll for policy updates every 5 minutes

Agent Lifecycle


Cross-Agent Threat Correlation

The Manager’s Threat Aggregator correlates threats across all agents in real-time:
  • Source IP correlation — Same attacker IP seen on multiple endpoints triggers escalation
  • Malware hash correlation — Same malware fingerprint across agents indicates an active campaign
  • Attack pattern correlation — Related MITRE ATT&CK patterns within a 5-minute window
Cross-agent correlation uses a 5-minute sliding window with 24-hour data retention. Threats correlated across 3+ agents are automatically elevated to CRITICAL severity.

Policy Distribution

The Policy Engine allows centralized control over all Guard agents:
Policy changes propagate to all agents within their next 5-minute poll cycle.

Real-Time Monitoring

SSE Event Stream

Stream events from all agents in real-time:

Fleet Overview


Manager Configuration

Environment Variables

Optional SQLite Persistence

For large deployments, enable SQLite for persistent storage:

Production Deployment

For production, install the Manager as a systemd service and place it behind a TLS-terminating reverse proxy. See the System Service guide and Docker Deployment guide.

Security Checklist

  • Generate a strong authentication token (openssl rand -hex 32)
  • Use TLS termination (nginx/Caddy reverse proxy)
  • Restrict Manager port (8443) to Guard agent networks only
  • Run as a non-root system user
  • Set NODE_ENV=production for hardened mode
  • Store secrets in environment files with chmod 600

Architecture

Full technical architecture of the Manager-Agent system.

System Service

Install Manager and Guard as systemd/launchd services.

Docker Deployment

Run the full stack with Docker Compose.

Threat Cloud

Centralized threat intelligence across your fleet.