Distributed Ledger Audit Chain for Hash-Based Traceability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing audit processes are resource-intensive and time-consuming, requiring organizations to produce detailed reports on system access, changes, and anomalies, which is inefficient and costly.
Innovation Solution
Implementing distributed ledger-based auditing systems that utilize trusted nodes to generate hashes of audit events, store them on scoped distributed ledgers, and verify the chain of custody using Merkle tree hashes, providing a secure and efficient method for tracking and verifying audit records.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional audit reporting processes are used, then comprehensive audit coverage is achieved, but resource consumption and time requirements increase significantly
Solution Approach 1:
The system performs preliminary actions by continuously capturing and hashing audit events as they occur, maintaining them in an immutable ledger before audits are requested. This eliminates the need for retroactive data collection and report generation, allowing auditors to access pre-prepared, verified audit trails immediately when needed.
Solution Approach 2:
The system creates cryptographic copies (hashes) of audit event data and stores them in an immutable distributed ledger. These cryptographic copies serve as verified replicas that can be independently audited without accessing the original systems, enabling comprehensive audit coverage while reducing the resource burden on production systems.
2Loss of information
If detailed audit reports are generated for every audit event, then complete traceability is achieved, but system performance and resource usage deteriorate
Solution Approach 1:
The system extracts only the essential audit event data (creating cryptographic hashes) and stores them in the distributed ledger, separating the verification-critical information from the full audit event details. This extraction approach maintains complete traceability through cryptographic verification while minimizing the processing burden on production systems.
Solution Approach 2:
The distributed ledger acts as an intermediary layer between production systems and audit systems. It receives and verifies audit events through cryptographic hashing, providing a lightweight verification mechanism that ensures traceability without requiring direct access to or heavy processing on production systems.
3Loss of time
If audit data is stored centrally for easy access, then retrieval speed improves, but data integrity and security verification become more difficult
Solution Approach 1:
The system segments audit verification into two parts: cryptographic hash verification (performed quickly on the distributed ledger) and detailed data validation (performed on-demand). This segmentation allows for rapid initial verification of data integrity through hash matching, with deeper validation available only when specifically needed.
Solution Approach 2:
The system replaces traditional mechanical verification methods (direct data comparison, access control checks) with cryptographic verification through hash functions. This substitution enables fast, automated verification of data integrity and authenticity without requiring complex access controls or manual verification processes.
4Reliability
If multiple audit systems are implemented across different departments, then comprehensive coverage is achieved, but system complexity increases
Solution Approach 1:
The distributed ledger provides a universal, standardized interface for capturing and verifying audit events from multiple different systems and departments. All audit events, regardless of source, are processed through the same cryptographic verification mechanism, eliminating the need for separate verification systems for each department while maintaining comprehensive coverage.
Data Source
AI summary
A trusted node in a distributed ledger audit system may identify first audit event data for a first audit event from a first computing resource on a messaging bus; generate a first hash of a subset of the first audit event data; write the first audit event data to a storage location; create a first block comprising a subset of the first audit event data and a header comprising the first hash; and write the first block to a scoped distributed ledger. A verification node may generate a third hash from the first hash and a second hash for a second block for a second audit event; create a third block comprising the third hash in a header of the third block and the subset of first audit event data and the subset of second audit even data; and write the second block to an audit distributed ledger.