เอกสารความปลอดภัยของ Gateway

When you want to lock things down properly, the /gateway/security docs are the place to go. They explain how to harden your deployment. 📖

Security centers on the Gateway because it is the single source of truth for sessions, routing, and every channel connection.

Since all traffic flows through the Gateway, securing it well protects every channel at once. That makes it your main focus.

The security docs walk through your core controls: tokens, allowlists, requireMention in groups, and mention patterns.

They reinforce the key idea: with full system access, allowlisting and mentions are the main guardrails you depend on.

Reach the security guide on the docs site under the /gateway/security route. Bookmark it before you connect real channels.

Read the security docs before you expose OpenClaw widely. It is easier to start tight than to lock down after the fact.

The docs explain the why; your ~/.openclaw/openclaw.json file is where you apply it. Read one, edit the other.

If access misbehaves, the /gateway/troubleshooting docs help you diagnose connection and routing problems alongside security.

OpenClaw is open source and evolving, so the docs are your most reliable, up-to-date guide as features change over time.

Revisit the security docs whenever you add a channel or sender. A quick review keeps your hardening choices intentional.

Let us confirm where security hardening guidance lives.

Harden through the Gateway using the /gateway/security docs, apply the advice in your config, and revisit it as you grow. ✅