superlinearly as #APIs grow Customer services Order services Catalog Customer history … Order details Payments Audit Search Suggest … Order validation Fraud Alerts … | CONFIDENTIAL Service

Deploy Debug Debug in Production Cluster 1 Acco unt User Cluster 2 Istiod Order s User AWS EKS Istiod Order s User Acco unt Ingre ss Ingre ss Ingre ss Gloo Mesh Management Plane SRE

exploit a race condition, already have privileged access, or otherwise overcome moderate hurdles in order to exploit the finding. Low Exploitation requires implausible social engineering, a difficult race Related to the identification of authenticated users. Timing Related to race conditions, locking, or order of operations. 39 | Google Istio Security Assessment Google / NCC Group Confidential Appendix B:

● Solves our problems, but… ● All Service Owners must be aware of the Virtual Services API in order to define their SLOs. ● Potential typing errors when dealing with YAMLs. ● Potential drift between

owners Demo Admiral API Gateway Payments Product Info Proxy Proxy Proxy Book Order Proxy + k8s Istio mTLS mTLS mTLS + k8s + k8s Istio

to create VirtualService and DestinationRule before anything happens ● VirtualService evaluation order matters #IstioCon Checkpoint 1. Minimize time to bug detection: yes 2. Allow simultaneous tests:

container Pods are the atomic unit, not containers. 15 Shortcoming 1: Controlling the running order for containers Stabilizing Istio Kubernetes lacks good control APIs to customize the containers