Malicious Software Detection Module File Group Behavior Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security software is ineffective in detecting and blocking worms and other malicious software, especially those using polymorphism or metamorphism, and may not be practical for all computer systems, failing to prevent rapid spread and data destruction.

Innovation Solution

A malicious software detection module (MSDM) that monitors storage devices for suspicious software arrivals, tracks associated files, and prevents replication or malicious behavior by employing heuristics to identify and block malicious activity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If security software is installed to detect and block malicious software, then the ability to prevent worm infections is improved, but the complexity of the system increases and may fail to detect polymorphic or metamorphic malware

Engineering Contradiction:
Improveability to detect and block malicious softwareVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The security system divides the detection task into multiple components: a monitoring module that tracks file operations, a heuristic analysis module that evaluates suspicious behaviors, and a response module that takes corrective actions. This segmentation allows each component to specialize in specific detection tasks, improving overall reliability while managing complexity through modular design

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary analysis of software behavior by monitoring file operations and tracking file associations before malicious activity occurs. By establishing baseline behavior patterns and detecting deviations early, the system can prevent polymorphic and metamorphic malware from executing their harmful payloads, improving detection capability without requiring overly complex real-time analysis

Inventive Principle:
Principle #10Preliminary action

2Reliability

If security software is used to detect malicious software, then protection against known threats is improved, but the software may fail to detect previously unknown malicious software using polymorphism or metamorphism

Engineering Contradiction:
Improveprotection against known threatsVSAvoidability to detect unknown threats
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system employs dynamic heuristic analysis that adapts to different types of malware behavior. Instead of relying on static signatures, the monitoring module tracks file operations, creation patterns, and behavioral characteristics in real-time, allowing the system to detect both known and unknown threats based on their actual behavior rather than predefined patterns

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system implements feedback mechanisms where detected suspicious behaviors are analyzed and used to refine detection heuristics. The monitoring module continuously evaluates file operations and updates its understanding of malicious patterns, enabling the system to adapt to polymorphic and metamorphic variants that modify their code structure while maintaining harmful behavior patterns

Inventive Principle:
Principle #23Feedback

3Reliability

If security software is installed on all computer systems, then overall security coverage is improved, but it is not practical for certain computer systems

Engineering Contradiction:
Improvesecurity coverageVSAvoidpracticality of deployment
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The monitoring module operates autonomously on each computer system, independently tracking file operations and making local security decisions without requiring centralized management or complex configuration. This self-service approach simplifies deployment across diverse systems while maintaining consistent security monitoring, making the solution practical for widespread implementation

Inventive Principle:
Principle #25Self-service

4Measurement precision

If traditional security software is used to detect worms, then detection of known worms is improved, but the rapid spread of worms can still occur before detection

Engineering Contradiction:
Improvedetection accuracyVSAvoidtime for worm to spread
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system performs preliminary monitoring of file operations and tracks file associations before worms can complete their replication cycle. By detecting suspicious behavior patterns early in the infection process, the system prevents worms from spreading rapidly across the network, reducing the time loss while maintaining high detection accuracy through continuous behavioral analysis

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7594272B1Detecting malicious software through file group behavior
Publication Date: 2009.09.22 GEN DIGITAL INC
  • US7594272B1 patent drawing
  • US7594272B1 patent drawing
  • US7594272B1 patent drawing

AI summary

A malicious software detection module (MSDM) detects worms and other malicious software. The MSDM executes on a computer system connected to a network. The MSDM monitors a storage device of the computer system for the arrival of software from a suspicious portal. The MSDM designates such software as suspicious. The MSDM tracks the set of files that are associated with the suspicious software. If the files in the set individually or collectively engage in suspicious behavior, the MSDM declares the suspicious software malicious and prevents file replication and/or other malicious behavior.