Protecting Encryption Keys with Azure Key Vault
summary
Shows how to deploy Azure Key Vault with HSM-backed keys, register an Azure AD app or use managed identities, and call the Key Vault SDK from C#. Demonstrates local key wrapping: generate AES keys locally, wrap/unwrap them with Key Vault to cut latency and cost, then encrypt DB fields per-tenant. Gives numbers: 4% of breaches are encrypted, Key Vault ops cost cents per 10k and HSM keys ≈$1 each plus per-op fees. Adds password salt protection and digital signatures for auditable settlements; the multi-tenant insurance example works and simplifies key rotation.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:12The threat of data breaches Cryptography overview Key management options Introducing Azure Key Vault HSM Patterns and Practices
- 4:14Data Breaches are Inevitable
- 4:28Don't Just Focus on Perimeter Security
- 10:45aws AWS HSM & AWS KMS
- 14:33Once a Key goes in the Key Vault, it never comes out again
- 19:00Keys vs Secrets
- 24:51Multiple Vaults for Environments
- 25:37NEVER share keys from production in any other environment
- 26:43Secrets are versioned in the Key Vault
- 41:43Salted Hash Passwords
- 52:50A digital is a mathematical technique used to validate the authenticity and integrity of a message, software or digital document
related talks
56mProtecting Encryption Keys with Azure Key Vault
59mProtecting Encryption Keys with Azure Key Vault
57mProtecting Encryption Keys with Azure Key Vault
10mCan you keep it a secret?
48mProtecting the confidentiality and integrity of your high value data with Azure SQL and SQL Server 2
22mSecure your secrets with automation
47mManaging your Secrets in a Cloud Environment
43mSecure Development