security-dashboardReal-time security monitoring dashboard for OpenClaw and Linux server infrastructure. Monitors gateway status, network security, public exposure, system updates, SSH access, TLS certificates, and resource usage.
Install via ClawdBot CLI:
clawdbot install vegasbrianc/security-dashboardReal-time security monitoring dashboard for OpenClaw and Linux server infrastructure.
cd /root/clawd/skills/security-dashboard
sudo ./scripts/install.shThis will:
openclaw-dashboard user with limited sudo privileges (if non-root)Security Note: Running as a dedicated user with limited sudo is recommended. The dashboard only needs sudo for security checks (fail2ban, firewall, systemctl status) - not full root access.
Localhost only (secure by default):
Via SSH port forwarding:
ssh -L 18791:localhost:18791 root@YOUR_SERVER_IPThen visit: http://localhost:18791
sudo systemctl start security-dashboard
sudo systemctl stop security-dashboard
sudo systemctl restart security-dashboardsudo systemctl status security-dashboardsudo journalctl -u security-dashboard -fGet raw security metrics:
curl http://localhost:18791/api/security | jqThe dashboard follows security best practices to minimize attack surface:
The install script creates a openclaw-dashboard user with limited sudo privileges:
/bin/false)Service runs with security restrictions:
NoNewPrivileges=true # Cannot escalate privileges
PrivateTmp=true # Isolated tmp directory
ProtectSystem=strict # Read-only filesystem except skill dir
ProtectHome=true # No access to /home
ReadWritePaths=... # Only skill directory is writable
Restart=on-failure # Restart only on crashes (not always)127.0.0.1 (localhost only)If you choose root during install:
Use the dedicated user option for production deployments.
Edit /root/clawd/skills/security-dashboard/server.js:
const PORT = 18791; // Change thisThen restart:
sudo systemctl restart security-dashboardDefault: 127.0.0.1 (localhost only - secure)
Alternative: 0.0.0.0 (all interfaces - only with Tailscale!)
Edit server.js line 445:
server.listen(PORT, '127.0.0.1', () => {
// Change '127.0.0.1' to '0.0.0.0' if needed
});ā ļø Security Warning: Only bind to 0.0.0.0 if behind Tailscale or firewall!
Add custom checks in server.js:
getOpenClawMetrics() - OpenClaw-specific metricsgetNetworkMetrics() - Network securitygetSystemMetrics() - System-level checksgetPublicExposure() - Port/binding analysisDashboard generates real-time alerts:
Critical (Red):
Warning (Yellow):
Info (Blue):
Add security status to morning report:
curl -s http://localhost:18791/api/security | jq '.status'Monitor for critical alerts:
curl -s http://localhost:18791/api/security | \
jq '.alerts[] | select(.level == "critical")'Pipe alerts to notification systems:
./scripts/check-alerts.sh | xargs -I {} notify-send "Security Alert" "{}"Backend: Node.js HTTP server
Frontend: Vanilla JavaScript (no frameworks)
Port: 18791 (configurable)
Binding: 127.0.0.1 (localhost only)
Service: systemd unit
Files:
server.js - Main backend (metrics collection + API)public/index.html - Dashboard UIlib/ - Shared utilities (if needed)systemctl - Service managementss - Socket statisticsufw or firewalld - Firewall checktailscale - VPN status (optional)fail2ban - Ban tracking (optional)openclaw - Gateway monitoringAll dependencies are standard Linux utilities except OpenClaw.
sudo systemctl status security-dashboard
sudo journalctl -u security-dashboard -n 50
ss -tlnp | grep 18791
curl http://localhost:18791/api/security
pgrep -f openclaw-gateway
cat ~/.openclaw/openclaw.jsonsudo systemctl stop security-dashboard
sudo systemctl disable security-dashboard
sudo rm /etc/systemd/system/security-dashboard.service
sudo systemctl daemon-reloadThen remove skill directory:
rm -rf /root/clawd/skills/security-dashboardTo publish to ClawdHub:
clawdhub publish security-dashboardMIT
Created by Erdma for Brian Christner's infrastructure monitoring.
Generated Mar 1, 2026
A DevOps team uses the dashboard to monitor real-time security metrics across their OpenClaw and Linux server infrastructure. They track gateway status, network security, and system updates to ensure compliance and quickly address vulnerabilities like inactive firewalls or exposed ports.
An MSSP deploys this dashboard for clients to provide continuous security oversight. It helps monitor SSH access, fail2ban status, and certificate health, enabling proactive alerts and detailed reporting on security posture for multiple client environments.
Enterprise IT departments utilize the dashboard to audit security configurations and generate reports for compliance standards. They assess exposure levels, config file permissions, and resource usage to meet internal policies and regulatory requirements.
A startup with limited IT staff relies on the dashboard for automated security monitoring of their cloud servers. It provides alerts on critical issues like weak gateway tokens or high disk usage, allowing small teams to maintain robust security without extensive manual checks.
Offer the dashboard as a managed service with monthly subscriptions, providing clients with real-time alerts, detailed reports, and support. Revenue is generated through tiered pricing based on the number of servers monitored and additional features like custom integrations.
Sell enterprise licenses for the dashboard with annual contracts, including premium support, customization, and training. Revenue comes from upfront licensing fees and ongoing support packages tailored to large organizations with complex infrastructure needs.
Provide a basic version of the dashboard for free to attract users, then monetize through premium add-ons such as advanced analytics, API access, or integration with third-party tools. Revenue is driven by upselling these enhanced features to power users.
š¬ Integration Tip
Integrate the dashboard's API endpoint into existing monitoring tools or scripts to automate security checks and feed data into centralized logging systems for enhanced visibility.
Automatically update Clawdbot and all installed skills once daily. Runs via cron, checks for updates, applies them, and messages the user with a summary of what changed.
Full desktop computer use for headless Linux servers. Xvfb + XFCE virtual desktop with xdotool automation. 17 actions (click, type, scroll, screenshot, drag,...
Essential Docker commands and workflows for container management, image operations, and debugging.
Tool discovery and shell one-liner reference for sysadmin, DevOps, and security tasks. AUTO-CONSULT this skill when the user is: troubleshooting network issues, debugging processes, analyzing logs, working with SSL/TLS, managing DNS, testing HTTP endpoints, auditing security, working with containers, writing shell scripts, or asks 'what tool should I use for X'. Source: github.com/trimstray/the-book-of-secret-knowledge
Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
Monitor topics of interest and proactively alert when important developments occur. Use when user wants automated monitoring of specific subjects (e.g., product releases, price changes, news topics, technology updates). Supports scheduled web searches, AI-powered importance scoring, smart alerts vs weekly digests, and memory-aware contextual summaries.