Skip to content

:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.

docs(agents): add the egress rule to the security guidance (#122904)

Tom Piccirello560bec8c2f87
diff --git a/.agents/security.md b/.agents/security.md
index cbe3498226e3..0e0cd304d9ac 100644
--- a/.agents/security.md
+++ b/.agents/security.md
@@ -192,6 +192,14 @@ semgrep --test .semgrep/rules/security/
docker run --rm -v "${PWD}:/src" semgrep/semgrep semgrep --test /src/.semgrep/rules/security/
```
+## Outbound requests and SSRF
+
+PostHog Cloud sends production egress through a Smokescreen proxy. On a code path that goes
+through the proxy, treat raw SSRF, such as a request to an internal IP or to cloud metadata, as
+mitigated. A code path that bypasses the proxy, and a self-hosted deployment, do not have this
+control. A request that probes or trusts an attacker-controlled server is always in scope. The
+SSRF rule in `.agents/skills/security-audit/SKILL.md` says which control is load-bearing.
+
## Out-of-band interaction domains
`posthog/security/crosslang/oob_domains.json` lists the services that capture out-of-band