Containerized Application Vulnerability Mitigation via Process Dependency Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for mitigating security vulnerabilities in containerized applications are inefficient, often requiring manual analysis and resource-intensive processes, and are prone to addressing false positives, which can be costly and time-consuming.

Innovation Solution

A method that identifies main processes in a containerized application, determines dependent and non-dependent processes, and generates a mitigated image by removing or mitigating non-dependent vulnerable processes within a sandbox environment, using additional layers to block or delete vulnerable components without affecting the main process, thereby automating vulnerability mitigation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual analysis and resource-intensive processes are used to mitigate vulnerabilities, then vulnerability mitigation can be performed, but the process is inefficient and time-consuming

Engineering Contradiction:
Improvevulnerability mitigation effectivenessVSAvoidmitigation process efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system automatically performs vulnerability mitigation by identifying main processes, determining process dependencies, and removing vulnerable non-dependent processes without requiring manual intervention. The automated image analysis and mitigation generation enables the system to service itself, eliminating the need for manual security analysis while maintaining effective vulnerability mitigation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary vulnerability assessment and process dependency analysis before deploying the containerized application. By pre-identifying main processes, determining dependencies, and generating mitigation strategies in advance, the system prepares the application environment proactively, preventing vulnerabilities from being introduced during deployment while maintaining high efficiency.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual vulnerability analysis is performed, then vulnerabilities can be identified and addressed, but false positives require additional manual review which is costly and time-consuming

Engineering Contradiction:
Improvevulnerability identification accuracyVSAvoidtime for manual review
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically distinguishes between false positives and real vulnerabilities by analyzing process dependencies. The automated determination of which processes are dependent on main processes versus independent allows the system to self-evaluate vulnerability significance, eliminating the need for manual false positive review while maintaining high identification accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system uses feedback from process dependency analysis to automatically adjust vulnerability assessment. By continuously analyzing which processes are essential to the application's main functionality and which are independent, the system refines its vulnerability identification accuracy, automatically filtering out false positives without requiring manual verification.

Inventive Principle:
Principle #23Feedback

3Reliability

If all vulnerable processes are removed from containerized applications, then security is improved, but essential dependent processes may be accidentally removed affecting application functionality

Engineering Contradiction:
Improvesecurity improvementVSAvoidapplication functionality preservation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system segments processes into three categories: main processes, dependent processes, and independent processes. By dividing the process landscape this way, the system can selectively apply mitigation only to independent vulnerable processes while preserving dependent and main processes, thereby improving security without compromising application functionality.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different quality characteristics to different process segments. Main and dependent processes receive protection and are preserved regardless of vulnerability status, while only independent processes undergo vulnerability-based removal. This localized approach ensures security improvements are applied precisely where safe, maintaining application functionality while enhancing security.

Inventive Principle:
Principle #3Local quality

4Productivity

If automated vulnerability mitigation is implemented, then manual intervention is reduced and resources are saved, but the system complexity increases

Engineering Contradiction:
Improveresource efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The automated mitigation system performs multiple functions within a single unified framework: it identifies main processes, determines process dependencies, assesses vulnerabilities, generates mitigations, and applies them automatically. This multi-functional approach consolidates what would otherwise require multiple separate tools and manual steps into one system, reducing overall complexity while maintaining high resource efficiency.

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

Data Source

PatentUS11556655B2Automatic vulnerability mitigation
Publication Date: 2023.01.17 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11556655B2 patent drawing
  • US11556655B2 patent drawing
  • US11556655B2 patent drawing

AI summary

An image for a containerized application is created. From the image, one or more main processes of the containerized application are identified. The one or more main processes comprise a first subset of a plurality of processes of the containerized application. Within a sandbox environment, the containerized application is started. Based on the started application within the sandbox environment, a second subset of processes within the plurality is determined. The second subset includes one or more dependent processes associated with the first subset. A third subset of processes within the plurality is determined. The third subset excludes the first and second subsets and is associated with a vulnerability list. According to the third subset, a mitigated image for the containerized application is generated.