Fast Secrets: Why Secrets Need to Match the Infrastructure
summary
Containers live short lives—93% under a week and 44% under five minutes—so static credentials fail. The talk shows a concrete stack: Packer + Terraform for images and policies, Vault as identity broker issuing dynamic, time-bound credentials to Kubernetes workloads, and Consul for service observability. Implementation enforces mutual TLS via proxies, identity-based authN/authZ, and least privilege; studies cited: ~57–79% of firms had secrets incidents, compromised credentials start 1 in 5 breaches (~$4.37M), zero trust cuts breach cost ~$1.76M.
AI-written summary · about
chapters (8)
- 0:00Introduction to fast secrets
- 2:30Secrets lifecycle and hybrid world
- 6:26Security risks of long-lived secrets
- 9:36Why dynamic secrets matter now
- 13:56Zero trust secrets management
- 16:43Building zero trust infrastructure
- 18:53Continuous authentication and least privilege
- 20:43Industrializing zero trust secrets
related talks
38mKeeping Secrets - A Practical Approach to Managing Credentials
29mBehind Closed Doors: Managing Passwords in a Dangerous World
30mHow to Make Kubernetes Secrets Really… Secret?
26mSecret Management in Kubernetes: The GitOps Way - Benjamin Ritter
25mCan you keep a secret?
45mAttackers' Nightmare: An Infrastructure Without Secrets
29mSecuring Secrets in K8s Environments
05mBreaking Up with Long-lived Secrets: Secure Automation in the Mode...