Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A cloud key management service creates, stores, and controls cryptographic keys inside hardware security modules, so encryption and decryption happen without the key ever leaving.

What Is a Cloud Key Management Service?
A cloud key management service is a managed store for cryptographic keys, backed by hardware security modules, in which the key material never leaves the boundary. Applications do not fetch a key; they send data or a wrapped key to the service and ask it to perform an operation. Every call is authenticated, authorised against a key policy, and written to the audit log. AWS KMS, Azure Key Vault and Managed HSM, and Google Cloud KMS all follow this model.
Sending gigabytes through a key management API would be slow and expensive, so cloud services use envelope encryption instead. A data encryption key is generated locally and used to encrypt the data. That data key is then encrypted—wrapped—by a key encryption key held in the key management service, and the wrapped version is stored alongside the ciphertext. To read the data, the service unwraps the data key, which is the only operation that touches the managed key.
This is why enabling encryption on a storage bucket or database is nearly free in performance terms, and why key rotation does not require re-encrypting your data: rotating the key encryption key changes how new data keys are wrapped, while existing ciphertext remains readable through the retained previous version.
| Model | What it means |
|---|---|
| Provider-managed | The provider creates and rotates the key. No configuration, no visibility, no separate audit trail. |
| Customer-managed | You create the key, set its policy, choose rotation, and can disable or schedule deletion. Operations appear in your audit log. |
| Bring your own key | Key material is generated by you and imported into the service under a wrapping key. |
| External key store | The key stays in an HSM you operate outside the cloud; the provider calls out to it for every operation. |
| Dedicated HSM | Single-tenant hardware, typically validated to FIPS 140-3, under your exclusive control. |
Each step down this list increases control and increases the chance that you will take your own service offline. An external key store means every read depends on a network path and an HSM you maintain; the resilience design has to match the availability the business expects. Choose customer-managed keys where you need separation of duties, cryptographic deletion, or evidence for an auditor, and resist the temptation to apply the strictest model to everything.
Encryption only separates duties if the people who can read the data cannot also use the key. A key policy that grants Decrypt to a broad administrative role has achieved compliance wording without achieving protection. Write the policy so that the key’s administrators and its users are different principals, require the calls to come from expected roles and network paths with condition keys, and remember that in AWS the key policy is evaluated independently of identity policies, which is covered in our entry on IAM policy evaluation.
Deletion deserves particular care. Scheduling a key for deletion makes every object encrypted under it permanently unreadable once the waiting period elapses. That is a powerful control for data disposal and a catastrophic accident otherwise. Use the longest waiting period you can tolerate, alert on deletion scheduling, and protect the action with a guardrail.
Encryption at rest defeats someone who obtains the storage media or the raw object without the right to use the key. It does nothing against an application with legitimate access, a compromised identity that can call the key service, or an over-permissive bucket policy, because in each case the platform decrypts the data on request exactly as designed. Most cloud data breaches are access-control failures, not cryptographic ones. Treat the key management service as the mechanism that makes separation of duties and cryptographic deletion possible, and spend your effort on who may call it.
At Privia Security, we review key management design and the access paths around it through our cloud security services.
Not by themselves. With a standard customer-managed key, the provider still operates the hardware security module and performs the cryptographic operation, so the protection is contractual and operational rather than absolute. An external key store, where the key never leaves hardware you control, comes closer, at the cost of availability risk. Confidential computing addresses a different part of the same concern.
Annual automatic rotation is the common baseline and satisfies most frameworks, including PCI DSS expectations when combined with documented key management procedures. Rotate immediately if you suspect exposure, if an administrator with key access leaves under difficult circumstances, or if a contractual obligation requires it. Keep previous versions enabled, because existing ciphertext still needs them.
Every object encrypted under it becomes permanently unrecoverable once the mandatory waiting period expires. Providers enforce a waiting window, typically between seven and thirty days, during which deletion can be cancelled. Use the longest window you can accept, alert on any scheduled deletion, and restrict the permission with an organisation-level guardrail so that a single mistaken API call cannot be made.
It is justified where a regulator, scheme, or contract requires single-tenant, validated hardware under your exclusive control, or where you are a certificate authority or payment processor handling root key material. For most workloads, a customer-managed key in the shared service already provides separation of duties, auditability, and cryptographic deletion at a fraction of the cost and operational burden.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.