Cloud Data Encryption via Synchronization Server Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Insecure cloud storage systems pose risks of unauthorized access and data tampering, compromising the confidentiality and integrity of data stored on untrusted remote storage mechanisms.
Innovation Solution
A system that encrypts data before uploading to cloud storage, uses a synchronization server to verify and sign commit records, and manages access through digital certificates and access control policies, ensuring secure data synchronization between clients and cloud storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is stored on untrusted remote storage mechanisms, then data accessibility and storage capacity are improved, but data confidentiality and integrity are compromised
Solution Approach 1:
The system performs preliminary encryption of data on the client device before uploading to cloud storage. This advance protective action ensures that data remains confidential even when stored on untrusted remote storage mechanisms, resolving the contradiction between accessibility and confidentiality.
Solution Approach 2:
The patent introduces cryptographic intermediaries including digital signatures, message authentication codes (MACs), and encryption keys that mediate between the client and cloud storage. These intermediaries verify data integrity and maintain confidentiality without preventing accessibility, thus resolving the contradiction.
2Quantity of substance
If data is transmitted to cloud storage, then storage capacity is improved, but data integrity is compromised due to potential tampering
Solution Approach 1:
The system implements feedback mechanisms through cryptographic verification. Message authentication codes (MACs) and digital signatures are generated for uploaded data and verified upon retrieval. This feedback loop detects any tampering during transmission or storage, maintaining data integrity while preserving storage capacity benefits.
Solution Approach 2:
The system performs preliminary cryptographic hashing and signature generation before data transmission. These preliminary integrity checks are embedded in the uploaded data structure, enabling automatic verification upon retrieval without compromising storage capacity or requiring additional physical security measures.
3Reliability
If encryption is applied to data before upload, then data confidentiality is improved, but computational overhead increases
Solution Approach 1:
The system applies partial encryption by encrypting only the data payload while leaving metadata and structural elements in plaintext. This selective approach maintains data confidentiality for the critical content while reducing computational overhead compared to full-system encryption, thus resolving the contradiction.
Solution Approach 2:
The client device performs self-service encryption using locally stored cryptographic keys before data transmission. This eliminates the need for server-side encryption infrastructure, reducing overall system computational overhead while maintaining strong confidentiality through client-side cryptographic processing.
4Reliability
If digital signatures and verification mechanisms are implemented, then data integrity is improved, but system complexity increases
Solution Approach 1:
The system implements multi-functional cryptographic primitives that simultaneously provide authentication, integrity verification, and data binding. A single message authentication code (MAC) structure performs multiple security functions, reducing the number of separate verification mechanisms needed and thereby lowering system complexity while maintaining strong integrity guarantees.
Data Source
AI summary
The disclosed embodiments provide a system that processes data. The system includes a first client that encrypts a first set of data, uploads the encrypted first set of data to a volume on a cloud storage system, and creates a commit record of the upload. The system also includes a synchronization server that verifies access to the volume by the first client and includes the commit record in a change set containing a set of commit records associated with the volume. The synchronization server also signs the change set and provides the change set for use in synchronizing the upload with a second client.


