Envoy Gateway End User Threat Model Report: Raising Awarenes...
summary
Threat model for Envoy Gateway (demoed on kind with kubectl, curl, port‑forwarding and a built container image) maps concrete attacks and mitigations: attackers can create a malicious cross-namespace HTTP route via shared Gateways when allowedRoutes match labels (recommend bind by namespace name), attackers can run a custom Envoy proxy image with tcpdump to sniff or tamper traffic, and attempts to patch a Gateway class show that Gateway class binding at startup reduces blast radius; v0.6 removes some cluster-role risks.
AI-written summary · about
chapters (9)
- 0:00Threat modeling Envoy Gateway
- 1:47What is threat modeling
- 4:36Gateway API architecture
- 8:43Multi-tenant deployments
- 12:37Cross-namespace route attack
- 17:33Malicious image compromise
- 23:14Gateway controller exploit
- 26:44Mitigations in 0.6
- 28:07Summary and report
related talks
26mSecuring the Gateway: A Deep Dive Into Envoy Gateway's Advanced Security Pol...
15mTaming AI Sprawl: Your First Look at the Envoy AI Gateway
05mKeynote: Envoy, the Engine for a Cloud Native Security Kernel
14mThreat Modeling for O11y: From Blind Spots to Actionable Insight
36mAdvanced Authentication patterns at the Edge
29mDebugging Envoy Tunnels: A Deep Dive
33mAvengers Assemble: Threat Modeling Kubernetes Clusters at a...
46mApplication Gateway Security What Developers Really Need to Know