Software Identification via Behavioral Scoring and Signature Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security programs are ineffective in detecting malicious software applications due to their reliance on filename scans or file signatures, which can be evaded through polymorphism and other evasion techniques, making it difficult to identify and classify potentially harmful software.

Innovation Solution

A method that monitors software application instances by matching operations performed against pre-defined application signatures, with a scoring system to classify applications based on their behavior, allowing for dynamic and environment-specific actions to be taken, such as terminating or quarantining the application.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If filename scans or file signatures are used for detection, then the detection method is simple to implement, but the detection effectiveness deteriorates due to polymorphism and evasion techniques

Engineering Contradiction:
Improveease of implementationVSAvoiddetection effectiveness
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

Instead of detecting malware by its static identity (filename, signature), the patent inverts the approach by detecting what the program is NOT - i.e., detecting legitimate program behavior and identifying anything that deviates from expected behavior patterns as potentially malicious

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent changes the detection parameters from static file attributes (filename, hash signature) to dynamic operational parameters (operations performed, sequences of actions, behavior patterns), making detection resistant to polymorphism since the behavior signature remains consistent even when the file changes

Inventive Principle:
Principle #35Parameter changes

2Reliability

If behavior monitoring with scoring system is implemented, then detection reliability improves, but device complexity increases

Engineering Contradiction:
Improvedetection effectivenessVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the behavior monitoring into discrete, manageable components: individual operations are identified and assigned weights, sequences of operations are tracked independently, and scoring is performed modularly for each application, making the complex system easier to implement and maintain

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The behavior monitoring system is designed to be universal, applying the same operation-tracking and scoring mechanism across all applications regardless of type or source, eliminating the need for separate detection systems for different threat types

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

Data Source

PatentUS9531740B2Software program identification based on program behavior
Publication Date: 2016.12.27 IBOSS INC
  • US9531740B2 patent drawing
  • US9531740B2 patent drawing
  • US9531740B2 patent drawing

AI summary

Operations performed by a software application instance executed by a computing device are monitored. A determination is made that a particular operation performed matches an application signature representing a particular software application. In response, a match score is added to a total score for the software application. In response to determining that the total score is greater than or equal to a threshold, the software is classified.