Vulnerability Result Integration to Eliminate Redundant Scanning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing vulnerability scanning methods, whether local or external, often result in redundant data collection, reducing overall efficiency and resource utilization in scanning private company networks.

Innovation Solution

Implementing a complementary scan engine scheme that coordinates with local scan agents to determine redundant data collection, allowing the scan engine to skip unnecessary checks and integrate vulnerability results efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If both local scan agents and external scan engines perform vulnerability checks, then comprehensive vulnerability detection is achieved, but redundant data collection increases resource consumption

Engineering Contradiction:
Improvevulnerability detection completenessVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent combines local scan agent results with external scan engine results by integrating vulnerability data from both sources into a unified view, eliminating redundant checks while maintaining comprehensive detection coverage

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system uses feedback from local scan agents to inform the external scan engine which vulnerability checks have already been performed, allowing the external scanner to skip redundant checks and focus only on unverified vulnerabilities

Inventive Principle:
Principle #23Feedback

2Reliability

If external scan engine performs all vulnerability checks, then complete vulnerability assessment is achieved, but scan time increases

Engineering Contradiction:
Improvevulnerability assessment completenessVSAvoidscan time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Local scan agents perform preliminary vulnerability checks before external scanning, pre-identifying known vulnerabilities so the external scan engine can skip these checks and focus only on unverified issues, significantly reducing overall scan time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The external scan engine skips vulnerability checks that have already been performed by local scan agents, rushing through the scanning process by focusing only on unverified vulnerabilities rather than re-checking known issues

Inventive Principle:
Principle #21Skipping (Rushing through)

3Extent of automation

If vulnerability results are integrated into databases, then centralized security management is achieved, but data storage requirements increase

Engineering Contradiction:
Improvecentralized security managementVSAvoiddata storage requirements
Core Design Contradiction:
Extent of automationVSQuantity of substance

Solution Approach 1:

The system extracts only essential vulnerability result data for centralized storage in databases, separating critical security information from redundant details, thereby achieving centralized management while minimizing storage requirements

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements local caching of vulnerability results at scan agents and external scanners, allowing each component to store only the specific data it needs locally while maintaining centralized database integration, optimizing storage distribution across the system

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12568106B1Vulnerability result integration scheme
Publication Date: 2026.03.03 RAPID7 INC
  • US12568106B1 patent drawing
  • US12568106B1 patent drawing
  • US12568106B1 patent drawing

AI summary

Various embodiments include systems and methods to implement a complementary scan engine scheme for avoiding redundant vulnerability check data collection when using a scan engine to scan a target asset and/or to implement a vulnerability result integration scheme for determining whether to integrate a respective vulnerability result into one or more databases. In various embodiments, at least one integration state may be determined. According to the vulnerability result integration scheme, the at least one integration state may define whether an integrator is to integrate the respective vulnerability result into the database(s).