That’s how most breaches start. Not with a dramatic exploit, but with a forgotten door left unlocked. In Kubernetes, that door can be a permanent credential, an over-granted role, or a token that never expires. These standing privileges stay in place for days, weeks, or months—long after they’re needed. And in the wrong hands, they turn into production-wide compromise.
Zero Standing Privilege flips that script. Instead of always-on access, you grant only what’s needed, only when it’s needed, and only for as long as it’s needed. When the task is done, the privilege disappears. No leftovers. No attack surface waiting to be found.
In Kubernetes, Zero Standing Privilege means there is no permanent kubeconfig with cluster-admin bound to it. It means developers, CI/CD pipelines, and external systems receive time-bound access with scoped permissions tied directly to the action at hand. Kubernetes RBAC and short-lived credentials replace static secrets. Auditing every request becomes straightforward. Incident response becomes faster because the map of who accessed what is clean and current.
This approach also kills the “silent sprawl” of access rights. In many clusters, a role granted for one emergency becomes invisible background noise. Weeks later, the same role can let a compromised developer account gain root-level cluster access without tripping alarms. Zero Standing Privilege removes that risk at its root.