Enterprise Deployment Guide

Overview

The CyberVault Enterprise Security Platform centralizes threat detection, endpoint protection, cloud security, and compliance monitoring into a unified control plane. This guide covers a standard deployment on Linux servers with multi-node agent distribution.

Prerequisites

Installation

# Import GPG key & add repo
curl -fsSL https://packages.cybervault.io/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/cybervault.gpg
echo "deb [signed-by=/etc/apt/keyrings/cybervault.gpg] https://packages.cybervault.io/release/ stable main" | sudo tee /etc/apt/sources.list.d/cybervault.list
sudo apt update

# Install control plane & core services
sudo apt install cybervault-core cybervault-agent cybervault-dashboard
echo "✅ Installation complete. Run 'cybervault init' to configure."

sudo cybervault init --license-key "CV-XXXX-XXXX-XXXX-XXXX" \
  --fqdn "cv-primary.internal.net" \
  --admin-email "security-ops@yourcompany.com"

Configuration

Core configuration resides in /etc/cybervault/config.yaml. Below is a minimal production-ready example:

# /etc/cybervault/config.yaml
service:
  mode: production
  bind_addr: "0.0.0.0"
  port: 8443
  tls:
    enabled: true
    cert_path: /etc/cybervault/certs/server.crt
    key_path: /etc/cybervault/certs/server.key

security:
  encryption_algorithm: AES-256-GCM
  audit_logging: true
  log_retention_days: 90

integrations:
  siem_endpoint: "https://siem.internal.net/api/v1/ingest"
  ldap_bind: "ou=security,dc=company,dc=com"
  smtp_relay: "smtp.internal.net:587"

Network & Firewall

Ensure the following ports are accessible according to your security zones:

# Example iptables rules
sudo iptables -A INPUT -p tcp --dport 443 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8443 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 9090 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A OUTPUT -p udp --dport 53 -j ACCEPT
sudo iptables -A OUTPUT -p udp --dport 123 -j ACCEPT

Agent Deployment

Agents are distributed as lightweight daemons. They auto-register with the control plane using mutual TLS.

sudo cybervault token create --scope "agent:register" --duration 24h
# Output: CV-AGENT-TOKEN-xxxxxxxxxxxxxxxx

sudo wget https://packages.cybervault.io/releases/agent/cybervault-agent.deb
sudo dpkg -i cybervault-agent.deb
sudo systemctl enable --now cybervault-agent

Verification

Confirm your deployment is healthy and communicating correctly:

# Check control plane status
sudo cybervault status
# Expected: Nodes: 3/3 Active | Agents: 42 Registered | Uptime: 14d

# Verify TLS & API endpoint
curl -k https://localhost:8443/api/v1/health
# Expected: {"status":"healthy","version":"4.2.1","timestamp":"2025-03-15T10:22:00Z"}

# View real-time agent telemetry
sudo cybervault agent list --output json

Access the web dashboard at https://<your-server>:443. Default admin credentials are rotated during initialization. Check your inbox for the secure access link.

Troubleshooting

• Agent fails to register: Verify outbound port 8443 and DNS resolution. Run cybervault agent diagnose --verbose on the endpoint.
• Certificate validation errors: Ensure system time is synchronized within ±30s via NTP. Rotate certs with sudo cybervault cert renew.
• High CPU/memory usage: Check log verbosity. Set log_level: warn in config.yaml. Default telemetry aggregation runs every 15s; adjust via telemetry_interval.
• Logs location: /var/log/cybervault/core.log (control plane) and /var/log/cybervault/agent.log (endpoints).

Next Steps

Now that your platform is deployed and verified, proceed with:

1. Importing existing threat intelligence feeds
2. Configuring baseline security policies & compliance rules
3. Integrating with your SIEM, SOAR, and ITSM workflows
4. Scheduling your first security awareness training campaign