Can you keep it a secret?
summary
Argues that production secrets belong in a cloud secret store rather than a homegrown DB and demonstrates using Azure Key Vault with Azure Active Directory for app identity, access policies, built‑in crypto and optional hardware security module backing. Shows one‑line SDK calls to get/set secrets, examples of encrypt/decrypt and key rotation, and a working demo of certificate‑based authentication to avoid shipping client secrets. Notes low cost, auditing trails for access, and that DIY secret stores usually fail security best practices.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:26What are secrets
- 0:58Types of secrets
- 1:17Project example
- 2:34Bruce Schneier quote
- 6:59Demo
- 9:02Summary
related talks
47mManaging your Secrets in a Cloud Environment
43mSecure Development
46mSecrets Management for the Modern Tech. Pro
56mDiscover the Art of Managing Secrets as a Software Engineer.
59mProtecting Encryption Keys with Azure Key Vault
30mSimplifying Secrets Management in the Public Cloud
55mEverything a .NET dev needs to know about configuration and secret management
01h 02mEverything a .NET developer needs to know about configuration & secret management