Transaction Security via Segmented Data and User Modification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for accessing services, such as banking transactions, are vulnerable to data alteration by malicious applications on personal computers, compromising transaction security.

Innovation Solution

A method where a first device receives complete transaction data, generates a signature, modifies it to create partial data, and sends it to a second device for user modification, which then generates a second signature for verification, ensuring only authorized transactions are completed if the signatures match.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If complete transaction data is sent to the user terminal for validation, then the user can review the full transaction details, but malicious applications on the PC can alter the data before it reaches the user

Engineering Contradiction:
Improvetransaction securityVSAvoiddata alteration by malicious applications
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The server segments the complete transaction data into multiple parts, each containing only specific fields (e.g., amount in one part, beneficiary in another). The user terminal receives and displays these separate parts, preventing malicious PC applications from altering the complete transaction data while maintaining user awareness of all transaction details.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The server acts as an intermediary that generates and controls the distribution of transaction data parts. Instead of the PC application handling complete transaction data, the server mediates by sending only specific parts to the user terminal for display, thereby preventing malicious alteration while ensuring the user receives all necessary information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the user is required to manually modify and complete transaction data parts, then security against malicious applications is improved, but the operation complexity and time required increase

Engineering Contradiction:
Improvetransaction securityVSAvoiduser operation complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The user terminal automatically performs the assembly of complete transaction data by combining the received parts in the correct sequence. The user only needs to provide supplementary information where required, while the terminal handles the complex task of reconstructing the complete transaction data, thereby maintaining security without significantly increasing user burden.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The server prepares and sends the transaction data parts in a predetermined structure and sequence to the user terminal before the user needs to validate them. This preliminary organization reduces the user's workload by presenting data in an already-structured format, requiring only minimal supplementary input rather than complete manual assembly.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If partial transaction data is sent to the user terminal instead of complete data, then security is improved by preventing malicious alteration, but the user receives incomplete information

Engineering Contradiction:
Improvetransaction securityVSAvoidincomplete transaction data at user terminal
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The user terminal sends feedback to the server indicating which transaction data parts are missing or require supplementation. The server responds by sending the appropriate additional parts or allowing the user to input missing information. This feedback loop ensures the user eventually receives and can review all complete transaction information while maintaining security through the segmented delivery process.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The transaction data delivery process is made dynamic, allowing the user terminal to request additional data parts as needed and the server to respond by sending them. This dynamic exchange ensures the user receives all necessary information to make an informed decision, while the segmented approach maintains security throughout the interactive process.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10263973B2Method for accessing a service, corresponding first device, second device and system
Publication Date: 2019.04.16 THALES DIS FRANCE SA
  • US10263973B2 patent drawing

AI summary

A first device generates a first signature by using complete transaction data received from a second device, a first algorithm and a first key, modifies at least one character from the complete transaction data and gets partial transaction data, and sends to the second device the partial transaction data. The second device requests a user to modify the partial transaction data by providing at least one character, as complementary data to the partial transaction data, gets, as request response from a user, at least one character to modify the partial transaction data, a corresponding result being proposed modified transaction data, generates a second signature by using the proposed modified transaction data, the first algorithm and the first key, and sends to the first device the second signature. Only if the second signature does match the first signature, then the first device authorizes to carry out a corresponding transaction.