Web Service Request Threat Level Flagging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security systems in data networks often result in false positives, where legitimate web service requests are incorrectly identified as security threats, leading to denial of service and user frustration, as they fail to differentiate between actual threats and benign requests effectively.

Innovation Solution

A method and system that analyze web service requests based on security signatures, determine a threat level, and flag the request with a corresponding threat level indicator, allowing the request to proceed while enabling downstream applications to handle it appropriately, rather than blocking it.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a security system blocks requests that match security signatures, then security threats are prevented, but legitimate requests are incorrectly denied due to false positives

Engineering Contradiction:
Improvesecurity threat preventionVSAvoidlegitimate request delivery
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent introduces an intermediary mechanism (threat level flagging system) between the security signature matching and request blocking. Instead of directly blocking requests that match security signatures, the system inserts a flag into the request that indicates a determined threat level, allowing downstream applications to make the final blocking decision based on the flagged threat level, thus preventing false positive blocking of legitimate requests while still blocking actual threats

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If a strict denial policy is applied to matching requests, then security is enforced, but user experience deteriorates due to inability to resend legitimate requests

Engineering Contradiction:
Improvesecurity enforcementVSAvoiduser request resending
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies dynamics by making the security policy flexible rather than static. Instead of a fixed strict denial policy, the system dynamically determines threat levels for each request and applies differentiated handling - requests with low threat levels can proceed while requests with high threat levels are blocked. This dynamic approach allows legitimate requests to be resent after temporary failures without compromising security enforcement

Inventive Principle:
Principle #15Dynamics

3Speed

If security systems block requests at the network level, then threats are stopped early, but downstream applications cannot implement nuanced handling of different threat levels

Engineering Contradiction:
Improvethreat blocking speedVSAvoidapplication-level threat handling
Core Design Contradiction:
SpeedVSAdaptability or versatility

Solution Approach 1:

The patent segments the security handling process into two parts: network-level threat level determination and flagging, and application-level decision making. The security system quickly determines threat levels and inserts flags into requests, providing fast initial filtering. Downstream applications then use the flagged threat levels to implement nuanced handling strategies, combining the speed of network-level processing with the adaptability of application-level decision making

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9537886B1Flagging security threats in web service requests
Publication Date: 2017.01.03 A10 NETWORKS INC
  • US9537886B1 patent drawing
  • US9537886B1 patent drawing
  • US9537886B1 patent drawing

AI summary

Provided are methods and systems for flagging security threats in web service requests. Specifically, a method for flagging security threats in web service requests can include receiving a request addressed to an addressee. The method can further include analyzing the request based on at least one security signature. The method can continue with determining a threat level associated with the request. The determination can be carried out based on the analysis. The method can further include creating a flag corresponding to the threat level. The method can further include inserting the flag into a network packet associated with the request, thereby creating a modified request. The method may further include sending the modified packet to the addressee. An application associated with the addressee can be operable to selectively process the request based on the threat level.