Secrets as Code
summary
Claims that secrets can be automated using Vault and shows a live dev-server demo: create a policy, enable AppRole, generate role ID and secret ID, log in to get a token, read allowed secrets and get a 403 for others. Shows the chicken‑and‑egg fix: bake the role ID into images via Terraform (or similar) and deliver a wrapped secret ID over a separate channel so the app unwraps, logs in, and fetches secrets.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:20Developers dont care about security
- 0:43The right mindset
- 1:11Automation
- 1:26Infrastructure as Code
- 2:53Secrets
- 4:15Separate Version Control
- 5:44Encryption
- 7:40Identity Access Management
- 9:16How does it work
- 11:01Demo
- 17:38Chicken or Egg
- 20:48Integration
- 22:15Conclusion
related talks
29mIntro to secrets management using Vault
25mCan you keep a secret?
24mDeveloper-First Application Security and DevSecOps
28mHow to Store Secrets—and When Do You Need Them—in HashiCorp Vault
38mKeeping Secrets - A Practical Approach to Managing Credentials
30mSimplifying Secrets Management in the Public Cloud
24mSecrets at Scale with Vault and Waypoint
41mHiding secrets in a Vault