Vulnerability Chain Generation for Adaptive Cybersecurity Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cybersecurity analysis tools are fragmented and require significant investments for automation, are environment-specific, and lack flexibility to adapt to changes, making systematic vulnerability testing and risk assessment difficult.

Innovation Solution

A computer-implemented method for automatically generating vulnerability chains in a target environment using a unified vulnerability database, based on software elements and their descriptions, without complex formalization of environments or attacks, by constructing chains through similarity comparisons of vulnerability consequences and means.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If commercial and open-source cybersecurity tools are used for vulnerability detection, then vulnerability discovery capability is improved, but system complexity and cost increase

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

Solution Approach 1:

The patent segments the vulnerability detection process into distinct modules: passive vulnerability detection, active vulnerability detection, and vulnerability chain generation. Each module handles specific aspects of security testing independently, reducing overall system complexity while maintaining comprehensive detection capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system integrates multiple vulnerability detection approaches (passive scanning, active testing, fuzzing) into a unified platform that can analyze the same target environment using different methods. This multi-functional approach consolidates what would otherwise require separate tools, reducing complexity while improving detection reliability.

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

2Productivity

If automated vulnerability testing is implemented, then productivity is improved, but adaptability to environment changes deteriorates

Engineering Contradiction:
Improvetesting efficiencyVSAvoidadaptability to environment changes
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The vulnerability chain generation component dynamically adapts to environment changes by continuously monitoring software versions, configurations, and vulnerability databases. When changes are detected, the system automatically updates attack paths and testing procedures, maintaining both automation and adaptability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system incorporates feedback mechanisms where vulnerability detection results and environment change information are fed back into the vulnerability chain generation process. This enables automated testing to adapt to new conditions without manual intervention, resolving the contradiction between automation and adaptability.

Inventive Principle:
Principle #23Feedback

3Measurement precision

If comprehensive vulnerability analysis is performed, then measurement precision is improved, but loss of time increases

Engineering Contradiction:
Improvevulnerability analysis accuracyVSAvoidtesting time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary vulnerability detection and classification before generating comprehensive vulnerability chains. By pre-identifying potential vulnerabilities and organizing them into structured chains, the system reduces the time required for complete analysis while maintaining high precision through systematic evaluation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The vulnerability chain generation process continuously refines and updates attack paths based on detected vulnerabilities and environment characteristics. This continuous processing eliminates gaps in analysis while maintaining efficiency, as the system builds upon previous findings rather than restarting the entire analysis.

Inventive Principle:
Principle #20Continuity of useful action

4Manufacturing precision

If environment-specific vulnerability testing is conducted, then manufacturing precision is improved, but adaptability deteriorates

Engineering Contradiction:
Improvetesting specificityVSAvoidenvironmental adaptability
Core Design Contradiction:
Manufacturing precisionVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal vulnerability chain generation framework that can be applied across different target environments. The system uses generic vulnerability representations and standardized attack path models that adapt to various software configurations, eliminating the need for environment-specific testing procedures while maintaining precision through contextual analysis.

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

Data Source

PatentEP4189572B1Computer-implemented method for testing the cybersecurity of a target environment
Publication Date: 2026.02.11 INRIA INSTITUT NATIONAL DE RECHERCHE EN INFORMATIQUE ET EN AUTOMATIQUE
  • EP4189572B1 patent drawingFigure 1~3
  • EP4189572B1 patent drawingFigure 4

AI summary

A computer-implemented method for testing the cybersecurity of a target environment, comprising: a. receiving target environment data comprising software components, b. accessing a vulnerability database, and extracting a list of vulnerabilities comprising all the vulnerabilities associated with a component. c. compiling a list of vulnerability chains from the list of vulnerabilities: c.1. For each given vulnerability in the list of vulnerabilities, comparing the consequences of the current vulnerability with the means of the given vulnerability, c.2. When a similarity is found, c.2.i. Defining one or more new chains by adding the given vulnerability to each of the chains in the current list c.2.ii Adding the new chain(s) to the list of vulnerability chains, c.2.iii. Repeating the operations a. and b. with the given vulnerability as the current vulnerability, and the list of vulnerability chains as the current list.