REST API Scanning with Crawling and Fuzzing for Vulnerability Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing REST APIs are vulnerable to security threats and vulnerabilities, such as cross-site request forgery, cross-site scripting, and SQL injection, due to the transmission of sensitive data, necessitating effective security testing methodologies.

Innovation Solution

A method involving an API testing tool that generates a scan configuration file based on API workflow data, crawls API requests, applies vulnerability tests, and generates a vulnerability report to secure the API against identified threats.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If REST APIs transmit sensitive data for optimal functionality, then the API provides necessary services and functionalities, but the API becomes vulnerable to security threats and vulnerabilities

Engineering Contradiction:
ImproveAPI functionalityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary action by performing security scanning and vulnerability assessment on REST APIs before they are deployed or used in production environments. The system automatically crawls API endpoints, analyzes request-response patterns, and identifies security vulnerabilities in advance, allowing developers to fix issues before they can be exploited. This proactive approach maintains API functionality while preventing security threats from materializing.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive security testing is performed on REST APIs, then security vulnerabilities are identified, but the testing process requires significant time and computational resources

Engineering Contradiction:
Improvesecurity assuranceVSAvoidtesting duration
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling REST APIs to test themselves automatically without requiring manual security testing intervention. The system uses automated crawling agents that independently navigate API endpoints, execute security tests, and generate vulnerability reports. This self-testing mechanism provides comprehensive security assurance while minimizing the time and human resources required, as the process runs autonomously using the API's own operational patterns.

Inventive Principle:
Principle #25Self-service

3Productivity

If automated crawling and scanning of API requests is implemented, then security vulnerabilities are detected efficiently, but the complexity of the testing system increases

Engineering Contradiction:
Improvevulnerability detection efficiencyVSAvoidtesting system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a multi-functional security testing system that combines multiple capabilities into a single unified platform. The automated crawling agent simultaneously performs endpoint discovery, request pattern analysis, vulnerability scanning, and report generation. This universal approach increases productivity by consolidating multiple security testing functions into one efficient process, while the modular architecture manages system complexity through standardized interfaces and reusable components.

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

Data Source

PatentUS20250227125A1Rest API scanning for security testing
Publication Date: 2025.07.10 QUALYS
  • US20250227125A1 patent drawing
  • US20250227125A1 patent drawing
  • US20250227125A1 patent drawing

AI summary

Methods and systems for securing an application programming interface (API) are presented. The method comprises: receiving API workflow data associated with an API testing tool and generating a scan configuration file using the API workflow data; crawling the collection of API requests by identifying and retrieving a link associated with the collection of API requests; and crawling the link to generate a crawled link response. The method also includes executing one or more vulnerability tests on the crawled link response including applying at least one passive detection rule to the crawled link response and fuzzing the link. The fuzzed link may be transmitted in a request to an application server following which scan data indicative of at least one vulnerability associated with a response from the application server may be generated. The scan data may be used to generate a vulnerability report.