Security policy
Warden is a security product, so we want to hear about any weakness in it. If you think you have found one, please tell us privately first.
Report to: [email protected] with the subject "Warden security report". Include what you found, how to reproduce it, and what an attacker could do with it.
In scope
- warden.ripitlabs.com: the gateway API, the console, the quickstart and the public ledger endpoints
- The Warden SDKs and MCP server (
/sdk/warden.py,/sdk/warden.mjs) - The self-hosted Warden bundle and its Kubernetes manifests
Especially interesting: reading or changing another workspace's data, getting an agent's traffic past Warden's checks, reaching internal addresses through Warden, getting a stored key back out, and editing the log without detection.
Please don't
- Test against other customers' workspaces or data. Use your own workspace, or ask us for a test one.
- Run denial-of-service or high-volume tests, or anything that degrades the service for others.
- Use social engineering, phishing, or physical attacks.
- Test other Rip It Labs services or third-party services (Cloudflare, Google, ntfy, Slack) through this policy.
- Keep or share any data you reach beyond what is needed to show the issue.
What we do
- We aim to acknowledge reports within 3 business days and to keep you updated until the issue is fixed.
- We will not pursue legal action against good-faith research that follows this policy.
- With your permission, we will credit you once the issue is fixed.
- We do not currently run a paid bug bounty.
Machine-readable contact: /.well-known/security.txt