clawdbot-security

You can audit a Clawdbot installation for security misconfigurations by running the clawdbot-security-audit CLI, which checks gateway bindings, file permissions, authentication modes, Node.js versions, and MDNS settings, then outputs concrete remediation steps.

Security checks to harden Moltbot gateway bindings and permissions include validating gateway binding configurations, verifying file permissions, enforcing secure authentication modes, checking Node.js versions, evaluating MDNS broadcasting, and testing optional external network reachability.

You can automatically fix authentication and network exposure issues on your Clawdbot server by running the audit CLI with the --fix flag, which enforces secure defaults and applies remediations for detected vulnerabilities.

The Clawdbot security audit supports optional deep external reachability checks to evaluate network exposure, alongside standard checks for MDNS settings, gateway binding, file permissions, authentication mode, and Node.js version.

The best way to secure Clawdbot external network exposure and gateway bindings is to run an automated security audit that detects misconfigurations, enforces secure defaults via auto-fix, and provides firewall setup and TailScale integration recommendations.

Your Moltbot deployment fails Node.js version and MDNS security checks because the audit detects outdated Node.js versions or insecure MDNS broadcasting settings, flagging them as misconfigurations that require remediation to enforce secure defaults.