Below-OS Security Agent for Malware Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional anti-malware security techniques are limited in detecting and neutralizing self-modifying malware, as they operate within the same execution priority as the operating system, making them susceptible to evasion by kernel mode malware, which can hide its presence and modify itself to avoid detection.

Innovation Solution

Implementing a below-operating system security agent that traps and analyzes memory accesses to detect suspicious behavior, records access history, and modifies malicious code to prevent its execution, operating at a higher priority than the operating system to avoid malware detection evasion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional anti-malware security techniques operate within the operating system kernel level, then they can access and modify malware processes, but they become susceptible to evasion by kernel mode malware that operates at the same execution priority

Engineering Contradiction:
Improvedetection capabilityVSAvoidmalware evasion
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent transitions the security agent from operating at the same execution priority level as the operating system (kernel mode) to operating below it (firmware or hypervisor level). This dimensional change in execution priority creates a hierarchical advantage where the security agent can observe and control malware processes without being subject to the same evasion techniques that work at the kernel level.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The security agent performs preliminary actions by establishing its monitoring and control mechanisms before malware can execute its evasion tactics. By operating at a lower execution priority level, the agent can trap and log memory access attempts before the malware has opportunity to modify itself or detect the security measures.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If security software filters all behaviors of an electronic device, then it can detect malicious actions, but it consumes significant system resources and may interfere with normal operations

Engineering Contradiction:
Improvemalware detectionVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The security agent applies local quality by focusing its monitoring efforts on specific memory access patterns and behaviors that are indicative of malware activity, rather than filtering all device behaviors uniformly. This targeted approach allows effective malware detection while minimizing interference with normal system operations.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The security agent acts as an intermediary layer between the hardware and the operating system, intercepting and analyzing memory access attempts. This intermediary position allows it to detect malicious behavior without requiring direct intervention in all system operations, thereby maintaining system performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If malware modifies its binary components to avoid detection, then it can escape signature-based detection, but it requires additional mechanisms to dynamically change its code

Engineering Contradiction:
Improvemalware evasion capabilityVSAvoiddetection complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The security agent implements feedback mechanisms by continuously monitoring memory access patterns and comparing them against known malware behaviors. When suspicious patterns are detected, the agent can respond by blocking the modification attempts or alerting the system, creating a feedback loop that adapts to evolving malware techniques without requiring complex signature updates.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent replaces traditional mechanical signature-based detection with a behavioral analysis approach. Instead of relying on static binary signatures that malware can easily bypass, the system monitors dynamic memory access patterns and behaviors, substituting the mechanical signature matching process with more sophisticated behavioral observation that is harder for malware to evade.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Reliability

If anti-malware applications use operating system functions to erase or neutralize malware, then they can remove threats, but sophisticated malware can detect and track these techniques to avoid neutralization

Engineering Contradiction:
Improvemalware neutralizationVSAvoidanti-malware effectiveness
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

The security agent operates from a different dimensional level (below the operating system) when neutralizing malware. This allows it to erase or block malicious code without triggering the detection mechanisms that malware has prepared to counter operating system-level anti-malware functions. The neutralization action occurs in a different execution context that malware cannot easily monitor or respond to.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8925089B2System and method for below-operating system modification of malicious code on an electronic device
Publication Date: 2014.12.30 MCAFEE LLC
  • US8925089B2 patent drawing
  • US8925089B2 patent drawing
  • US8925089B2 patent drawing

AI summary

A system for securing an electronic device, may include a memory, a processor, one or more operating systems residing in the memory for execution by the processor; and a security agent configured to execute on the electronic device at a level below all of the operating systems of the electronic device accessing the memory. The security agent may be further configured to detect presence of malicious code, and in response to detecting presence of the malicious code, modify the malicious code.