Tamper-Evident Event Logging via Position-Lock Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional event logging systems are vulnerable to tampering, deletion, and reorganization, and are computationally intensive, requiring distributed consensus and significant resources, which delays authentication and logging processes.
Innovation Solution
A system comprising a logging device and a triggering device, where the triggering device creates an append request for a new event, including a position-lock data and signature, which is verified by the logging device to create a secure and tamper-evident logged event, stored in chronological order without needing consensus from multiple computing terminals.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional event logging systems are used to securely record events, then data integrity and security are improved, but computational resource usage increases significantly and processing speed decreases
Solution Approach 1:
The patent extracts the consensus mechanism from the logging system, separating the security function (cryptographic hashing and signing) from the distributed validation function. This allows the logging device to operate independently without requiring multiple computing terminals to confirm each transaction, thereby improving processing speed while maintaining data integrity through cryptographic methods.
Solution Approach 2:
The system segments the logging process into distinct cryptographic operations: creating position-lock data based on previous event hashes, generating digital signatures, and appending signed events to the chain. This segmentation allows each operation to be optimized independently, improving overall processing efficiency while maintaining security.
2Reliability
If distributed consensus mechanisms are implemented for secure event logging, then tamper resistance is improved, but device complexity and resource requirements worsen
Solution Approach 1:
The logging device performs self-validation through cryptographic hashing and digital signatures without requiring external validation from other nodes. Each event contains a hash of the previous event, creating a self-referential chain that automatically provides tamper resistance. This eliminates the need for complex distributed consensus infrastructure while maintaining security.
Solution Approach 2:
The system performs preliminary cryptographic hashing to create position-lock data before appending new events. This preliminary action locks the position and integrity of previous events in the chain, providing tamper resistance in advance rather than requiring post-hoc validation from multiple terminals, thereby simplifying the system architecture.
3Stability of the object's composition
If blockchain-based secure logging is implemented, then event sequence integrity is improved, but time consumption for authentication increases
Solution Approach 1:
The patent replaces the mechanical distributed consensus process with cryptographic verification. Instead of requiring multiple terminals to sequentially validate and propagate transactions, the system uses digital signatures and hash chains that can be verified independently and instantaneously, dramatically reducing authentication time while maintaining event sequence integrity.
Solution Approach 2:
Digital signatures are generated and attached to events before they are appended to the chain. This preliminary signing action allows receiving systems to immediately verify event authenticity and sequence integrity without requiring time-consuming consensus processes, as the cryptographic proof is already embedded in the event data.
Data Source
AI summary
A system for secured logging of a second event. The system includes a logging device and a triggering device The triggering device receives an input related to the second event, creates second event message based on received input related to the second event, and receives the first set of data related to first logged event from the logging device. The triggering device further creates a first position-lock data from the first set of data, creates a second append request, and provides the second append request to the logging device. The logging device is configured to verify the second append request. Based on positive verification, the logging device creates a logging device signature over a second log-append-approval, and combines the created logging device signature with the provided second append request to form a second logged event.