Vulnerability Scanning via Component Dependency Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computer systems face complexity in identifying and managing security vulnerabilities across networked elements, particularly in applications that may be exploited by malware, as existing tools struggle to accurately associate vulnerabilities with specific application components and contextual security information.

Innovation Solution

A system that includes a processor and memory with instructions to scan application components, identify additional components accessed by them, determine known vulnerabilities, associate these vulnerabilities, and adjust their characterization based on contextual security information, using a combination of local and remote scanning capabilities and databases for comprehensive vulnerability management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If comprehensive scanning of application components and their dependencies is performed to identify all vulnerabilities, then vulnerability detection completeness is improved, but system complexity and processing time increase

Engineering Contradiction:
Improvevulnerability detection completenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the vulnerability scanning process into distinct phases: identifying application components, determining their dependencies, scanning for vulnerabilities, and associating findings. This segmentation allows each phase to be handled independently, reducing overall system complexity while maintaining comprehensive coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary identification of application components and their dependencies before conducting vulnerability scanning. By pre-establishing the component hierarchy and relationships, the system avoids complex real-time analysis during the scanning phase, thereby reducing processing complexity while ensuring complete vulnerability detection.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive scanning of application components and their dependencies is performed to identify all vulnerabilities, then vulnerability detection completeness is improved, but processing time increases

Engineering Contradiction:
Improvevulnerability detection completenessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary identification of application components and their dependencies before conducting vulnerability scanning. By pre-establishing the component hierarchy and relationships, the system avoids complex real-time analysis during the scanning phase, thereby reducing processing time while ensuring complete vulnerability detection.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system automatically determines dependencies between application components by analyzing code references and inter-component communications without requiring manual input. This self-service approach eliminates time-consuming manual dependency mapping while maintaining accurate vulnerability association.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If vulnerabilities are associated with specific application components using dependency analysis, then vulnerability characterization accuracy is improved, but measurement and detection difficulty increases

Engineering Contradiction:
Improvevulnerability characterization accuracyVSAvoiddetection difficulty
Core Design Contradiction:
Measurement precisionVSDifficulty of detecting and measuring

Solution Approach 1:

The system uses feedback from dependency analysis results to refine vulnerability associations. By continuously analyzing component relationships and updating vulnerability mappings based on discovered dependencies, the system improves characterization accuracy while using the feedback loop to automate complex detection processes, reducing overall difficulty.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system replaces manual vulnerability characterization with automated analysis mechanisms that examine code references, data flows, and component interactions. This substitution of automated mechanical analysis for manual processes improves precision while reducing the difficulty of detection through systematic, repeatable methods.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Measurement precision

If contextual security information is used to adjust vulnerability characterizations, then security assessment accuracy is improved, but information processing requirements increase

Engineering Contradiction:
Improvesecurity assessment accuracyVSAvoidinformation processing requirements
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system applies contextual security information selectively to specific vulnerabilities based on their characteristics and the surrounding environment. Rather than processing all information uniformly, the system tailors the analysis to each vulnerability's local context, improving assessment accuracy while reducing overall information processing requirements by focusing only on relevant data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9977905B2Method and system for identification of security vulnerabilities
Publication Date: 2018.05.22 ASSURED ENTERPRISES INC
  • US9977905B2 patent drawing
  • US9977905B2 patent drawing
  • US9977905B2 patent drawing

AI summary

A system for securing an electronic device may include a processor and a memory. The memory may be communicatively coupled to the processor and include instructions. The instructions, when loaded and executed by the processor, cause the processor to scan data including one or more application components to uniquely identify elements therein, determine from a given application component additional components to be accessed by the given application component, scan the additional components to uniquely identify elements therein, determine whether the additional components include any known vulnerabilities, associate one or more known vulnerabilities of the additional components with the given application component, record the known vulnerabilities and the given application component. The given application component may be uniquely identified.