Audit Environment for Live Risk Model Timeout Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing AI systems in risk analysis for online transaction processing face challenges in identifying and mitigating sophisticated computing attacks, which can lead to timeouts and vulnerabilities, due to the time-consuming and resource-intensive process of debugging data processing models.

Innovation Solution

Implementing an audit computing environment that mirrors the production environment, allowing for live testing of risk models using production data to identify and debug models causing timeouts, by processing production traffic and data, and utilizing a replay request service to analyze execution times and flag models exceeding standard deviations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional debugging methods are used to identify timeouts in AI models, then security vulnerabilities can be detected, but the process is time-consuming and resource-intensive

Engineering Contradiction:
Improvesecurity vulnerability detectionVSAvoiddebugging time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary action by proactively injecting synthetic slow requests into the production environment before actual timeouts occur. These test requests are processed alongside real traffic to identify which AI models are susceptible to timeout attacks, enabling early detection and mitigation without waiting for actual security incidents

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a copy of the production environment by injecting synthetic test requests that mirror real user traffic patterns. These copied requests include artificial delays to simulate slow responses, allowing the system to observe timeout behavior in a controlled manner without disrupting actual operations

Inventive Principle:
Principle #26Copying

2Reliability

If AI models are tested extensively to identify timeout vulnerabilities, then security is improved, but system resources are consumed

Engineering Contradiction:
Improvesecurity robustnessVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies partial action by injecting only a controlled proportion of synthetic test requests into the production environment, rather than overwhelming the system with extensive testing. The synthetic requests are injected at a rate that consumes minimal additional resources while still being sufficient to identify timeout-vulnerable AI models through statistical analysis

Inventive Principle:
Principle #16Partial or excessive action

3Measurement precision

If the system processes all production traffic through audit pools for timeout detection, then accuracy is improved, but processing speed decreases

Engineering Contradiction:
Improvetimeout identification accuracyVSAvoidtransaction processing speed
Core Design Contradiction:
Measurement precisionVSSpeed

Solution Approach 1:

The system segments traffic processing by creating separate audit pools that handle synthetic test requests independently from real production traffic. This segmentation allows timeout vulnerability analysis to occur in parallel without blocking actual transaction processing, maintaining both accuracy and speed

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11785030B2Identifying data processing timeouts in live risk analysis systems
Publication Date: 2023.10.10 PAYPAL INC
  • US11785030B2 patent drawing
  • US11785030B2 patent drawing
  • US11785030B2 patent drawing

AI summary

This application discusses identifying data processing timeouts in live risk analysis systems. A service provider, such as an electronic transaction processor, may provide a production computing environment that includes a risk analysis system having one or more risk models, which may be machine-learning based. These risk models may be utilized in order to determine whether incoming data processing requests are fraudulent. To test these risk models using production data traffic, an audit computing environment made of a set of machines that do not service production computing environment requests, but that utilize databases and data connections as are used by the production systems. The audit computing environment may thus mirror the risk models and functionality of the production computing environment without the drawbacks of a typical fully separate testing environment. Thus, risk model performance and execution times may be monitored to determine whether any models encounter errors with production data traffic.