Keep the encryption keys for agent data under your control and limit who can use them
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
Check 11 of 30: Keep the encryption keys for agent data under your control and limit who can use them. If the agent's role can use a key, it can read whatever that key protects. Customer-managed keys let you cut off access by changing the key policy or disabling the key.
The whole checklist ยท The map
Why it matters
If the agent's role can use a key, it can read whatever that key protects. Customer-managed keys let you cut off access by changing the key policy or disabling the key.
How, in each cloud
- AWS
- Use a KMS key policy, which AWS calls the primary way to control access to a KMS key.
- Google Cloud
- Use Cloud KMS customer-managed encryption keys (CMEK) and grant key access only to the identities that need it.
- Azure
- Use customer-managed keys for Azure Storage held in an Azure key store.
What the documentation says
- "A key policy is a resource policy for an AWS KMS key. Key policies are the primary way to" (source)
- "customer-managed encryption keys (CMEK). Using Cloud KMS CMEK gives you" (source)
- "You can use your own encryption key to protect the data in your storage account." (source)
- Previous: Grant roles at the narrowest scope that works
- Next: Block public access on storage the agent can write to
Related pages
- Block public access on storage the agent can write to: the check, and how in AWS, Google Cloud and Azure
- Put data stores the agent reads inside a perimeter that blocks copying data out: the check, and how in AWS, Google Cloud and Azure
- Limit data access with tags, attributes or conditions, not only resource lists: the check, and how in AWS, Google Cloud and Azure
Sources
- docs.aws.amazon.com/kms/latest/developerguide/key-policies.html, read 10 Nov 2026
- cloud.google.com/kms/docs/cmek, read 10 Nov 2026
- learn.microsoft.com/en-us/azure/storage/common/customer-managed-keys-overview, read 10 Nov 2026
Last reviewed 16 Nov 2026.