Agreement-Key Validation for Tamper-Resistant Electronic Interactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computer systems for performing interactions between two entities are difficult to secure and often subject to tampering, leading to inefficiencies, false positives, and ineffective security measures.
Innovation Solution
A system and method that verifies electronic interactions using an agreement key by exchanging and securely storing key information between initiating and receiving devices, comparing it with extracted information during the interaction, and employing encryption to ensure authenticity, allowing for secure completion or reversal of interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing security measures are implemented to protect interactions, then security is improved, but interaction completion speed decreases and false positives increase
Solution Approach 1:
The system performs preliminary actions by pre-generating and storing authentication keys and checksum values before interactions occur. When an interaction is initiated, the system quickly verifies authenticity by comparing extracted keys and checksums against pre-stored values, enabling rapid validation without complex real-time analysis that would slow down interaction completion.
Solution Approach 2:
The system changes the verification parameter from complex multi-factor authentication to simple key and checksum comparison. By transforming the security verification into a straightforward matching operation between extracted authentication data and pre-stored reference data, the system achieves both high security and fast verification speed.
2Reliability
If sophisticated security checks are performed on interactions, then tampering detection is improved, but resource utilization decreases
Solution Approach 1:
The system extracts only the essential authentication elements (authentication key and checksum value) from the interaction data for verification purposes. By taking out only these critical components rather than performing comprehensive analysis of entire interaction datasets, the system achieves effective tampering detection with minimal resource consumption.
Solution Approach 2:
The system uses disposable authentication keys and checksums that are generated for specific interactions and discarded after verification. These lightweight cryptographic elements provide strong tampering detection capability without requiring sustained computational resources, enabling efficient one-time verification.
3Reliability
If encryption is applied to protect interaction data, then security is improved, but data processing complexity increases
Solution Approach 1:
The system performs encryption and key generation as preliminary actions before interactions occur. Authentication keys are pre-generated and stored in encrypted form, and the system prepares verification routines in advance. This preliminary preparation simplifies real-time processing during actual interactions, as the system only needs to perform straightforward key comparison rather than complex real-time encryption operations.
Data Source
AI summary
A system includes a memory and a processor that validates an interaction between an initiating and a receiving device. An encrypted request is received to perform the interaction and the processor extracts an initiating device identification, a receiving device identification, and one or more numerical values associated with the interaction. Using this extracted information, the processor produces a verification key by applying a hash function and a verification checksum value using a checksum function. The verification key and verification checksum value are then compared with an authentication key and authentication checksum value that were produced in a same manner prior to the interaction being initiated. If it is determined that either the verification key and the authentication key do not have the same value, or verification checksum value and authentication checksum value do not have the same value, then the interaction is reversed.