Virtual Container Code Analysis via Hash Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional security systems often fail to prevent harmful code from spreading across networks and require costly, time-consuming measures that hinder organizational operations.

Innovation Solution

A security system utilizing virtual containers and hashing technology to analyze suspicious information, where hashes are compared to stored lists to quickly identify harmful or acceptable information, and if unknown, the information is analyzed within a secure virtual environment to prevent spread and log actions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional security systems are used to identify harmful code, then harmful code can be detected, but harmful code may spread to other systems and expensive, time-consuming measures are required

Engineering Contradiction:
Improveharmful code detection accuracyVSAvoidanalysis time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system creates hash values of suspicious code in advance and stores them in a database before actual analysis is needed. When new suspicious code is detected, its hash is compared against the pre-stored hashes to quickly determine if it is harmful, eliminating the need for time-consuming re-analysis of the same code

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of analyzing the actual suspicious code multiple times, the system creates and stores a hash copy (digital fingerprint) of the code. This hash copy serves as a lightweight representation that can be rapidly compared without requiring full code analysis, significantly reducing processing time while maintaining detection accuracy

Inventive Principle:
Principle #26Copying

2Object-affected harmful factors

If traditional security systems implement restrictive measures to prevent harmful code spread, then harmful code propagation is reduced, but organizational operations are hampered

Engineering Contradiction:
Improveharmful code spread preventionVSAvoidorganizational operations
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The system introduces a virtual container as an intermediary environment between the suspicious code and the actual organizational systems. The code is executed and analyzed within this isolated container, allowing security verification without direct interaction with production systems. This enables operations to continue normally while maintaining security controls

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If full analysis of suspicious information is performed without hashing, then accurate identification is achieved, but analysis burden increases and time is consumed

Engineering Contradiction:
Improvesuspicious information identification accuracyVSAvoidanalysis efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system performs a partial analysis by first comparing only the hash values before conducting full code analysis. This two-stage approach applies minimal necessary action (hash comparison) to filter out obvious matches, reserving comprehensive analysis only for cases where hash matching fails, thereby optimizing the balance between accuracy and efficiency

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11269991B2System for identifying suspicious code in an isolated computing environment based on code characteristics
Publication Date: 2022.03.08 BANK OF AMERICA CORP
  • US11269991B2 patent drawing
  • US11269991B2 patent drawing
  • US11269991B2 patent drawing

AI summary

Providing an isolation system that allows analysts to analyze suspicious information in way that aids in preventing harmful information from spreading to other applications and systems on a network. A plurality of virtual containers may be used by analysts to analyze suspicious information. The suspicious information may first be hashed before being analyzed by the analyst. The hash for the suspicious information may be compared to stored hashes. When the hash meets a stored harmful hash the suspicious information may be determined to include harmful information without having to be further analyzed. When the hash meets a stored acceptable hash the suspicious information may be determined to be acceptable information without having to be further analyzed. Should the hash for the suspicious information fail to meet any stored hashes, then the suspicious information may be analyzed for harmful information within the virtual container.