# US 2012/0254995 A1 · System and method for below-operating system trapping and securing loading of code into memory

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254995 A1
- Document ID: US20120254995A1
- Status: Published application
- Kind: A1
- Application number: 13/076,480
- Filed: 2011-03-31
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: McAfee, Inc.
- Inventors: Ahmed Said Sallam
- Web page: https://patentgrep.com/patent/US20120254995A1

## CPC

- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/554: {involving event detection and direct action}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system for protecting an electronic device against malware includes a memory, an operating system configured to execute on the electronic device, and a below-operating-system security agent. The below-operating-system security agent is configured to trap an attempted access of a resource of the electronic device, access one or more security rules to determine whether the attempted access is indicative of malware, and operate at a level below all of the operating systems of the electronic device accessing the memory. The attempted access includes attempting to write instructions to the memory and attempting to execute the instructions.

## Claims

### Claim 1

A system for protecting an electronic device against malware, comprising:
a memory;
an operating system configured to execute on the electronic device;
a below-operating-system security agent configured to:
trap an attempted access of a resource of the electronic device, the attempted access comprising:
attempting to write instructions to the memory; and
attempting to execute the instructions;
access one or more security rules to determine whether the attempted access is indicative of malware; and
operate at a level below all of the operating systems of the electronic device accessing the memory.

### Claim 2 (depends on 1)

The system of claim 1, wherein trapping the attempted resource comprises further configuring the below-operating-system security agent to trap an attempt to allocate portions of the memory with enabled write permissions.

### Claim 3 (depends on 1)

The system of claim 1, wherein trapping the attempted resource comprises further configuring the below-operating-system security agent to trap an attempt to change permissions of the memory in which instructions were written.

### Claim 4 (depends on 1)

The system of claim 1, wherein determining whether the attempted access is indicative of malware comprises configuring the below-operating-system security agent to scan the instructions written to memory.

### Claim 5 (depends on 1)

The system of claim 1, wherein determining whether the attempted access is indicative of malware comprises determining the identify of an entity which made the attempted access.

### Claim 6 (depends on 1)

The system of claim 1, wherein trapping the attempted access comprises further configuring the below-operating-system security agent to trap an attempted access of a portion of the memory containing a memory page data structure entry for a driver, wherein the malware status of the driver is unknown.

### Claim 7 (depends on 1)

The system of claim 1, wherein trapping the attempted access comprises further configuring the below-operating-system security agent to trap an attempted access of a portion of the memory containing an unallocated virtual page of kernel space.

### Claim 8 (depends on 1)

The system of claim 1, wherein trapping the attempted access comprises further configuring the below-operating-system security agent to trap an attempted access of a portion of the memory containing an empty virtual page allocated by the operating system.

### Claim 9 (depends on 1)

The system of claim 1, wherein trapping the attempted access comprises further configuring the below-operating-system security agent to:
compare contents of a first memory page written to disk during a swap file write to the contents of a second memory page after a swap file read, the swap file read and swap file write corresponding to the same location identified by the operating system.

### Claim 10 (depends on 1)

The system of claim 1, wherein the below-operating system security agent is configured to:
allow the attempted writing of instructions; and
halt the attempted execution.

### Claim 11

A method for protecting an electronic device against malware, comprising:
trapping an attempted access of a resource of an electronic device, the attempted access comprising:
attempting to write instructions to a memory of the electronic device, the memory comprising the resource; and
attempting to execute the instructions;
accessing one or more security rules to determine whether the attempted access is indicative of malware;
wherein the trapping of the attempted access and determining whether the attempted access is indicative of malware is conducted at a level below all of the operating systems of the electronic device accessing the memory.

### Claim 12 (depends on 11)

The method of claim 11, wherein trapping the attempted resource comprises trapping an attempt to allocate portions of the memory with enabled write permissions.

### Claim 13 (depends on 11)

The method of claim 11, wherein trapping the attempted resource comprises trapping an attempt to change permissions of the memory in which instructions were written.

### Claim 14 (depends on 11)

The method of claim 11, wherein determining whether the attempted access is indicative of malware comprises scanning the instructions written to memory.

### Claim 15 (depends on 11)

The method of claim 11, wherein determining whether the attempted access is indicative of malware comprises determining the identify of an entity which made the attempted access.

### Claim 16 (depends on 11)

The method of claim 11, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing a memory page data structure entry for a driver, wherein the malware status of the driver is unknown.

### Claim 17 (depends on 11)

The method of claim 11, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing an unallocated virtual page of kernel space.

### Claim 18 (depends on 11)

The method of claim 11, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing an empty virtual page allocated by the operating system.

### Claim 19 (depends on 11)

The method of claim 11, wherein trapping the attempted access comprises:
comparing contents of a first memory page written to disk during a swap file write to the contents of a second memory page after a swap file read, the swap file read and swap file write corresponding to the same location identified by the operating system.

### Claim 20 (depends on 11)

The method of claim 11, further comprising:
allowing the attempted writing of instructions; and
halting the attempted execution.

### Claim 21

An article of manufacture, comprising:
a computer readable medium; and
computer-executable instructions carried on the computer readable medium, the instructions readable by a processor, the instructions, when read and executed, for causing the processor to:
trap an attempted access of a resource of an electronic device, the attempted access comprising:
attempting to write instructions to a memory of the electronic device, the memory comprising the resource; and
attempting to execute the instructions;
access one or more security rules to determine whether the attempted access is indicative of malware;
wherein the processor is configured to conduct the trapping of the attempted access and determining whether the attempted access is indicative of malware at a level below all of the operating systems of the electronic device accessing the memory.

### Claim 22 (depends on 21)

The article of claim 21, wherein trapping the attempted resource comprises trapping an attempt to allocate portions of the memory with enabled write permissions.

### Claim 23 (depends on 21)

The article of claim 21, wherein trapping the attempted resource comprises trapping an attempt to change permissions of the memory in which instructions were written.

### Claim 24 (depends on 21)

The article of claim 21, wherein determining whether the attempted access is indicative of malware comprises scanning the instructions written to memory.

### Claim 25 (depends on 21)

The article of claim 21, wherein determining whether the attempted access is indicative of malware comprises determining the identify of an entity which made the attempted access.

### Claim 26 (depends on 21)

The article of claim 21, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing a memory page data structure entry for a driver, wherein the malware status of the driver is unknown.

### Claim 27 (depends on 21)

The article of claim 21, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing an unallocated virtual page of kernel space.

### Claim 28 (depends on 21)

The article of claim 21, wherein trapping the attempted access comprises trapping an attempted access of a portion of the memory containing an empty virtual page allocated by the operating system.

### Claim 29 (depends on 21)

The article of claim 21, wherein trapping the attempted access comprises:
comparing contents of a first memory page written to disk during a swap file write to the contents of a second memory page after a swap file read, the swap file read and swap file write corresponding to the same location identified by the operating system.

### Claim 30 (depends on 21)

The article of claim 21, wherein the processor is further caused to:
allow the attempted writing of instructions; and
halt the attempted execution.
