There's a deep irony in modern Kubernetes security: the operators
we deploy to secure our clusters are themselves unsecured.
ArgoCD — which controls what runs in your cluster — often runs
with ClusterRole permissions that would make a penetration tester
weep. cert-manager manages TLS certificates for every service.
External Secrets Operator has read access to your entire secrets
vault. Strimzi controls your Kafka cluster. KEDA can scale any
workload.

These operators are privileged, trusted, and almost never audited.
They are also updated regularly, pulling new container images from
public registries. They are, in short, a perfect supply chain
attack surface — and most teams have zero visibility into it.

At Zscaler's Data Fabric team, we run 10+ operators in production
across multiple Kubernetes clusters. In this talk, I'll share
exactly how we threat-modelled, audited, and hardened our entire
operator ecosystem — and the automated guardrails we built to
keep it that way through upgrades.