Key management service security hardening
High
Cross-cloud
General
keyvault-key-management-service-security
Applies to
Microsoft.KeyVault/vaultsAWS::KMS::Key
What CGPulse checks
A resource passes this rule when properties.enableSoftDelete must equal true OR keyRotationEnabled must equal true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Configure key deletion waiting period to prevent accidental permanent key loss. In AWS Console: KMS > Keys > select key > Key actions > Schedule key deletion (set 30-day wait). See: https://docs.aws.amazon.com/kms/latest/developerguide/deleting-keys.html
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related Cross-cloud rules
- Block storage volumes must be encrypted
- Cache service security hardening
- Cache services must enforce TLS encryption in transit
- Container registry security hardening
- Database authentication must use managed identities
- Databases must not be publicly accessible
- IAM password policy must require minimum length of 14
- Kubernetes clusters must restrict public API access