Workflow Data Tracking via Secure Database and Blockchain
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data security processes are cumbersome and often skipped, lacking integration into user workflows, and do not adequately verify purposeful changes to digital assets in public safety applications.
Innovation Solution
A method and system for tracking digital assets using a secure database that stores metadata describing steps in a workflow, including input and output data files and transactions, allowing for the generation of a trace of the workflow and providing proof of non-manipulated data through blockchain technology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual hash code verification is performed, then data authenticity can be verified, but the process is cumbersome and time-consuming
Solution Approach 1:
The system performs hash code verification automatically in the background when files are accessed or opened, before the user needs to work with the data. This preliminary action eliminates the need for manual verification while ensuring data authenticity is maintained throughout the workflow.
Solution Approach 2:
The verification system operates autonomously without requiring user intervention. It automatically checks hash codes, tracks data modifications, and maintains the chain of custody records, allowing the system to serve itself rather than burdening the user with manual verification tasks.
2Reliability
If hash code checking is integrated into workflow, then verification consistency improves, but system complexity increases
Solution Approach 1:
The system merges data verification functions with the existing workflow by integrating hash code checking, modification tracking, and chain of custody management into the file access and processing operations. This combination ensures verification consistency without requiring separate complex verification steps.
Solution Approach 2:
A database serves as an intermediary between the user workflow and the verification system. It stores hash codes, modification records, and chain of custody information, enabling consistent verification while keeping the user interface simple and the system architecture manageable through structured data storage.
3Reliability
If automated tracking is implemented, then human errors are reduced, but device complexity increases
Solution Approach 1:
The automated tracking system operates independently, automatically recording file accesses, modifications, and transfers without requiring user input or intervention. This self-service approach eliminates human errors in tracking while maintaining manageable system complexity through standardized automated processes.
Solution Approach 2:
The system continuously monitors and records data modifications, hash code changes, and access patterns, providing automatic feedback about the data's provenance and integrity status. This feedback mechanism ensures accurate tracking while using structured logging and database storage to keep the system complexity organized and manageable.
4Reliability
If comprehensive workflow tracking is performed, then evidence reliability improves, but time for processing increases
Solution Approach 1:
The system records workflow information automatically at the moment of file access, modification, or transfer, before any analysis or legal proceedings occur. This preliminary recording of evidence chain information eliminates the need for retrospective tracking while ensuring comprehensive evidence reliability is maintained.
Solution Approach 2:
The system extracts and stores only the essential workflow information needed for evidence reliability (timestamps, user identifiers, file hashes, modification types) rather than capturing every detail of the entire workflow process. This extraction approach maintains evidence reliability while minimizing processing time and storage requirements.
Data Source
AI summary
A method that includes providing a database for storing meta-data that describes steps in a workflow and an order of the steps in the workflow. The meta-data includes, for each of the steps: a reference to an input data file for the step; a description of a transaction performed at the step; and a reference to an output data file generated by the step based at least in part on applying the transaction to the input data file. Data that includes meta-data for a step in the workflow is received and the data is stored in the database. A trace of the workflow is generated based at least in part on contents of the database. The generating is based on receiving a request from a requestor for the trace of the workflow. At least a subset of the trace is output to the requestor.