Secure your secrets with automation
summary
Automates rotation of partner-facing credentials by scanning Key Vault for secrets expiring in the next month, generating new values and updating Azure AD app registrations or storing random secrets in demo runs, then notifying partners by email and opening Azure DevOps tickets in production. Uses Azure Key Vault and Logic App + Automation Account with PowerShell cmdlets, encodes the app object ID in the secret name to re-link credentials, handles rotation end-to-end, works in demo, identity token login latency is a known pain point.
AI-written summary · about
chapters (10)
- 0:00Introduction and agenda
- 1:04What are secrets
- 3:32Why secure secrets
- 6:01Pain points of manual rotation
- 8:54Business scenario overview
- 13:54Key Vault setup and policies
- 14:38Automation requirements
- 15:23Demo architecture explained
- 17:31Secret rotation demo
- 20:47Results and next steps
related talks
46mSecrets Management for the Modern Tech. Pro
44mSecrets at Scale: Managing Cloud Credentials with PowerShell Automation
43mSecure Development
10mCan you keep it a secret?
47mSecuring Serverless Applications in Azure
30mLong Live Short Lived Credentials - Auto-rotating Secrets At Scale
59mProtecting Encryption Keys with Azure Key Vault
20mAzure Authentication With Vault