Approved 2025/05/20 13:40 by ddehamer (version: 1) | Approver: @ai-us-principals
Azure Key Vault Best Practices
π Overview
Azure Key Vault is a cloud service for securely storing and accessing secrets, keys, and certificates. To maximize security, it's critical to follow industry-standard and Microsoft-recommended practices.
1. π Access Control
β
Use Azure RBAC (Role-Based Access Control)
β
Enable Role Assignments at the Right Scope
β
Use Managed Identities
2. π Secrets, Keys, and Certificates Management
β
Enable Soft Delete
β
Enable Purge Protection
β
Set Expiration Dates
Apply expiry dates to secrets, keys, and certificates.
Monitor expiration and renew proactively.
β
Use Versioning
3. π Monitoring and Auditing
β
Enable Logging
β
Set Alerts
Configure alerts for:
Unauthorized access attempts
Secrets/keys expiring soon
High-frequency access patterns
4. π Networking and Access Restrictions
β
Use Private Endpoints
β
Use Firewall Rules
5. π Encryption and HSM
β
Use Customer-Managed Keys (CMK)
β
Use Premium Tier for HSM-backed Keys
Required for high-assurance applications (e.g., FIPS 140-2 Level 3).
Supports Managed HSM for isolated key storage.
6. βοΈ Automation and Governance
β
Use Azure Policy
Enforce standards like:
Vaults must have soft delete enabled
Disallow public network access
Require private endpoints
β
Automate Secret Rotation
β
Regularly Review Access
7. π₯ Multi-Factor Authentication (MFA)
π Summary Checklist
| Practice | Status |
| π Soft Delete + Purge Protection enabled | β
|
| π« Public access disabled (Private Link preferred) | β
|
| π RBAC roles scoped to least privilege | β
|
| π
Secrets and keys have expiration dates | β
|
| π Logging and alerting configured | β
|
| π MFA + Conditional Access for admins | β
|
AI Knowledge