Docker sidecar + JIT secrets 的安全落地手册
针对不想把个人主机凭据暴露给代理的场景,这条实践把 OpenClaw 与浏览器拆到隔离容器,并用 1Password 服务账号做按需取密。
REDDITDiscovered 2026-02-12Author u/Quirky_Researcher
Prerequisites
- You can run Docker Compose and already have a private Tailscale tailnet (or equivalent private network).
- A dedicated agent identity exists (separate email + 2FA + password manager vault).
- 1Password CLI/service account (or equivalent vault API) is available for JIT secret retrieval.
Steps
- Deploy OpenClaw, Chrome, and Tailscale as separate sidecars; expose no public inbound endpoint.
- Configure browser automation to connect to Chrome container (CDP) instead of mixing browser runtime inside agent container.
- Create a scoped vault/service account and fetch secrets just-in-time when a task starts (not at process boot).
- Enable immutable audit logs for secret access and automation actions, then add a one-command credential revoke path.
- Run a threat-model pass (entry point, secret exposure, browser abuse, account takeover) before production usage.
Commands
openclaw gateway statusdocker compose psop whoamiVerify
Gateway and browser are reachable only from private network, and revoking the service account immediately blocks secret retrieval.
Caveats
- Headful browser anti-bot behavior and CAPTCHAs vary by target platform; bypass reliability is not guaranteed(需验证).
- Do not reuse personal identity for agent automation accounts.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗