# US 2012/0254994 A1 · System and method for microcode based anti-malware security

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

- Number: US 2012/0254994 A1
- Document ID: US20120254994A1
- Status: Published application
- Kind: A1
- Application number: 13/073,842
- Filed: 2011-03-28
- Published: 2012-10-04
- Earliest claimed: 2011-03-28
- Assignees: McAfee, Inc.
- Inventors: Ahmed Said Sallam
- Web page: https://patentgrep.com/patent/US20120254994A1

## CPC

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

## Abstract

A system for securing an electronic device includes a processor comprising microcode, a resource coupled to the processor, and a microcode security agent embodied the microcode. The microcode security agent is configured to intercept a communication and determine whether the communication is indicative of malware. The communication includes a request made of the resource or information generated from the resource.

## Claims

### Claim 1

A system for securing an electronic device, comprising:
a processor comprising microcode;
a resource coupled to the processor;
a microcode security agent embodied the microcode, the microcode security agent configured to:
intercept a communication, the communication comprising a request made of the resource or information generated from the resource; and
determine whether the communication is indicative of malware.

### Claim 2 (depends on 1)

The system of claim 1, wherein if the communication is indicative of malware, the microcode security agent is configured to deny the request or sending the information generated from the resource.

### Claim 3 (depends on 1)

The system of claim 1, wherein the resource comprises physical memory.

### Claim 4 (depends on 1)

The system of claim 1, wherein the resource comprises a processor flag.

### Claim 5 (depends on 1)

The system of claim 1, wherein the resource comprises a processor exception.

### Claim 6 (depends on 1)

The system of claim 1, wherein the resource comprises a register.

### Claim 7 (depends on 1)

The system of claim 1, wherein the resource comprises a processor interrupt.

### Claim 8 (depends on 1)

The system of claim 1, wherein:
the communication comprises a processor instruction; and
determining whether the communication is indicative of malware comprises evaluating whether the processor instruction is indicative of malware.

### Claim 9 (depends on 8)

The system of claim 8, wherein determining whether the communication is indicative of malware comprises evaluating whether a source address of the processor instruction is indicative of malware.

### Claim 10 (depends on 8)

The system of claim 8, wherein determining whether the communication is indicative of malware comprises evaluating whether a target address of the processor instruction is indicative of malware.

### Claim 11 (depends on 8)

The system of claim 8, wherein determining whether the communication is indicative of malware comprises evaluating whether an operand of the processor instruction is indicative of malware.

### Claim 12 (depends on 1)

The system of claim 1, further comprising:
a below-operating-system security agent communicatively coupled to the microcode security agent, wherein:
configuring the microcode security agent to determine whether the communication indicates malware comprises:
configuring the microcode security agent to send information to the security agent, the information comprising the communication; and
the below-operating-system security agent is configured to access one or more security rules to determine whether the information indicates malware.

### Claim 13 (depends on 12)

The system of claim 12, wherein the below-operating-system security agent is configured to operate within a bare metal layer of the electronic device.

### Claim 14 (depends on 12)

The system of claim 12, further comprising an operating system security agent running in an operating system of the system and communicatively coupled to the below-operating-system security agent, wherein the operating system security agent is configured to provide the security agent with information regarding one or more elements in the operating system associated with the communication.

### Claim 15 (depends on 12)

The system of claim 12, wherein the microcode security agent is configured to validate the security of the below-operating-system security agent.

### Claim 16 (depends on 12)

The system of claim 12, wherein:
the below-operating-system security agent is configured to execute at a level below all operating systems of the electronic device accessing the resource; and
the communication has a source or destination of a level above the below-operating-system security agent.

### Claim 17 (depends on 12)

The system of claim 12, wherein:
the below-operating-system security agent executes at a higher priority than all operating systems of the electronic device accessing the resource, such priority defined by the processor; and
the communication has a source or destination of an entity with less priority than the below-operating-system security agent.

### Claim 18 (depends on 12)

The system of claim 12, wherein:
the below-operating-system security agent executes on a more privileged ring of execution than all operating systems of the electronic device accessing the resource; and
the communication has a source or destination of a less privileged ring of execution than the below-operating-system security agent.

### Claim 19

A method for securing an electronic device, comprising:
using a microcode security agent embodied in microcode of a processor, intercepting a communication comprising a request made of a resource or information generated from the resource, the resource coupled to the processor;
consulting one or more security rules; and
based on the one or more security rules, determining whether the communication is indicative of malware.

### Claim 20 (depends on 19)

The method of claim 19, further comprising, if the communication is indicative of malware, denying the request or communication of the information.

### Claim 21 (depends on 19)

The method of claim 19, wherein the resource comprises physical memory.

### Claim 22 (depends on 19)

The method of claim 19, wherein the resource comprises a processor flag.

### Claim 23 (depends on 19)

The method of claim 19, wherein the resource comprises a processor exception.

### Claim 24 (depends on 19)

The method of claim 19, wherein the resource comprises a register.

### Claim 25 (depends on 19)

The method of claim 19, wherein the resource comprises a processor interrupt.

### Claim 26 (depends on 19)

The method of claim 19, wherein:
the communication comprises a processor instruction; and
determining whether the communication is indicative of malware comprises evaluating whether the processor instruction is indicative of malware.

### Claim 27 (depends on 26)

The method of claim 26, wherein determining whether the communication is indicative of malware comprises evaluating whether a source address of the processor instruction is indicative of malware.

### Claim 28 (depends on 26)

The method of claim 26, wherein determining whether the communication is indicative of malware comprises evaluating whether a target address of the processor instruction is indicative of malware.

### Claim 29 (depends on 26)

The method of claim 26, wherein determining whether the communication is indicative of malware comprises evaluating whether an operand of the processor instruction is indicative of malware.

### Claim 30 (depends on 19)

The method of claim 19, wherein determining whether the communication indicates malware comprises sending information to a below-operating-system security agent, the information comprising the communication, the security agent configured to access one or more security rules to determine whether the information indicates malware.

### Claim 31 (depends on 30)

The method of claim 30, wherein the longhorn security agent is configured to operate within a bare metal layer of the electronic device.

### Claim 32 (depends on 30)

The method of claim 30, further comprising:
communicating with an operating system security agent running in an operating system of the electronic device; and
receiving information regarding one or more elements in the operating system associated with the communication with the resource.

### Claim 33 (depends on 30)

The method of claim 30, further comprising validating the instance of the below-operating-system security agent.

### Claim 34 (depends on 30)

The method of claim 30, wherein:
the below-operating-system security agent is configured to execute at a level below all operating methods of the electronic device; and
the request is made from a level above the below-operating-system security agent.

### Claim 35 (depends on 30)

The method of claim 30, wherein:
the below-operating-system security agent is configured to execute at a higher priority than all operating systems of the electronic device accessing the resource, such priority defined by the processor; and
the request is made from an entity with less priority than the below-operating-system security agent.

### Claim 36 (depends on 30)

The method of claim 30, wherein:
the below-operating-system security agent is configured to execute on a more privileged ring of execution than all operating systems of the electronic device accessing the resource; and
the request is made from a less privileged ring of execution than the below-operating-system security agent.

### Claim 37

An article of manufacture comprising:
a computer readable medium; and
computer-executable microcode embodied in instructions carried on the computer readable medium, the instructions readable by a processor, the instructions, when read and executed, for causing the processor to:
using the microcode instructions, intercept a communication, the communication comprising a request made of a resource or information generated from the resource, the resource coupled to the processor;
consult one or more security rules; and
based on the one or more security rules, determine whether the communication is indicative of malware.

### Claim 38 (depends on 37)

The article of claim 37, wherein the processor is further caused to:
if the request is indicative of malware, deny the request or communication of the information.

### Claim 39 (depends on 37)

The article of claim 37, wherein the resource comprises physical memory.

### Claim 40 (depends on 37)

The article of claim 37, wherein the resource comprises a processor flag.

### Claim 41 (depends on 37)

The article of claim 37, wherein the resource comprises physical memory.

### Claim 42 (depends on 37)

The article of claim 37, wherein the resource comprises a processor exception.

### Claim 43 (depends on 37)

The article of claim 37, wherein the resource comprises a register.

### Claim 44 (depends on 37)

The article of claim 37, wherein the resource comprises a processor interrupt.

### Claim 45 (depends on 37)

The article of claim 37, wherein:
the communication comprises a processor instruction; and
determining whether the communication is indicative of malware comprises causing the processor to evaluate whether the processor instruction is indicative of malware.

### Claim 46 (depends on 37)

The article of claim 37, wherein determining whether the communication is indicative of malware comprises causing the processor to evaluate whether a source address of the processor instruction is indicative of malware.

### Claim 47 (depends on 37)

The article of claim 37, wherein determining whether the communication is indicative of malware comprises causing the processor to evaluate whether a target address of the processor instruction is indicative of malware.

### Claim 48 (depends on 37)

The article of claim 37, wherein determining whether the communication is indicative of malware comprises causing the processor to evaluate whether an operand of the processor instruction is indicative of malware.

### Claim 49 (depends on 37)

The article of claim 37, wherein determining whether the communication is indicative of malware comprises causing the processor to send information to a below-operating-system security agent, the information comprising the communication, the below-operating-system security agent configured to access one or more security rules to determine whether the information indicates malware.

### Claim 50 (depends on 49)

The article of claim 49, further comprising causing the processor to validate the instance of the below-operating-system security agent.

### Claim 51 (depends on 49)

The article of claim 49, wherein:
the below-operating-system security agent is configured to execute at a level below all operating methods of the electronic device; and
the request is made from a level above the below-operating-system security agent.

### Claim 52 (depends on 49)

The article of claim 49, wherein:
the below-operating-system security agent is configured to execute at a higher priority than all operating systems of the electronic device accessing the resource, such priority defined by the processor; and
the request is made from an entity with less priority than the below-operating-system security agent.

### Claim 53 (depends on 49)

The article of claim 49, wherein:
the below-operating-system security agent is configured to execute on a more privileged ring of execution than all operating systems of the electronic device accessing the resource; and
the request is made from a less privileged ring of execution than the below-operating-system security agent.
