Is your OpenClaw installation secure?

Walk through the security checklist, check off what you have done, and see where your setup needs hardening.

Security Score: 0/16

Needs attention

0% complete

Environment(0/4)

.env file excluded from git (.gitignore)No API keys hardcoded in source filesAll required environment variables set correctly.env.example file exists for team reference

Network(0/4)

WebSocket port (18789) not exposed to public internetFirewall configured (ufw, iptables, or cloud security group)HTTPS enabled for any web-facing endpointsReverse proxy set up (nginx, Caddy, or similar)

Authentication(0/3)

API keys rotated within the last 90 daysNo default or example passwords in useMulti-user access restricted (or single-user only)

Skills(0/3)

All ClawHub skills reviewed before installationUnknown or unused skills removedSkill permissions reviewed (file system, network access)

Updates(0/2)

Running the latest stable OpenClaw versionCVE-2026-25253 (ClawJacked) patched

Want a professional audit?

This checklist covers the basics. A full security audit includes penetration testing, skill auditing, and a written remediation report.

Security audit service

OpenClaw Help

OpenClaw Help is a focused library of OpenClaw setup guidance, troubleshooting notes, and direct support options maintained by Milan.

milan@openclawhelp.dev

Quick Links

Home Issues Blog Services Contact

The public site is intentionally focused right now: browse issue fixes, read blog posts, or get in touch directly.

Built by Milan