Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Envelope encryption encrypts data with a local data key, then encrypts that data key with a master key held in a key management service. It is how every major cloud platform encrypts at scale.

What Is Envelope Encryption?
Suppose every file your application stores must be encrypted with a key held in a hardware-backed key management service. Sending each file to that service is impossible: the request size is capped at a few kilobytes, the latency is milliseconds per call, and the throughput quota will stop you long before your users do. Envelope encryption solves the problem by encrypting the data locally and sending only the key to be protected.
The pattern is two layers. A data encryption key (DEK), generated per object, per record, or per tenant, encrypts the actual data with AES-GCM. A key encryption key (KEK), which never leaves the key management service or hardware security module, encrypts the DEK. The encrypted DEK travels with the ciphertext, which is where the envelope metaphor comes from.
Only the second step touches the data, and only small values cross the network. AWS KMS, Azure Key Vault, Google Cloud KMS, HashiCorp Vault, and Kubernetes secret encryption with a KMS provider all implement this shape, as do S3 server-side encryption, EBS volume encryption, and BigQuery column encryption beneath the surface.
Teams frequently claim annual key rotation when what rotates is the KEK alone. Re-wrapping a DEK under a new master key changes nothing about the key that actually protects the data, and an attacker who captured a DEK still holds it. Both layers need a policy:
| Layer | Typical rotation | Effect |
|---|---|---|
| KEK | Annually, or automatically by the service | Limits exposure of the wrapping key; cheap |
| DEK | Per object, or on re-encryption | Limits what any single key protects; requires rewriting data |
Generating a fresh DEK for every object makes the second row free, because no key is ever reused. That is the configuration to aim for, and it is also what keeps AES-GCM nonce limits comfortably out of reach.
The cryptography is handled by the platform; the failures are architectural.
Decrypt on the master key, the encryption protects you from the storage layer and from nobody else. Key policies, not just IAM roles, are the control that matters.That last point has a positive use. Destroying a tenant’s KEK renders every object encrypted under it unrecoverable, which is a defensible way to satisfy a deletion request across backups and replicas without hunting down every copy. We review key hierarchies, policies, and rotation claims as part of our cloud security services, where the gap between the documented design and the deployed key policy is usually the finding.
Key management services cap request payloads at around 4 KB and charge per call, so encrypting objects directly is impossible for files and ruinously slow for high volumes. Envelope encryption keeps the bulk work local and asks the service only to protect a 32-byte key, which is what it is designed to do well.
No, they answer different questions. Envelope encryption describes the two-layer key structure. Bring your own key describes who generates and controls the master key: you import it rather than letting the provider create it. The two are usually combined, with an imported or customer-managed KEK sitting at the top of the envelope hierarchy.
As few as practical. Generating a DEK per object gives the smallest blast radius and avoids nonce reuse concerns entirely. Where that is too costly, scope keys per tenant, per table, or per time window, and record the key identifier in the ciphertext header so you can re-encrypt selectively later.
Reads fail, because the wrapped data key cannot be unwrapped. Treat the key service as a tier-one dependency: use multi-region or replicated keys, understand the provider’s availability commitments, cache unwrapped keys for a short, defined period where the risk allows, and test the failure mode before a regional incident tests it for you.
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.