Key Hierarchy and Root of Trust
What You'll Learn
You'll learn how cloud KMS systems use hierarchical key structures with hardware security modules (HSMs) as the foundation to establish a secure chain of trust for protecting your data.
The Key Hierarchy
Cloud KMS doesn't just use a single key to encrypt everything—that would be a security nightmare. Instead, it uses a multi-tier hierarchy where keys protect other keys, creating layers of security.
Think of it like a safety deposit box: you need a key to open the box, but that key itself is stored in a master vault that requires a separate, more secure mechanism to access.
The Hierarchy Levels
-
Root Key (Hardware Security Module): Lives in tamper-resistant HSM hardware. This is the "root of trust"—the foundational key that never leaves the HSM and is used to protect other keys.
-
Key Encryption Keys (KEK): Protected by the root key. These keys encrypt your Data Encryption Keys.
-
Data Encryption Keys (DEK): Protected by KEKs. These keys actually encrypt your application data.
Why This Matters
The root of trust is critical: if the root key is compromised, everything below it falls. HSMs provide:
- Physical tamper protection that destroys keys if attacked
- FIPS 140-2 Level 3 or higher certification
- Cryptographic isolation from the operating system
When you use KMS, you're creating encrypted DEKs that only your KEK can decrypt, and that KEK is only decryptable by the HSM's root key. Even cloud providers with access to servers can't decrypt your data without compromising HSM hardware.
Key Takeaway: KMS uses a hierarchical key structure rooted in hardware security modules (HSMs), ensuring that even if higher-level keys are exposed, the root of trust remains secure in tamper-resistant hardware.