One of the more reassuring things about OpenClaw is that it does not pretend security is just a vibes problem.

The platform ships a built-in audit tool and documents it clearly:

  • openclaw security audit
  • openclaw security audit --deep
  • openclaw security audit --fix
  • openclaw security audit --json

Why the security audit matters

OpenClaw's risk surface is not just one thing. It is gateway auth, browser isolation, plugin hygiene, allowlists, logging behavior, file permissions, session state, proxy trust, and whatever else you have turned on because it felt productive at the time.

The audit is there to catch common foot-guns before they become incidents.

The core commands

openclaw security audit

This is the baseline pass. Run it first, especially on an install you configured quickly.

openclaw security audit --deep

This adds a best-effort live gateway probe, which matters because a config file can look sensible while the running exposure is still messy.

openclaw security audit --fix

This applies safe deterministic remediations the tool knows how to make.

openclaw security audit --json

This is the one for automation, CI, or policy checks.

What the audit actually checks

The docs call out a practical list. It warns about things like:

  • gateway auth left too open
  • drifted plugin and hook install records
  • mutable allowlists where stable IDs are safer
  • sensitive logging settings
  • weak permissions on config, state, and sensitive files
  • trusted proxy setups missing critical pieces

What --fix changes

OpenClaw documents --fix as applying safe deterministic remediations, including:

  • flipping common open group policy settings to allowlist mode
  • setting logging.redactSensitive from off to tools
  • tightening permissions on state, config, credentials, auth profiles, sessions, and session logs

What --fix does not change

The docs also say --fix does not:

  • rotate tokens, passwords, or API keys
  • disable tools like gateway, cron, or exec
  • change gateway bind, auth, or network exposure choices
  • remove or rewrite plugins or skills

In other words, it tightens obvious defaults. It does not save you from your own architecture.

What you should actually do

Run the audit after installation. Run it after adding skills or plugins. Run it after network changes. Run it before exposing anything more broadly. Use --json in CI if you are serious. Use --deep when the running environment matters. Use --fix when you want OpenClaw to clean up the safe, mechanical stuff for you.

The security audit is not a magic shield. It is a flashlight.

Related reading