Least privilege for Cloud KMS means a key-level role such as cryptoKeyEncrypterDecrypter, never Owner
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Cloud KMS binds roles at project, key ring and key level. Google's documentation, read 16 Nov 2026, says to grant the most limited permissions to the lowest object in the hierarchy, and that only Owner or Cloud KMS Admin can grant or revoke access to Cloud KMS resources.
Open the calculator ยท All services
Cloud KMS roles inherit down from project to key ring to key
Google's documentation says policy bindings can be set on the project, key ring, key, import job and other Cloud KMS resources. A principal with a role at a higher level inherits it on child resources, so an owner on a project is an owner on all key rings and keys in it.
The inverse does not hold: a permission on a key gives nothing on its key ring. Google notes that a user with permissions only on a key ring or key cannot manage key resources in the console without also holding a browser role on the project.
Google also publishes a separation of duties page, which pairs with the role list below.
The identities that call this service (people, services, workloads, third parties) are covered in the Google Cloud service identities guide and the workload identities guide.
Roles to avoid, with the documented reason
Administration and use of a key should not be held by the same identity.
- Owner (roles/owner) on a project: Google says it makes the holder an owner on every key ring and key in the project.
- Cloud KMS Admin (roles/cloudkms.admin): Google's guidance is to grant it on the key to manage that key. Google says only principals with Owner or this role can grant or revoke access to Cloud KMS resources.
- cryptoKeyEncrypterDecrypter where encryption alone is enough: choose the encrypter role if the principal never decrypts.
- Key-ring or project scope for a single workload: it widens the grant to every key in the ring or project.
Minimal bindings by task
Google's least privilege section maps tasks to roles on the key.
| Task | Role on the key |
|---|---|
| Encrypt but not decrypt | roles/cloudkms.cryptoKeyEncrypter |
| Encrypt and decrypt | roles/cloudkms.cryptoKeyEncrypterDecrypter |
| Verify but not sign | roles/cloudkms.publicKeyViewer |
| Sign and verify | roles/cloudkms.signerVerifier |
| Manage a key | roles/cloudkms.admin |
Hierarchy position is the narrowing control
Google's page says to practice least privilege by granting the most limited set of permissions to the lowest object in the resource hierarchy. For Cloud KMS the lowest object is usually the key itself, which means a policy per key rather than a policy per project.
Because a key ring grant covers every key in it, put keys with different users in different key rings. Pair this with the separation of duties page so the identity that administers keys is not the identity that uses them.
Checking what is used
The IAM recommender compares each principal's roles with the permissions it used in the last 90 days, per Google's documentation. Review the output for principals holding roles/cloudkms.admin or the encrypter and decrypter roles at project scope.
Then list the IAM policy of each key and key ring and remove principals that are no longer in the data path.
Google's IAM overview states that basic roles include thousands of permissions across all services, and a project-level Editor or Owner would carry key permissions with them. When reviewing Cloud KMS, therefore, list basic role holders on the project as well as the bindings on the keys. A key with a tight policy still inherits whatever the project policy grants above it, so the project policy is part of the key's access.
Related pages
Sources
- Cloud KMS access control with IAM, read 16 Nov 2026
- Role recommendations overview, read 16 Nov 2026
Last reviewed 16 Nov 2026.