Audit OpenClaw security

Audit systems the user owns or is authorised to assess. Start read-only; get approval for configuration changes, repairs, restarts, credential rotation, or exposure changes. Never request raw tokens, passwords, cookies, or credential stores.

Establish the trust boundary

Record the installed OpenClaw version, host/container arrangement, gateway bind address, proxy/tunnel path, and who can send messages or invoke tools. One gateway is one trusted operator/team boundary, not isolation between mutually adversarial users. Use separate gateways and credentials for separate trust domains.

Host installs and container images can have different bind defaults. Inspect the running listener and published container ports rather than inferring exposure from the install method.

Collect evidence

Resolve SKILL_DIR to the directory containing this file. Bundled paths are relative to that directory, not the project being audited. Keep output local and private until reviewed.