Secure Data Transfer via Identity Verification and Hash Fingerprinting
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital data transfer systems lack adequate security measures to ensure that only authorized data is transferred from a first storage repository to a verified second repository, risking unauthorized access and data integrity issues.
Innovation Solution
A method and system that establish secure data transfer by using a data port device to create communications links between repositories, verify the identity of the second repository through human and internal identifiers, and ensure data integrity using cryptographic hash functions before and after transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If data ports are opened to enable data transfer between repositories, then data transfer capability is improved, but security against unauthorized access deteriorates
Solution Approach 1:
The system performs preliminary verification of the second repository's identity using human recognizable identifiers and internal identifiers before opening the data port. This advance verification ensures that only authorized repositories can receive data transfers, preventing unauthorized access while maintaining transfer capability.
Solution Approach 2:
The data port device acts as an intermediary between the workflow computing system and the second repository. It mediates the data transfer process by controlling port access based on verified repository identity, thus enabling secure transfers while blocking unauthorized access attempts.
2Productivity
If data ports are opened for data transfer, then transfer efficiency is improved, but control over transferred data deteriorates
Solution Approach 1:
The system uses cryptographic hash functions to generate fingerprints of the data set before and after transfer, then compares these fingerprints to verify data integrity. This feedback mechanism ensures that only the designated data set is transferred and remains unaltered, maintaining control over transferred data while enabling efficient transfer.
Solution Approach 2:
The system calculates the cryptographic hash fingerprint of the data set before transfer and records it in the work order. This preliminary action establishes a reference for later verification, ensuring data control without hindering the transfer process.
3Ease of operation
If repository identification is simplified, then ease of operation is improved, but verification accuracy deteriorates
Solution Approach 1:
The repository identification system uses two separate identifiers: a human recognizable identifier for easy identification and an internal identifier for precise verification. This segmentation allows the system to maintain both ease of operation and verification accuracy by using each identifier for its appropriate purpose.
Solution Approach 2:
The data port device serves as an intermediary that receives and verifies both human recognizable identifiers and internal identifiers. It mediates between the simplified identification interface and the rigorous verification requirements, ensuring both ease of operation and verification accuracy.
Data Source
AI summary
Methods, systems and devices for securely transferring digital data from a first repository to a second repository are disclosed. Per at least one embodiment, a second repository is identified with a human recognizable identifier and an internal identifier associated with such second repository is determined. When a data transfer is desired, a work order associating the data to be transferred and identifying the second repository based on each of the human identifier and the internal identifier is generated. Such work order is utilized by a data port device to open normally closed communications port to accomplish the transfer of the data to the second repository when the identity of such second repository is confirmed by the data port device. A data integrity check confirms that only the designated to be transferred data was actually transferred to the second repository designated in the work order.