Zero-Trust OpenClaw: Gateway Security and Shell Blocking

The Identity-First Security Model OpenClaw's security operates in three layers, evaluated sequentially: identity, scope, then model. Most teams get this backwards. They start with model guardrails (system prompts) and add identity controls as an afterthought. That's wrong. Layer 1: Identity Who can talk to the bot? This is your first gate. Options include DM pairing, explicit allowlists, or open access. Until identity passes, no message processing occurs. Layer 2: Scope Where can the bot act? Tool policies, sandboxing, device permissions, and filesystem boundaries. This layer assumes identity passed but limits what authenticated users can do. Layer 3: Model What does the model decide to do? By the time you reach this layer, blast radius is already constrained. The model can be manipulated, but damage is bounded. Identity → Scope → Model ↓ ↓ ↓ Gate Limit Contain The rationale is simple: most failures aren't sophisticated exploits. Someone messages the bot and it complies. A well-crafted