Client-Side Encrypted Cloud Storage With Hierarchical Key Recovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud storage systems lack robust client-side encryption solutions that provide complete privacy and security for user data, with usability issues preventing widespread adoption, and there is a need for secure management of encryption keys.

Innovation Solution

A system and method for secure cloud storage and retrieval of client-side encrypted data using a hierarchical encryption structure, out-of-band key exchange, and trusted party relationships to manage encryption keys, ensuring user data is never exposed to the service provider.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data-at-rest encryption is implemented to protect stored data, then security against storage location attacks is improved, but data accessibility by the server is worsened

Engineering Contradiction:
ImprovesecurityVSAvoiddata accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The encryption key is segmented into multiple parts and distributed to different trusted parties. No single party holds the complete key, preventing any one entity from accessing all encrypted data while still allowing authorized access when key parts are combined.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Trusted parties act as intermediaries between the user and the encrypted data. They hold portions of the decryption key and can facilitate data access without the server having direct key access, thereby maintaining both security and accessibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the service provider keeps encryption keys to decrypt user data, then account recovery and data accessibility are improved, but user privacy and security are worsened

Engineering Contradiction:
Improveaccount recoveryVSAvoiduser privacy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The decryption key is divided into multiple parts held by different trusted parties. The service provider cannot unilaterally decrypt user data, as they do not possess the complete key. This segmentation ensures user privacy while still enabling recovery through coordinated action of trusted parties.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Trusted parties are pre-established and pre-configured with key segments before any data access or recovery scenario occurs. This preliminary setup enables both privacy protection and recovery capability without requiring the service provider to hold complete decryption authority.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If client-side encryption is implemented to provide complete privacy, then user privacy and security are improved, but usability and account recovery are worsened

Engineering Contradiction:
Improveuser privacyVSAvoidusability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Trusted parties serve as intermediaries that bridge the gap between complete client-side encryption and usability needs. They can assist with account recovery and data access without compromising the fundamental privacy guarantees of client-side encryption, as they require user authorization and cooperation.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Users pre-configure trusted parties and distribute key segments before needing recovery assistance. This preliminary action maintains encryption security while establishing a recovery mechanism that preserves both privacy and usability when needed.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If encryption keys are protected and distributed to trusted parties, then security against server compromise is improved, but key management complexity is worsened

Engineering Contradiction:
ImprovesecurityVSAvoidkey management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The encryption key is segmented into parts and distributed to trusted parties, which simplifies the security model by ensuring no single point of failure. While distribution adds complexity, the segmented approach prevents catastrophic security failures from key compromise.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The trusted parties serve multiple functions: they hold key segments for security, can facilitate data recovery, and act as authorization intermediaries. This multi-functionality reduces the need for separate systems for key management, recovery, and access control.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12470378B2Secure cloud storage and retrieval of client-side encrypted files
Publication Date: 2025.11.11 KEYCRYPT LABS PTY LTD
  • US12470378B2 patent drawing
  • US12470378B2 patent drawing
  • US12470378B2 patent drawing

AI summary

A system and method for secure cloud storage of client-side encrypted data using a hierarchical encryption structure and a hierarchical storage structure to provide hierarchical key management and hierarchical data access.