Immutable Logging for Distributed File Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional databases and blockchain systems face challenges in securely storing and accessing large data sets, particularly in distributed environments, as they often lack adequate protection against internal threats and tampering, and are not well-suited for low-latency operations or large binary object storage.
Innovation Solution
The implementation of a tamper-evident, immutable data structure using Merkle Trees and directed acyclic graphs (DAGs) within a blockchain software suite, such as Docuchain, which allows for low-latency read and write operations by storing data directly in the Merkle Trees and using cryptographic hash pointers to ensure data integrity and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional databases are used to store data in distributed file systems, then data storage and access operations can be performed, but the security and integrity of the data cannot be trusted as attackers can modify or exfiltrate records and delete access logs
Solution Approach 1:
The patent replaces traditional mechanical logging systems with cryptographic hash-based immutable logging. Instead of relying on conventional database logs that can be deleted or modified, the system uses cryptographic hash chains where each log entry is linked to previous entries through hash functions, making tampering computationally infeasible and providing mathematical guarantees of data integrity
Solution Approach 2:
The patent creates a composite security architecture by combining distributed file system operations with blockchain technology. The hybrid system integrates traditional file access mechanisms with immutable ledger recording, creating a composite structure that maintains operational efficiency while adding cryptographic security layers to prevent tampering and ensure integrity
2Productivity
If access logs are stored in traditional datastores, then logging operations can be performed, but the logs can be deleted or tampered with by attackers to mask their activity
Solution Approach 1:
The patent replaces traditional mutable logging mechanisms with immutable cryptographic logging. Each log entry contains a cryptographic hash of previous entries, creating an immutable chain that cannot be altered without detection. This substitution ensures that audit trails remain intact and tamper-evident while maintaining logging functionality
Solution Approach 2:
The patent introduces cryptographic hash functions as intermediaries between log entries. Instead of directly storing log data in mutable structures, the system uses hash functions to create cryptographic links between entries, serving as an intermediary layer that guarantees integrity and prevents unauthorized modification of the audit trail
3Adaptability or versatility
If data is distributed across multiple computing entities, then system scalability and availability are improved, but security against internal threats and tampering becomes more difficult to ensure
Solution Approach 1:
The patent segments data into fragments that are distributed across multiple computing entities, with each fragment stored in an immutable data structure. This segmentation allows the system to maintain scalability and availability while ensuring that no single entity holds complete control over the data, thereby reducing internal threat risks and enabling cryptographic verification of data integrity across the distributed system
Data Source
AI summary
Provided is a process including: receiving a request to access a distributed data store, wherein the distributed data store stores a plurality of units of content that are each distributed among multiple computing entities hosting different subsets of data of the distributed data store; and causing, with one or more processors of a computing device configured to participate in combining the information from the plurality of computing entities to access units of content, logging of the request in an entry in a tamper-evident log.