Hold Your Own Key (HYOK)

The defining characteristic of HYOK is that the cryptographic key is generated, stored, and used exclusively within the customer's on-premises Hardware Security Module (HSM) or a sovereign-controlled enclave. Unlike CMK, where a key might be wrapped and exported to a cloud HSM, HYOK ensures the plaintext key never crosses the trust boundary. All cryptographic operations occur locally, with only the resulting ciphertext being sent to the cloud. This guarantees that the cloud provider has zero technical ability to decrypt the data, satisfying the strictest data sovereignty mandates.

HYOK architectures often leverage proxy re-encryption to enable secure collaboration without exposing the master key. The workflow is:

• A document is encrypted with a symmetric Data Encryption Key (DEK).
• The DEK is wrapped by the customer's local HSM using the master HYOK key.
• To share the document, the local HSM transforms the ciphertext so it can be decrypted by a different recipient's key, without ever decrypting the DEK in transit. This allows the cloud to store and distribute data while remaining cryptographically blind to its contents.

It is critical to differentiate HYOK from related key management models:

• BYOK (Bring Your Own Key): The customer generates a key and imports a copy into the cloud provider's HSM. The provider now has a copy of the key material.
• CMK (Customer-Managed Key): The key is generated inside the cloud provider's HSM, but the customer controls its lifecycle and access policies. The provider's infrastructure still hosts the plaintext key.
• HYOK (Hold Your Own Key): The key is generated and used exclusively outside the provider's domain. The provider never possesses the key material at any point.

The security of a HYOK architecture is entirely dependent on the integrity of the local Hardware Security Module (HSM). This device acts as the hardware root of trust, providing:

• Tamper-resistant key storage: Physical mechanisms that zeroize keys upon intrusion detection.
• FIPS 140-2 Level 3 validation: A mandatory certification for HSMs used in regulated industries.
• Secure execution environment: Cryptographic operations are performed inside the HSM's secure boundary, isolating them from the general-purpose operating system. Without a certified HSM, the HYOK model collapses into a less secure software-based key storage pattern.

HYOK introduces architectural friction that must be addressed:

• Latency Overhead: Every encryption or decryption operation requires a network round-trip to the on-premises HSM, adding latency compared to cloud-native key services.
• Throughput Bottlenecks: On-premises HSMs have finite cryptographic operations per second, requiring careful capacity planning for high-volume data pipelines.
• Availability Risk: If the local HSM cluster becomes unavailable, all cryptographic operations halt. This necessitates a high-availability HSM deployment with redundant devices and secure synchronization protocols.
• Key Ceremony Complexity: Initializing and backing up HSMs requires multi-person integrity ceremonies, increasing operational overhead.

HYOK is the definitive technical control for satisfying the most stringent data sovereignty regulations:

• Schrems II / EU-US Data Privacy Framework: By ensuring the cloud provider cannot access plaintext data, HYOK functions as a supplementary technical measure that mitigates risks from foreign surveillance laws.
• ITAR / EAR: For defense articles and dual-use technologies, HYOK ensures that cryptographic access remains exclusively with authorized U.S. persons.
• Cloud Act Resistance: Since the provider lacks the key, any legal order to produce data yields only ciphertext, preserving the customer's data sovereignty.

A top-level cryptographic key used exclusively to encrypt and wrap other keys (Data Encryption Keys or DEKs). In a HYOK architecture, the KEK remains in the customer's HSM and is used to wrap DEKs that are then sent to the cloud provider for bulk data operations.

• Envelope encryption is the standard pattern
• KEK never leaves the HSM boundary
• DEKs can be rotated frequently without touching the KEK
• Decouples key management from data processing scale