Token-Based Firewall Correlation for Multi-Tenant Web Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for correlating firewall events with web application sub-systems in multi-tenant environments, such as database queries and file system activities, are inaccurate and inefficient, particularly in complex web applications where race conditions and noise can obscure vulnerabilities.

Innovation Solution

Implementing a token-based firewall correlation system that injects identifying tokens into session contexts, database queries, and responses, allowing the firewall to accurately track and correlate events across multiple sub-systems, enabling more precise identification of abnormalities and reactive security measures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If timing-based correlation is used to link firewall events with web application sub-systems, then the system can attempt to correlate events without additional infrastructure, but the accuracy of correlation deteriorates in complex web applications with race conditions and noise

Engineering Contradiction:
Improvecorrelation system complexityVSAvoidevent correlation accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent introduces tokens as intermediary elements that are injected into web application sessions and subsequently embedded in database queries, file system operations, and other sub-system activities. These tokens act as mediators that carry correlation information through the complex multi-tenant environment, enabling accurate event linking without relying on fragile timing-based methods. The tokens serve as persistent identifiers that survive through race conditions and system noise.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If tokens are injected into session contexts and sub-system calls to improve correlation accuracy, then event tracking precision improves, but the device complexity and processing overhead increase

Engineering Contradiction:
Improveevent correlation accuracyVSAvoidfirewall system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent creates a universal token mechanism that serves multiple functions simultaneously: it identifies web application sessions, traces database queries, correlates file system operations, and links outbound connections. This single token-based approach replaces multiple separate correlation systems, reducing overall complexity while maintaining high accuracy across diverse sub-systems.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Use of energy by moving object

If timing-based correlation is used, then the system operates without additional processing overhead, but the ability to detect vulnerabilities deteriorates due to race conditions and environmental noise

Engineering Contradiction:
Improveprocessing overheadVSAvoidvulnerability detection reliability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The patent implements preliminary action by injecting tokens into web application sessions before any sub-system operations occur. This pre-establishes a reliable correlation mechanism that persists through all subsequent operations, eliminating the need for post-hoc timing analysis. The tokens are prepared in advance and embedded in all relevant operations, ensuring reliable vulnerability detection without excessive processing overhead during actual security analysis.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10116623B2Methods and systems for providing a token-based application firewall correlation
Publication Date: 2018.10.30 SALESFORCE INC
  • US10116623B2 patent drawing
  • US10116623B2 patent drawing
  • US10116623B2 patent drawing

AI summary

Token-based firewall functionality. A request is received for access to a resource from a remote user device, the request received by an application firewall. A token is associated with the request. The token and associated information are stored in an event correlator coupled with the application firewall. The token is associated with one or more subsequent actions by the resource in response to receiving the request. A response to the request including the token is generated. The response with the token is transmitted to the remote user device via the application firewall. The application firewall analyzes the response and determines an action to be taken on the response based on the token and the associated information.