Cloud Key Multi-Custody Using Secure Enclave Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based services face challenges in maintaining multi-custody control of cryptographic keys due to the potential for account root authorities to circumvent the multiple participant nature and enhanced security of traditional multi-custody key management paradigms, especially when using hierarchical cloud-service architectures.

Innovation Solution

Implement secure enclaves and trusted execution environments (TEEs) within cloud-based services to manage cryptographic keys, binding application keys to enclave signing keys and restricting access to a quorum of key custodians, ensuring that multi-custody control is maintained even in the cloud environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If cloud-based services use hierarchical account root authorities for key management, then service accessibility and ease of operation are improved, but multi-custody control security is weakened

Engineering Contradiction:
Improveservice accessibilityVSAvoidmulti-custody control security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the account root authority into multiple independent custodian keys (first custodian key, second custodian key, third custodian key). Each key is managed separately by different custodians, eliminating the single point of failure. The key management service can access and use keys only when the required number of custodians are present, implementing multi-custody control while maintaining service accessibility.

Inventive Principle:
Principle #1Segmentation

2Reliability

If physical HSMs with tokens are used for multi-custody control, then key security is improved, but device complexity and operational friction increase

Engineering Contradiction:
Improvekey securityVSAvoidphysical security infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces physical HSMs and mechanical token-based systems with a cloud-based key management service that uses cryptographic key pairs. The physical tokens and secure storage infrastructure are substituted with digital key pairs that can be accessed through the cloud service. The key management service maintains multi-custody control by requiring multiple custodians to provide keys for decryption, eliminating the need for physical security infrastructure while maintaining key security.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If account root authority can modify key policies, then operational flexibility is improved, but multi-custody control is circumvented

Engineering Contradiction:
Improveoperational flexibilityVSAvoidmulti-custody control integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary anti-action by configuring the key management service to prevent account root authority from modifying policies associated with custodian keys. The service is pre-configured with the constraint that only the specified number of custodians can modify their respective key policies. This preliminary protective measure ensures that even if account root authority attempts to circumvent multi-custody control, the system prevents such actions before they can succeed, maintaining both operational flexibility within constraints and multi-custody control integrity.

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS20250365144A1Systems and Methods for Implementing Multi-Custody Control of Cryptographic Keys Using Cloud-Based Services
Publication Date: 2025.11.27 INTERTRUST TECH CORP
  • US20250365144A1 patent drawing
  • US20250365144A1 patent drawing
  • US20250365144A1 patent drawing

AI summary

Embodiments of the disclosed systems and methods facilitating multi-party control of protected cryptographic keys in cloud-based service architectures. Consistent with embodiments disclosed herein, secure enclaves associated with cloud service virtual machines may be leveraged in a manner such that multi-custody control of protected keys may be implemented, while cloud-service account root authority access to these keys may be restricted. In certain embodiments, policy managed by a key management system may persistently bind an application key to an enclave signing key, which may be placed under multi-custody control. With the application key being securely bound to the enclave signing key within enforced policy, the application kay may be effectively placed under multi-custody control within the cloud-based service.