Keys, Certs and Vault: From DevSecOps to Post-Quantum
summary
Expired certificates cause real outages; a recent incident cost an evening of root‑cause work and would have been prevented by automated renewal and revocation. HashiCorp Vault Community Edition provides a centralized crypto control plane with PKI, transit and KV engines, CI/CD integration, short‑lived credentials and plugin backends so teams can automate rotation and audit trails. It already has 25,000+ users, supports experimenting with NIST‑finalized PQC (2022) and hybrid backends, and lets you avoid a costly TLS upgrade that can take 6–9 months by enabling short‑lived credentials.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:04Cost of expired certificates
- 2:31Cryptographic objects for apps
- 4:39Why crypto agility matters
- 9:15What is crypto agility
- 13:35Vault as crypto agility tool
- 15:44Vault high-level architecture
- 16:49Key management workflow
- 17:53Certificate management workflow
- 18:59Vault with CI/CD
- 20:25Post-quantum readiness with Vault
- 21:48Developer blueprint
- 23:13Future-proofing
- 24:22Q&A
- 25:28Vault vs Jenkins Secrets
- 26:53Vault implementation language
- 27:35Vault with AWS and Let’s Encrypt
related talks
26mCombining DevOps with PKI Compliance Using HashiCorp Vault & Consul
27mAddressing the growing threat of non-human identities with PKI
44mSecret Management with Hashicorp's Vault
51mRun modern PKI workflows with HCP Vault on AWS
43mSecret Management with Hashicorp's Vault
28mEmbedding secrets governance into the enterprise through organizational change
28mSecret Management with Hashicorp´s Vault
29mHow to get dynamic with secrets management