Hold Your Own Key (HYOK)

A cryptographic architecture where the data owner generates and controls the key material using a dedicated Key Management Service (KMS). Unlike HYOK, the key typically resides within the cloud provider's boundary but in a tenant-isolated vault, preventing the provider from using the key without explicit authorization. This creates a logical separation of duties where the provider manages the lock but the customer holds the key.

A hardware-enforced security model that protects data in use by performing computation within a Trusted Execution Environment (TEE). This isolates sensitive workloads from the host OS, hypervisor, and cloud operators. When combined with HYOK, it ensures that even during active processing, the decrypted data is never exposed to the underlying infrastructure, closing the final gap in the data lifecycle protection.

The explicit geographic or jurisdictional location where data is stored at rest. Enforcing residency requires binding constraints that prevent data replication or backup to unauthorized regions. HYOK complements residency by ensuring that if a foreign entity physically seizes a hard drive, the data remains cryptographically inaccessible without the on-premise master key, rendering the seizure useless.

The legal framework resulting from the 2020 Court of Justice of the European Union ruling that invalidated the EU-US Privacy Shield. It requires Transfer Impact Assessments (TIAs) and supplementary measures for international data transfers. HYOK serves as a robust supplementary measure by ensuring that even if a US cloud provider receives a FISA 702 request, they lack the cryptographic material to decrypt the EU citizen's data.

A dedicated, tamper-resistant physical appliance or cloud service that generates, stores, and manages digital keys. In a HYOK architecture, the enterprise's on-premise HSM acts as the root of trust. It securely performs cryptographic operations without ever exporting the private key material, ensuring that the master key never exists in software or memory outside the hardened physical boundary.

A security model that assumes no implicit trust based on network location. Access to data requires continuous verification of identity, device posture, and context. Applying zero-trust principles to HYOK means that even internal services cannot access key material by default. Every decryption request is authenticated, authorized, and logged, preventing lateral movement by attackers who have breached the perimeter.