Proxy System Causal Graph for DoS Attack Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems fail to effectively manage and validate requests to website locations, leading to undesirable access such as Denial of Service (DoS) and Distributed Denial of Service (DDoS) attacks that overwhelm server resources.

Innovation Solution

A proxy system that intercepts and stores cookies with identifying information for website locations, using these cookies to establish legitimate request criteria and enforce access policies, thereby preventing illegitimate requests by ensuring requests follow established access patterns.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the server manages traffic by providing access to particular locations via an established path through locations of the website, then legitimate access is controlled, but the server cannot distinguish between legitimate requests and DoS attack requests that follow the same path

Engineering Contradiction:
Improvelegitimate access controlVSAvoidDoS attack vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary action by storing cookies with identifying information for website locations in advance during legitimate browsing sessions. These pre-stored cookies serve as reference data that enables later differentiation between legitimate requests (which contain matching cookies) and DoS attack requests (which lack proper cookies), thus resolving the contradiction between controlling legitimate access and preventing attacks.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system stores cookies with identifying information for website locations, then legitimate request validation is enabled, but additional storage and processing overhead is introduced

Engineering Contradiction:
Improverequest validation capabilityVSAvoidcookie storage and processing
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system uses cookies as simplified copies or representations of website location information rather than storing complete path profiles or complex access patterns. This copying approach enables request validation through simple cookie matching while avoiding the complexity of storing and processing detailed browsing history or complete access path data, thus resolving the contradiction between validation capability and system complexity.

Inventive Principle:
Principle #26Copying

3Object-affected harmful factors

If the proxy system intercepts and validates all incoming requests against stored path profiles, then DoS attacks are prevented, but legitimate request processing time increases

Engineering Contradiction:
ImproveDoS attack preventionVSAvoidrequest processing time
Core Design Contradiction:
Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The system applies partial action by performing validation only on specific request characteristics (presence of matching cookies) rather than analyzing complete request content or full browsing paths. This selective validation approach provides sufficient DoS protection while minimizing processing time overhead, as the proxy only needs to check for cookie presence and match identifying information rather than performing comprehensive path analysis on every request.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS20240089288A1Providing application security using causal graph
Publication Date: 2024.03.14 PALO ALTO NETWORKS INC
  • US20240089288A1 patent drawing
  • US20240089288A1 patent drawing
  • US20240089288A1 patent drawing

AI summary

Computer systems and methods are provided for storing a first path profile. A computing device receives a first request to access a first location of a website, transmits the first request to a server, and receives a first cookie that includes identifying information for the first location. In response to receiving the first cookie, the device stores the identifying information. The device receives a second request to access a second location of the website that is distinct from the first location. The second request includes the identifying information for the first location. The device transmits the second request to the server and receives a second cookie that includes the identifying information for the first location and for the second location. In response to receiving the second cookie, the device stores the first path profile that includes the identifying information for the first location and the second location.