Cloud Data Encryption Key Segmentation for Scalable Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud storage solutions face security challenges, particularly in ensuring the confidentiality and scalability of data sharing among multiple users, as they often rely on inadequate authentication methods and are vulnerable to data breaches, with existing encryption methods being resource-intensive and not scalable for large data exchanges.

Innovation Solution

A method and system for secure sharing of encrypted information in a cloud system, where data is encrypted only once and each user accesses a shared folder using individual encrypted key material, with a device providing secure communication and visual content protection by blurring content when not in use or if an unknown face is detected, utilizing public-key encryption and a hierarchical key management system to prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is encrypted for each user individually using traditional methods, then security and confidentiality are improved, but processing time and computational resources increase significantly

Engineering Contradiction:
Improvedata confidentialityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The encryption system is segmented into hierarchical key levels (master keys, data encryption keys, and user-specific keys). Each level handles specific encryption tasks independently, allowing parallel processing and reducing overall computation time while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Master keys and data encryption keys are generated and stored in advance before actual data sharing occurs. This preliminary key preparation eliminates the need for time-consuming key generation during data access, significantly reducing processing time while maintaining strong encryption.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If encryption keys are managed centrally for multiple users, then ease of operation is improved, but security vulnerabilities increase

Engineering Contradiction:
Improvekey managementVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

Key management is segmented into distributed hierarchical levels rather than centralized control. Each user has their own key pair, and encryption keys are distributed selectively to authorized users only. This segmentation maintains ease of operation through automated distribution while enhancing security by eliminating single points of failure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces cryptographic intermediaries (digital signatures, key encryption keys) that mediate between central key generation and distributed user access. These intermediaries enable automated key management while preventing unauthorized access, as each layer provides cryptographic proof of authorization without exposing master keys.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If cloud service providers have access to decryption keys for service functionality, then ease of operation is improved, but data privacy is compromised

Engineering Contradiction:
Improveservice functionalityVSAvoiddata privacy
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The critical decryption capability is extracted from the cloud service provider and held exclusively by end users through their private keys. The provider only handles encrypted data and key distribution, never possessing master decryption keys. This extraction maintains service functionality while ensuring users retain full control over their data privacy.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

Cryptographic key encryption keys serve as intermediaries between the cloud service provider and user data. The provider can encrypt data with these intermediate keys without having access to the final decryption capability, which remains with users. This intermediary layer enables service functionality while preserving user privacy control.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If encryption is applied to large amounts of data for sharing, then security is improved, but processing power and resource consumption increase

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing power
Core Design Contradiction:
ReliabilityVSPower

Solution Approach 1:

Encryption is segmented into multiple passes using different key levels. Data is first encrypted with data encryption keys, then wrapped with key encryption keys, and finally protected by user-specific keys. This segmentation allows distributed processing across multiple systems and reduces the computational burden on any single processor while maintaining comprehensive security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes encryption parameters dynamically based on data size and user requirements. For large data sets, it uses symmetric encryption with pre-shared keys for efficient bulk encryption, then applies asymmetric encryption only to the smaller key material. This parameter adjustment significantly reduces processing power requirements while maintaining security for large-scale data sharing.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10805071B2Method and system for protecting and sharing digital data between users in a network
Publication Date: 2020.10.13 INVENIA
  • US10805071B2 patent drawing
  • US10805071B2 patent drawing
  • US10805071B2 patent drawing

AI summary

Scalable method and system for secure sharing of encrypted information in a cloud system, the encrypted information being encrypted only once, and each user joining and accessing a shared folder by individual encrypted key material transferred.