Cloud-Managed vs Customer-Managed Encryption Keys
You'll learn how different key management models in cloud encryption shift control and responsibility between you and your cloud provider.
The Three Key Management Models
When encrypting data at rest in the cloud, you choose who manages the encryption keys:
Cloud-Managed Keys (CMK)
The provider handles everything: key generation, storage, rotation, and access control. You simply enable encryption with a checkbox. Think of this like letting the bank keep your valuables in their vault with their lock—convenient, but you trust them completely.
Example: AWS default S3 encryption (SSE-S3), Azure Storage Service Encryption.
Customer-Managed Keys (CMK)
You control the key lifecycle through the provider's key management service (like AWS KMS, Azure Key Vault, or GCP KMS). You create, rotate, and delete keys, set access policies, and audit usage—but the service stores the key material in their HSMs.
Analogy: You own the lock and key, but store them in the provider's secure facility. You control who can use your key.
Customer-Provided Keys (CPK)
You generate keys externally and provide them for each encryption operation. The provider never stores your key material—maximum control, maximum operational burden.
Security Tradeoffs
| Model | Control | Operational Burden | Compliance | Risk |
|---|---|---|---|---|
| Cloud-Managed | Low | Minimal | Limited | Provider compromise |
| Customer-Managed | Medium | Moderate | Better | Misconfiguration, key loss |
| Customer-Provided | High | High | Best | Key management complexity |
Customer-managed keys give you audit trails, separate key and data breach requirements (attacker needs both), and satisfy compliance mandates requiring key control. The tradeoff? You can lock yourself out permanently if you delete a key.
Key Takeaway: Cloud-managed keys offer convenience; customer-managed keys provide control and compliance benefits; customer-provided keys maximize security isolation but demand rigorous operational discipline—choose based on your threat model and regulatory requirements.