Event-Based Data Acquisition for Real-Time Integrity Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data acquisition methods for real-time applications (RTAs) are not repeatable or reproducible due to continuous system modifications, and lack scalability for multiple sources, making it difficult to ensure data integrity and chain of custody, especially in high-use systems like business-critical applications.
Innovation Solution
A system comprising an agent and a collector that defines time-ordered frames to collect events, calculate local integrity checks, and transmit a global integrity check for secure storage, allowing for repeatable and reproducible data acquisition without system shutdowns.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data extraction methods are used on real-time applications, then data can be collected, but the data is not repeatable or reproducible due to continuous system modifications
Solution Approach 1:
The system performs preliminary actions by capturing events as they occur in real-time and continuously updating the hash value before any potential modifications occur. This proactive approach ensures that the evidence is recorded in its original state, making it repeatable and reproducible regardless of subsequent system changes.
Solution Approach 2:
Instead of directly extracting data from the running system which may change, the system creates a cryptographic copy (hash) of the events. This hash copy remains stable and reproducible even when the original system continues to modify its state, allowing verification without affecting the live system.
2Reliability
If data extraction is performed on high-use systems, then evidence can be collected, but the traditional chain of custody process requires system shutdown which is impracticable
Solution Approach 1:
The patent replaces the mechanical approach of shutting down systems to collect evidence with a software-based event capture mechanism. Events are intercepted and hashed while the system remains operational, substituting the physical shutdown requirement with an intelligent software agent that works transparently in the background.
Solution Approach 2:
An intermediary hash value is introduced between the event sources and the evidence collection process. This hash acts as a mediator that captures the state of events without requiring direct intervention or system shutdown, allowing chain of custody to be maintained while the system continues to operate normally.
3Quantity of substance
If current data acquisition methods are used, then a snapshot of data can be obtained, but the data is not scalable to systems with multiple sources of information
Solution Approach 1:
The system segments the evidence collection process into independent event sources, each generating its own hash. Multiple sources can be monitored simultaneously without interference, allowing the system to scale from single-source to multi-source environments while maintaining the same integrity verification mechanisms.
Solution Approach 2:
The patent merges multiple event sources by combining their individual hash values into a comprehensive evidence set. This merging process maintains the integrity of each source while creating a unified view of system state, enabling scalable deployment across complex multi-source environments.
Data Source
AI summary
A system for acquiring time limited data to facilitate integrity verification in real-time applications (RTAs) includes an agent and a collector. The agent is associated with a RTA and is in communication with the collector. The agent defines a plurality of time ordered time frames and during each time frame collects a collection of events from event sources occurring on the RTA. The agent calculates a local integrity check from the collection and a previous integrity check or an initial key, and transmits a global integrity check calculated from local integrity checks to the collector. The collector receives the global integrity check from the agent and stores the received global integrity check in a secure storage. The collector validates the integrity of the global integrity check and the received collections of events.