# US 2012/0255000 A1 · System and method for below-operating system trapping and securing of interdriver communication

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

- Number: US 2012/0255000 A1
- Document ID: US20120255000A1
- Status: Published application
- Kind: A1
- Application number: 13/075,072
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: McAfee, Inc.
- Inventors: Ahmed Said Sallam
- Web page: https://patentgrep.com/patent/US20120255000A1

## CPC

- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, 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 by a first driver of the operating system of a second driver 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 second driver.

## 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 by a first driver of the operating system of a second driver 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 second driver.

### Claim 2 (depends on 1)

The system of claim 1, wherein determining whether the attempted access is indicative of malware comprises:
determining and considering an identity of the first driver; and
if a security status of the first driver is unknown, determining that the attempted access is indicative of malware.

### Claim 3 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted direct access of a code section of the second driver by bypassing functions provided by the first kernel module or the operating system.

### Claim 4 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted installation of a callback routine.

### Claim 5 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted access of an address from an export table of the second driver.

### Claim 6 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted access of a data section of the second driver.

### Claim 7 (depends on 6)

The system of claim 6, wherein the attempted access includes an attempted access of information about a third driver communicatively coupled to the second driver.

### Claim 8 (depends on 7)

The system of claim 7, wherein the attempted access includes an attempted access of an address from an import table of the second driver, the import table containing information regarding the third driver.

### Claim 9 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted hooking of a function of the second driver.

### Claim 10 (depends on 1)

The system of claim 1, wherein the attempted access includes an input-output request packet sent to the second driver.

### Claim 11 (depends on 1)

The system of claim 1, wherein the attempted access includes an attempted write to a code section of the second driver.

### Claim 12

A method for protecting an electronic device against malware, comprising:
trapping an attempted access by a first driver of the operating system of a second driver of the electronic device;
accessing one or more security rules; and
determining, based on the one or more security rules, 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 are conducted at a level below all of the operating systems of the electronic device accessing the second driver.

### Claim 13 (depends on 12)

The method of claim 12, wherein determining whether the attempted access is indicative of malware comprises:
determining and considering an identity of the first driver; and
if a security status of the first driver is unknown, determining that the attempted access is indicative of malware.

### Claim 14 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted direct access of a code section of the second driver by bypassing functions provided by the first kernel module or the operating system.

### Claim 15 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted installation of a callback routine.

### Claim 16 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted access of an address from an export table of the second driver.

### Claim 17 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted access of a data section of the second driver.

### Claim 18 (depends on 17)

The method of claim 17, wherein the attempted access includes an attempted access of information about a third driver communicatively coupled to the second driver.

### Claim 19 (depends on 18)

The method of claim 18, wherein the attempted access includes an attempted access of an address from an import table of the second driver, the import table containing information regarding the third driver.

### Claim 20 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted hooking of a function of the second driver.

### Claim 21 (depends on 12)

The method of claim 12, wherein the attempted access includes an input-output request packet sent to the second driver.

### Claim 22 (depends on 12)

The method of claim 12, wherein the attempted access includes an attempted write to a code section of the second driver.

### Claim 23

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 by a first driver of the operating system of a second driver of the electronic device;
access one or more security rules; and
determine, based on the one or more security rules, 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 second driver.

### Claim 24 (depends on 23)

The article of claim 23, wherein causing the processor to determine whether the attempted access is indicative of malware comprises causing the processor to:
determine and considering an identity of the first driver; and
if a security status of the first driver is unknown, determine that the attempted access is indicative of malware.

### Claim 25 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted direct access of a code section of the second driver by bypassing functions provided by the first kernel module or the operating system.

### Claim 26 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted installation of a callback routine.

### Claim 27 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted access of an address from an export table of the second driver.

### Claim 28 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted access of a data section of the second driver.

### Claim 29 (depends on 28)

The article of claim 28, wherein the attempted access includes an attempted access of information about a third driver communicatively coupled to the second driver.

### Claim 30 (depends on 29)

The article of claim 29, wherein the attempted access includes an attempted access of an address from an import table of the second driver, the import table containing information regarding the third driver.

### Claim 31 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted hooking of a function of the second driver.

### Claim 32 (depends on 23)

The article of claim 23, wherein the attempted access includes an input-output request packet sent to the second driver.

### Claim 33 (depends on 23)

The article of claim 23, wherein the attempted access includes an attempted write to a code section of the second driver.
