OpenClaw gateway security documentation
This documentation page provides the vendor-recommended gateway security baseline, including loopback binding, token-based auth, restrictive tool profiles, DM scoping, and disabled elevated execution.
Date
Mar 11, 2026
First Seen
Mar 11, 2026
Last Reviewed
Mar 11, 2026
Publisher
OpenClaw
Source Type
docs
Related reading
OpenClaw Security GuideA practical baseline for local binding, scoped credentials, sandboxing, runtime checks, and Armorer Guard.
Securing OpenClaw with Armorer GuardHow Armorer wraps OpenClaw with managed setup, Docker hardening, health checks, approvals, and Guard-backed scanning.
Source Summary
What It Contains
This documentation page provides the vendor-recommended gateway security baseline, including loopback binding, token-based auth, restrictive tool profiles, DM scoping, and disabled elevated execution.
Extracted Claims
- Local-only gateway operation should use loopback binding.
- Control-plane access should require tokens.
- Shared or messaging workflows need tighter session scoping and restricted tool groups.
- Broad tool access and shared DMs should not be combined.
Evidence Quality
Primary documentation from the product vendor. Strong for hardening guidance.
Follow-Up
- Add environment-specific config examples as separate control records if needed.