Cryptographic Signatures for Authentic File Version Retrieval
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud data storage systems face challenges in identifying authentic file versions, especially when immutable and versioned storage is used, as malicious attackers can create new versions, making it difficult to determine legitimate from corrupted files.
Innovation Solution
Generating and utilizing user metadata with cryptographic signatures based on file identifiers, timestamps, and cryptographic keys associated with archival locations to authenticate and filter out malicious versions during data retrieval.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If immutable and versioned storage is used in cloud data storage systems, then data durability and reliability are improved, but the ability to identify authentic file versions deteriorates because malicious attackers can create new versions
Solution Approach 1:
The system performs preliminary actions by generating and storing cryptographic signatures along with file metadata at the time of upload. These signatures are created before any potential malicious modifications can occur, establishing a baseline of authenticity that can be verified later when retrieving file versions.
Solution Approach 2:
Cryptographic signatures serve as an intermediary mechanism between the file content and the authentication process. Instead of directly analyzing file content to determine authenticity, the system uses these intermediary signatures as trusted references to verify whether a file version is legitimate or malicious.
2Ease of repair
If multiple versions of files are stored in cloud storage, then data recovery capability is improved, but the complexity of determining which version is legitimate increases
Solution Approach 1:
The system creates cryptographic copies of file metadata including signatures, timestamps, and identifiers for each version. These copies are stored alongside the actual file versions, enabling the system to replicate and compare version information without manipulating the original files, thus simplifying the identification process.
Solution Approach 2:
The system changes the 'color' or state of version identification by introducing cryptographic signatures as a new attribute. This transforms the version identification process from analyzing file content differences to verifying cryptographic authenticity, making it easier to distinguish legitimate versions from malicious ones.
3Reliability
If cryptographic signatures are added to authenticate file versions, then data integrity is improved, but the complexity of the data storage system increases
Solution Approach 1:
The cryptographic signature system serves multiple functions simultaneously: it authenticates file versions, provides non-repudiation proof, enables version comparison, and detects modifications. By making the signature mechanism multi-functional, the system achieves enhanced data integrity without proportionally increasing complexity.
Data Source
AI summary
A second data source may retrieve metadata for one or more versions of a set of versions of a file stored at the first data source. In some examples, the metadata for the one or more versions of the file may include at least an identifier of the file, a timestamp, and a cryptographic signature. In some examples, generation of the cryptographic signature may be based on the identifier of the file, the timestamp, and a cryptographic key. The second data source may identify a set of versions of the file that were uploaded from a trusted data source to the first data source based on a comparison of the cryptographic signature to a computed cryptographic signature. The second data source may then determine a targeted version of the file and retrieve the targeted version of the file from the first data source.