Web Application Data Tokenization via Intermediary Security Device

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Off-the-shelf encryption and tokenization solutions for securing web application data are often insufficient, requiring significant changes to existing computer systems and software, which can be costly and introduce bugs, leading many organizations to forego implementation, especially for internet-based data.

Innovation Solution

A method that modifies the HTML document of a webpage to replace user input fields with token equivalents, transmitting user data to a secured server instead of the original server, using a security device and vault provider to manage and store tokens, allowing secure data processing without altering the original system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If custom encryption or tokenization is implemented, then data security is improved, but system complexity and implementation cost increase

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a security device as an intermediary component that sits between the web application server and the client. This mediator handles all tokenization and decryption operations, allowing the original application to remain unchanged while security functions are added. The security device receives requests, performs tokenization on sensitive data, and returns tokenized values to the application, thus improving data security without increasing application complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the system into distinct functional components: the original web application server, a separate security device for tokenization operations, and a vault provider for secure storage. By dividing the security functionality into a separate segment, the original application doesn't need to be modified, and security can be implemented independently, reducing overall system complexity while maintaining security improvements.

Inventive Principle:
Principle #1Segmentation

2Reliability

If custom encryption or tokenization is implemented, then data security is improved, but implementation cost and risk increase

Engineering Contradiction:
Improvedata securityVSAvoidimplementation cost
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent creates a copy of the original web application's interface and functionality within the security device. The security device replicates the necessary input fields and forms, allowing users to interact with what appears to be the original application while actually submitting data through the secure tokenization pathway. This copying approach allows security implementation without requiring expensive custom development of entirely new interfaces or systems.

Inventive Principle:
Principle #26Copying

3Reliability

If data is removed and replaced with tokens, then data security is improved, but data accessibility and system functionality may be affected

Engineering Contradiction:
Improvedata securityVSAvoiddata accessibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent performs preliminary tokenization of sensitive data before it is processed by the application logic. By pre-replacing sensitive information with tokens that preserve the necessary data structure and format, the system maintains full functionality and adaptability while ensuring security. The tokens are designed to work seamlessly with existing application logic, allowing the system to adapt to various data types and operations without modification.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10726157B2Method, device and software for securing web application data through tokenization
Publication Date: 2020.07.28 DATEX
  • US10726157B2 patent drawing
  • US10726157B2 patent drawing
  • US10726157B2 patent drawing

AI summary

A method of securing user data provided through a webpage includes receiving an electronic file defining a webpage displayable by a computer. The webpage is initially configured to present an input field for receiving user data from a user, and instruct the computer to transmit the user data to a defined server. The method includes executing code that causes the computer to reconfigure the webpage to present a replacement field for receiving the user data from the user instead of the input field; and upon receiving user data in the replacement field, transmit said user data to a secured server instead of the defined server. The secured server may tokenize the data. The computer receives token data from the secured server; and transmits the token data instead of the user data to the defined server.