Centralized Coordinator for Distributed Vulnerability Scans

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed vulnerability scans in networking environments face challenges such as congestion, redundant scanning, unpredictable resource utilization, and inefficient coordination, leading to overburdened resources and unpredictable scan timing.

Innovation Solution

A centralized scanning coordinator determines parameters for distributed scans, assigning scanning targets and timing to scanning nodes based on their attributes, dividing them into groups for coordinated and efficient resource utilization, thereby preventing simultaneous scans and optimizing resource use.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If distributed scanning nodes perform scans independently and simultaneously, then scan speed increases, but network congestion occurs and resource utilization becomes unpredictable

Engineering Contradiction:
Improvescan speedVSAvoidcoordination complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

A centralized scanning coordinator is introduced as an intermediary between scanning nodes and network resources. The coordinator receives scan requests, assigns targets to specific nodes, and schedules scan timing to prevent simultaneous scans. This mediator manages the complexity of coordination while allowing distributed nodes to maintain their scanning capabilities, thus improving scan speed without causing network congestion or unpredictable resource utilization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If scanning nodes operate autonomously without coordination, then ease of operation improves, but redundant scanning and lack of high-level analysis occur

Engineering Contradiction:
Improveautonomous operationVSAvoidscan effectiveness
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The scanning system is segmented into two functional layers: autonomous scanning nodes that perform actual vulnerability scanning, and a centralized coordinator that manages target assignment and result aggregation. This segmentation allows nodes to operate independently (maintaining ease of operation) while the coordinator ensures no redundant scanning occurs by tracking which nodes scan which targets, and provides high-level analysis by collecting and processing results from all nodes.

Inventive Principle:
Principle #1Segmentation

3Reliability

If a centralized coordinator manages distributed scans, then resource utilization predictability improves, but system complexity increases

Engineering Contradiction:
Improveresource utilization predictabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The centralized scanning coordinator performs multiple functions within a single system component: it assigns scanning targets to nodes, schedules scan timing to prevent congestion, tracks which nodes have scanned which targets to eliminate redundancy, and aggregates results for high-level analysis. By consolidating these diverse functions into one universal coordinator, the system achieves predictable resource utilization without proportionally increasing overall system complexity.

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

Data Source

PatentUS11916950B1Coordinating a distributed vulnerability network scan
Publication Date: 2024.02.27 VMWARE INC
  • US11916950B1 patent drawing
  • US11916950B1 patent drawing
  • US11916950B1 patent drawing

AI summary

The disclosure provides an approach for coordinating a distributed vulnerability network scan. Embodiments include sending, by a computing node, a check-in message to a scanning coordinator, the check-in message indicating attributes of the computing node. Embodiments include receiving, by the computing node, a scan configuration message from the scanning coordinator, the scan configuration message comprising: scan timing information for the computing node; and a list of scanning targets for the computing node. Embodiments include determining, by the computing node, a scanning time window based on the scan timing information for the computing node. Embodiments include scanning, by the computing node, one or more scanning targets in the list of scanning targets for the computing node during the scanning time window.