# US 2012/0255003 A1 · System and method for securing access to the objects of an operating system

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

- Number: US 2012/0255003 A1
- Document ID: US20120255003A1
- Status: Published application
- Kind: A1
- Application number: 13/076,537
- 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/US20120255003A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a system for protecting an electronic device against malware includes an object-oriented operating system configured to execute on the electronic device and a below-operating-system security agent. The below-operating-system security agent may be configured to trap an attempted access of an object manager of the operating system, 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. In some embodiments, the below-operating-system security agent may determine whether the attempted access is indicative of malware by comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

## Claims

### Claim 1

A system for protecting an electronic device against malware, comprising:
an object-oriented operating system configured to execute on the electronic device;
a below-operating-system security agent configured to:
trap an attempted access of an object manager of the operating system;
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 object manager.

### Claim 2 (depends on 1)

The system of claim 1, wherein:
the below-operating system security agent is further configured to determine the entity that attempted to access the object manager; and
determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 3 (depends on 1)

The system of claim 1, wherein the attempted access of the object manager includes an attempted access of a subfunction of the object manager.

### Claim 4 (depends on 3)

The system of claim 3, wherein the below-operating system security agent is further configured to determine whether the attempted access of the subfunction was made by circumventing the object manager.

### Claim 5 (depends on 1)

The system of claim 1, wherein the below-operating system security agent is further configured to update a behavioral state map to reflect the attempted access.

### Claim 6 (depends on 1)

The system of claim 1, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 7

A system for protecting an electronic device against malware, comprising:
an object-oriented operating system configured to execute on the electronic device;
a below-operating-system security agent configured to:
trap an attempted access of an object of the operating system;
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 object.

### Claim 8 (depends on 7)

The system of claim 7, wherein the below-operating-system security agent is further configured to trap an attempted access of a function of the object.

### Claim 9 (depends on 8)

The system of claim 8, wherein:
the below-operating system security agent is further configured to determine the caller of the object function; and
determining whether the attempted access is indicative of malware comprises evaluating the caller of the function.

### Claim 10 (depends on 7)

The system of claim 7, wherein the below-operating-system security agent is further configured to trap an attempted access of a data structure of the object.

### Claim 11 (depends on 10)

The system of claim 10, wherein:
the below-operating system security agent is further configured to determine the entity that attempted to access the object data structure; and
determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 12 (depends on 7)

The system of claim 7, wherein the below-operating system security agent is further configured to update a behavioral state map to reflect the attempted access.

### Claim 13 (depends on 7)

The system of claim 7, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 14

A system for protecting an electronic device against malware, comprising:
an object-oriented operating system configured to execute on the electronic device;
a below-operating-system security agent configured to:
trap an attempted access of an object manager of the operating system;
trap an attempted generation of one or more objects of the operating system;
trap an attempted access of one or more object functions of the one or more objects;
build a behavioral state map of the trapped actions of the object manager and the one or more objects; and
operate at a level below all of the operating systems of the electronic device accessing the object manager.

### Claim 15

A method for protecting an electronic device against malware, comprising:
trapping an attempted access of an object manager of an operating system; and
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 object manager.

### Claim 16 (depends on 15)

The method of claim 15:
further comprising determining the entity that attempted to access the object manager; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 17 (depends on 15)

The method of claim 15, wherein the attempted access of the object manager includes an attempted access of a subfunction of the object manager.

### Claim 18 (depends on 17)

The method of claim 17, further comprising determining whether the attempted access of the subfunction was made by circumventing the object manager.

### Claim 19 (depends on 15)

The method of claim 15, further comprising updating a behavioral state map to reflect the attempted access.

### Claim 20 (depends on 15)

The method of claim 15, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 21

A method for protecting an electronic device against malware, comprising:
trapping an attempted access of an object of an operating system; and
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 object.

### Claim 22 (depends on 21)

The method of claim 21, further comprising trapping an attempted access of a function of the object.

### Claim 23 (depends on 22)

The method of claim 22:
further comprising determining the caller of the object function; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the caller of the function.

### Claim 24 (depends on 21)

The method of claim 21, further comprising trapping an attempted access of a data structure of the object.

### Claim 25 (depends on 24)

The method of claim 24:
further comprising determining the entity that attempted to access the object data structure; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 26 (depends on 21)

The method of claim 21, further comprising updating a behavioral state map to reflect the attempted access.

### Claim 27 (depends on 21)

The method of claim 21, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 28

A method for protecting an electronic device against malware, comprising:
trapping an attempted access of an object manager of an operating system;
trapping an attempted generation of one or more objects of the operating system;
trapping an attempted access of one or more object functions of the one or more objects; and
building a behavioral state map of the trapped actions of the object manager and the one or more objects;
wherein the trapping is conducted at a level below all of the operating systems of the electronic device accessing the object manager.

### Claim 29

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 an object manager of an operating system; and
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 object manager.

### Claim 30 (depends on 29)

The article of claim 29:
the instructions further for causing the processor to determine the entity that attempted to access the object manager; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 31 (depends on 29)

The article of claim 29, wherein the attempted access of the object manager includes an attempted access of a subfunction of the object manager.

### Claim 32 (depends on 31)

The article of claim 31, the instructions further for causing the processor to determine whether the attempted access of the subfunction was made by circumventing the object manager.

### Claim 33 (depends on 29)

The article of claim 29, the instructions further for causing the processor to update a behavioral state map to reflect the attempted access.

### Claim 34 (depends on 29)

The article of claim 29, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 35

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 an object of an operating system; and
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 object.

### Claim 36 (depends on 35)

The article of claim 35, the instructions further for causing the processor to trap an attempted access of a function of the object.

### Claim 37 (depends on 36)

The article of claim 36:
the instructions further for causing the processor to determine the caller of the object function; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the caller of the function.

### Claim 38 (depends on 35)

The article of claim 35, the instructions further for causing the processor to trap an attempted access of a data structure of the object.

### Claim 39 (depends on 38)

The article of claim 38:
the instructions further for causing the processor to determine the entity that attempted to access the object data structure; and
wherein determining whether the attempted access is indicative of malware comprises evaluating the entity.

### Claim 40 (depends on 35)

The article of claim 35, the instructions further for causing the processor to update a behavioral state map to reflect the attempted access.

### Claim 41 (depends on 35)

The article of claim 35, wherein determining whether the attempted access is indicative of malware comprises comparing the attempted access to a behavioral state map to determine if the attempted access represents behavior associated with malware.

### Claim 42

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 an object manager of an operating system;
trap an attempted generation of one or more objects of the operating system;
trap an attempted access of one or more object functions of the one or more objects; and
build a behavioral state map of the trapped actions of the object manager and the one or more objects;
wherein the processor is configured to conduct the trapping at a level below all of the operating systems of the electronic device accessing the object manager.
