OpenClaw gateway security baseline
Use the OpenClaw gateway security documentation as the baseline control set for local-only deployment, token-based auth, narrow DM scope, and reduced tool access.
OpenClaw Gateway Security Baseline
Summary
Use the OpenClaw gateway security documentation as the baseline control set for local-only deployment, token-based auth, narrow DM scope, and reduced tool access.
Core Baseline
- Bind the gateway to loopback for local-only operation.
- Require token auth for the control plane.
- Set
session.dmScopeto isolate conversations per peer. - Use restrictive messaging profiles and deny runtime, fs, and automation groups by default where possible.
- Keep elevated execution disabled unless there is a strong operational reason.
Why It Matters
These controls directly reduce the blast radius for the most credible abuse paths: exposed local APIs, over-broad tool use, and data leakage through shared inboxes or channels.
Source
- Documentation source record: OpenClaw gateway security docs
Implementation Notes
- This baseline should be referenced from every exposure or messaging-related finding.
- A later phase can add concrete configuration snippets per deployment mode.
Get email updates
Get reviewed Armorer threat-intel updates when new findings are published.