API Proxy Token Mapping for User Activity Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Short-lived tokens used for API authorization do not allow for effective monitoring of user behavior over time, making it difficult to track user activity and detect malicious attacks, as they expire quickly and do not reveal the API key used to generate them.

Innovation Solution

A proxy system is introduced between client devices and API services that stores and maps API keys to short-lived tokens, enabling the monitoring of user behavior by logging and analyzing API service requests, and applying security threat algorithms to detect anomalies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If short-lived tokens are used for API authorization, then security is improved by limiting the impact of stolen credentials, but user tracking and behavior monitoring become difficult

Engineering Contradiction:
ImprovesecurityVSAvoiduser tracking capability
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent introduces a proxy server as an intermediary component between the client and API services. This proxy intercepts API requests, extracts tokens, and maps them back to original API keys through a mapping service. This intermediary layer enables continuous tracking of user behavior across multiple short-lived tokens while maintaining the security benefits of token expiration, as the proxy can correlate activity patterns without exposing actual API keys.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If tokens expire quickly to limit attack impact, then security is improved, but the ability to detect malicious behavior over time is reduced

Engineering Contradiction:
ImprovesecurityVSAvoidmalicious behavior detection
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements a feedback mechanism where the proxy server continuously monitors API requests, extracts token information, and sends queries to the mapping service to retrieve associated API keys and user identifiers. This feedback loop enables the system to accumulate behavioral data over time, analyze patterns, and detect malicious activities such as unusual request frequencies or abnormal access patterns, even though individual tokens have short lifetimes.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If API keys are made accessible to clients for ease of use, then ease of operation is improved, but security is worsened due to potential key theft

Engineering Contradiction:
Improveclient accessVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the authentication system into distinct components: API keys remain securely stored on the server side, while clients receive short-lived tokens for actual API access. The proxy server and mapping service create additional segmentation layers that enable tracking and security monitoring without exposing API keys to clients. This segmentation allows clients to operate easily with tokens while the system maintains strong security through key isolation and monitored access patterns.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20230216681A1API user tracking via token to API key mapping
Publication Date: 2023.07.06 IMPERVA INC
  • US20230216681A1 patent drawing
  • US20230216681A1 patent drawing
  • US20230216681A1 patent drawing

AI summary

Embodiments of the present disclosure relate to tracking a user’s activity using a mapping of their API key to a token. A proxy device may receive a registration request from a client, the registration request including a first API key. The proxy device may forward the registration request to a registration endpoint and receive a first token generated using the first API key during an authentication process performed by the registration endpoint. The proxy device may associate the first API key with the first token and forward the first token to the client. The proxy device may receive a service request from the client that includes the first token and may add information regarding the service request into an entry in a log corresponding to the first API key.