API Call Interception for Secure Production Scanning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Web application scanning for security vulnerabilities often results in unintended modifications to the production environment and triggers unnecessary tasks, leading to performance issues and usability problems.
Innovation Solution
A system that detects specific API calls to assist in scanning sessions by monitoring and redirecting or skipping certain API calls, such as file modifications, database connections, and email interactions, to minimize disruption and identify potential vulnerabilities without affecting the application's functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If web application scanning is performed to detect security vulnerabilities, then security detection capability is improved, but unintended modifications to production environment occur and unnecessary tasks are triggered
Solution Approach 1:
The patent introduces an intermediary component that intercepts API calls during scanning operations. This intermediary layer monitors and controls the interaction between the scanning process and the production environment, preventing harmful modifications while allowing legitimate security detection. The intermediary acts as a buffer that filters out unwanted side effects.
Solution Approach 2:
The patent segments the scanning process into distinct phases and controls API call execution based on the current scanning phase. By dividing the scanning operation into controlled segments, the system can permit certain API calls during specific phases while blocking others, thereby preventing unintended modifications to the production environment.
2Reliability
If comprehensive scanning is performed to identify all security vulnerabilities, then detection completeness is improved, but application performance deteriorates due to resource consumption
Solution Approach 1:
The patent implements partial action by selectively executing only the necessary API calls required for security scanning during each phase. Instead of performing all possible scanning operations simultaneously, the system executes a subset of API calls appropriate to the current scanning stage, reducing resource consumption while maintaining detection effectiveness.
Solution Approach 2:
The patent employs periodic action by structuring the scanning process into distinct phases that execute sequentially. Each phase performs specific scanning tasks and then pauses, allowing the application to maintain normal performance between phases. This periodic execution pattern prevents continuous resource exhaustion while ensuring comprehensive security coverage over time.
3Reliability
If scanning operations are executed to detect vulnerabilities, then security assessment is improved, but usability of the application deteriorates
Solution Approach 1:
The patent applies dynamics by making the scanning process adaptive to application state and user activity. The system dynamically adjusts scanning intensity and API call execution based on current application conditions, reducing interference with user operations while maintaining security assessment capability. This dynamic approach allows the application to remain responsive and usable during scanning operations.
Data Source
AI summary
Examples herein disclose via use of a physical processor, detecting a specific application programming interface (API) call to interact with an application running on a production server. Based on the detection of the specific API call, die examples assist, using the physical processor, a scanning session based on the specific API call Using the physical processor, the examples identify a modification to the application based on the scanning session.