Lookahead Signature Malware Detection Scheduling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing malware detection techniques are computationally intensive and impact system performance, particularly when applied during user interaction with computing devices, leading to delays in other system tasks.

Innovation Solution

A method that predicts usage patterns to schedule malware scans for executable files as low-priority background processes before they are needed, utilizing cached records to determine if a scan is necessary, thereby reducing the computational burden during peak usage times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If malware scans are performed during user interaction, then malware detection capability is maintained, but system performance deteriorates due to computational intensity

Engineering Contradiction:
Improvemalware detection capabilityVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs malware scans in advance of when files are actually needed by predicting future file usage based on historical patterns. Usage-based file lists are generated for future time periods, and scans are scheduled during preceding time periods when the system is less busy, completing the scanning work before the files are launched.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The scanning process is divided into segments based on predicted usage patterns. Instead of scanning all files uniformly, the system segments files into usage-based categories and schedules scans for specific time windows preceding their predicted execution, distributing the computational load across different time periods.

Inventive Principle:
Principle #1Segmentation

2Reliability

If malware scans are performed at application launch, then security is ensured, but task execution is delayed due to computational burden

Engineering Contradiction:
ImprovesecurityVSAvoidtask execution delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs malware scans in advance of when files are actually needed by predicting future file usage based on historical patterns. Usage-based file lists are generated for future time periods, and scans are scheduled during preceding time periods when the system is less busy, completing the scanning work before the files are launched.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If computational resources are concentrated during peak usage, then malware detection thoroughness is improved, but system responsiveness deteriorates

Engineering Contradiction:
Improvemalware detection thoroughnessVSAvoidsystem responsiveness
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs malware scans in advance of when files are actually needed by predicting future file usage based on historical patterns. Usage-based file lists are generated for future time periods, and scans are scheduled during preceding time periods when the system is less busy, completing the scanning work before the files are launched.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts scanning schedules based on predicted system usage patterns. By analyzing historical data, the system identifies when files are likely to be used and schedules scans during preceding periods when system responsiveness is less critical, creating a dynamic balance between security and user experience.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11586732B2Lookahead signature-based malware detection
Publication Date: 2023.02.21 MALWAREBYTES INC
  • US11586732B2 patent drawing
  • US11586732B2 patent drawing
  • US11586732B2 patent drawing

AI summary

A computing device determines, for a first time period, a usage-based file list identifying one or more executable files. The computing device determines, for each of the one or more executable files identified by the usage-based file list, whether to perform a malware scan upon the executable file based on a cached record for the executable file. The computing device schedules, for execution during a preceding time period before the first time period, a malware scan for at least one of the one or more executable files based on the corresponding determination of whether to perform a malware scan. Each scheduled malware scan is initiated as a low priority thread for execution. The computing device performs each scheduled malware scan during the preceding time period.