Are sensitive data encrypted with customer-managed keys whose use is limited to named identities and services?
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Question 20 of the assessment asks: Are sensitive data encrypted with customer-managed keys whose use is limited to named identities and services? Key policy is a second, separate lock, so access to a data store alone does not give readable data.
Start the assessment ยท All 40 questions
Why it matters
Key policy is a second, separate lock, so access to a data store alone does not give readable data.
Answers and what each is worth
| Answer | Value |
|---|---|
| Yes, for sensitive data | 1 |
| For some data | 0.5 |
| No or not known | 0 |
How to check it in each cloud
- AWS
- List KMS keys and check key policies and grants for kms:Decrypt by principals, and that sensitive S3, EBS and RDS resources use customer-managed keys.
- Azure
- Check Key Vault or Managed HSM access policy or RBAC assignments and that sensitive storage uses customer-managed keys with purge protection.
- Google Cloud
- Check Cloud KMS key IAM bindings for roles/cloudkms.cryptoKeyDecrypter and that sensitive buckets and datasets use CMEK.
The fix
Move sensitive data stores to customer-managed keys and restrict key use to the services and roles that need it. Effort: medium.
Where it comes from
- Microsoft cloud security benchmark DP-5: Use customer-managed key option in data at rest encryption when required
- NIST SP 800-53 Rev. 5 SC-12: source
Related pages
Sources
- Microsoft cloud security benchmark DP-5, read 16 Nov 2026
- NIST SP 800-53 Rev. 5 SC-12, read 16 Nov 2026
Last reviewed 16 Nov 2026.