Dynamic Token Tracking for Replay Attack Prevention
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Replay attacks during token authorization compromise user identities, allowing attackers to misuse secured data, as existing methods lack effective mechanisms to prevent unauthorized reuse of tokens.
Innovation Solution
A token authentication and tracking model is implemented, using a server computer to generate and verify unique authentication values through a function table, ensuring that each authorization is uniquely linked and tracked, making it difficult for malicious parties to use compromised tokens without knowing the specific function and prior authentication values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If token authorization is implemented to enable secure data access, then data security is improved, but the system becomes vulnerable to replay attacks where stolen tokens can be reused for unauthorized access
Solution Approach 1:
The patent implements dynamic token tracking values that change with each authorization attempt. Instead of static tokens, the system generates current token tracking values based on prior values and stored functions, making each token dynamically unique and preventing replay attacks where stolen tokens would be reused
Solution Approach 2:
The system performs preliminary actions by storing multiple functions and prior token tracking values before authorization occurs. During authentication, the system pre-computes what the current token tracking value should be based on stored functions and prior values, then verifies this against the presented token to detect replay attempts
2Reliability
If unique authentication values are generated and verified for each authorization, then replay attack prevention is improved, but the device complexity increases due to function tables and tracking mechanisms
Solution Approach 1:
The patent uses cryptographic functions to generate token tracking values that are computationally derived copies rather than storing complex authentication data. The function tables store mathematical relationships, and the system computes token values by applying these functions to prior values, simplifying storage while maintaining security
Solution Approach 2:
The system changes parameters by using different functions from the stored function table for different tokens or authorization contexts. This allows the same basic mechanism to handle diverse authentication scenarios without increasing fundamental system complexity, as the core structure remains the same while parameters (which functions to use) vary
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method including receiving, by a server computer (410), a request message from a token requestor computer (404) on behalf of a user device. The request message comprising a first current token tracking value and a first function index value. The server computer (410) can determine a second function index value. The server computer (410) can then compare the first function index value to the second function index value. If the first function index value and the second function index value match, the server computer (410) can determine (464) a function based on the first function index value and a stored function table associated with the user device. The server computer (410) can then determine a second current token tracking value based on the function, then compare the first current token tracking value to the second current token tracking value. The server computer (410) can generate a response message in response to the comparing.