# US 2012/0255017 A1 · System and method for providing a secured operating system execution environment

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

- Number: US 2012/0255017 A1
- Document ID: US20120255017A1
- Status: Published application
- Kind: A1
- Application number: 13/077,227
- 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/US20120255017A1

## CPC

- G06F 21/575: {Secure boot}
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 2009/45591: {Monitoring or debugging support}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In one embodiment, a system for launching a security architecture includes an electronic device comprising a processor and one or more operating systems, a security agent, and a launching module. The launching module comprises a boot manager and a secured launching agent. The boot manager is configured to boot the secured launching agent before booting the operating systems, and the secured launching agent is configured to load a security agent. The security agent is configured to execute at a level below all operating systems of the electronic device, intercept a request to access a resource of the electronic device, the request originating from the operational level of one of one or more operating systems of the electronic device, and determine if a request is indicative of malware. In some embodiments, the secured launching agent may be configured to determine whether the security agent is infected with malware prior to loading the security agent.

## Claims

### Claim 1

A system for launching a security architecture, comprising:
an electronic device comprising a processor and one or more operating systems;
a security agent configured to:
execute at a level below all operating systems of the electronic device accessing a resource;
intercept a request to access the resource of the electronic device, the request originating from the operational level of one of one or more operating systems of the electronic device; and
determine if the request is indicative of malware; and
a launching module comprising:
a secured launching agent configured to launch the security agent; and
a boot manager configured to boot the secured launching agent before booting the one or more operating systems.

### Claim 2 (depends on 1)

The system of claim 1, wherein the boot manager is further configured to replace an existing Master Boot Record with an alternate Master Boot Record prior to booting the secured launching agent, wherein the alternate Master Boot Record is configured to boot the secured launching agent.

### Claim 3 (depends on 1)

The system of claim 1, wherein the secured launching agent is further configured to determine whether the security agent is infected with malware prior to launching the security agent.

### Claim 4 (depends on 3)

The system of claim 3, wherein determining whether the security agent is infected with malware comprises determining whether one or more hash values associated with the security agent indicate that the security agent is infected with malware.

### Claim 5 (depends on 3)

The system of claim 3, wherein the secured launching agent is further configured to restore the security agent from a backup copy if the security agent is infected with malware.

### Claim 6 (depends on 1)

The system of claim 1, wherein the secured launching agent is further configured to determine whether any of the one or more operating systems are infected with malware.

### Claim 7 (depends on 1)

The system of claim 1, wherein the secured launching agent is further configured to determine whether the launching module is infected with malware.

### Claim 8 (depends on 1)

The system of claim 1, wherein the secured launching agent is further configured to create a backup copy of the security agent.

### Claim 9 (depends on 8)

The system of claim 8, wherein the security agent is further configured to update the backup copy of the security agent.

### Claim 10 (depends on 1)

The system of claim 1, wherein:
the resource is a storage device; and
the security agent configured to determine if the request is indicative of malware is configured to:
determine if the request involves a protected area of the storage device; and
if the request involves a protected area of the storage device, determine if the request is authorized.

### Claim 11 (depends on 10)

The system of claim 10, wherein the protected area includes one or more files associated with the security agent.

### Claim 12 (depends on 10)

The system of claim 10, wherein the protected area includes one or more files associated with the one or more operating systems.

### Claim 13 (depends on 10)

The system of claim 10, wherein the protected area includes a Master Boot Record.

### Claim 14 (depends on 10)

The system of claim 10, wherein the protected area includes one or more files associated with the launching module.

### Claim 15 (depends on 1)

The system of claim 1, wherein the security agent is further configured to utilize a disk mapping bitmap containing metadata corresponding to one or more files associated with the security agent.

### Claim 16 (depends on 15)

The system of claim 15, wherein the metadata specifies one or more sectors on a storage device where each of the one or more files are stored.

### Claim 17 (depends on 15)

The system of claim 15, wherein the metadata specifies a hash value for each of the one or more files for verifying the integrity of each of the one or more files.

### Claim 18 (depends on 1)

The system of claim 1:
further comprising a virtual machine monitor; and
wherein the security agent is executing in the virtual machine monitor.

### Claim 19 (depends on 1)

The system of claim 1, wherein:
the processor comprises microcode; and
the security agent is executing in the microcode.

### Claim 20 (depends on 1)

The system of claim 1, further comprising:
a storage device memory;
a storage device firmware residing in the storage device memory;
a disk security agent executing in the storage device firmware, the disk security agent configured to trap access to one or more protected files associated with the launching module; and
wherein the disk security agent is communicatively coupled to the security agent.

### Claim 21

A method for launching a security architecture, comprising:
booting a secured launching agent before booting one or more operating systems of an electronic device;
launching a security agent, wherein the security agent is configured to execute at a level below all of the one or more operating systems of the electronic device accessing the resource;
intercepting, by the security agent, a request to access the resource of the electronic device, the request originating from the operational level of one of the one or more operating systems of the electronic device; and
determining if the request is indicative of malware.

### Claim 22 (depends on 21)

The method of claim 21, further comprising replacing an existing Master Boot Record with an alternate Master Boot Record prior to booting the secured launching agent, wherein the alternate Master Boot Record is configured to boot the secured launching agent.

### Claim 23 (depends on 21)

The method of claim 21, further comprising determining whether the security agent is infected with malware prior to launching the security agent.

### Claim 24 (depends on 23)

The method of claim 23, wherein determining whether the security agent is infected with malware comprises determining whether one or more hash values associated with the security agent indicate that the security agent is infected with malware.

### Claim 25 (depends on 23)

The method of claim 23, further comprising restoring the security agent from a backup copy if the security agent is infected with malware.

### Claim 26 (depends on 21)

The method of claim 21, further comprising determining whether any of the one or more operating systems are infected with malware prior to booting any of the one or more operating systems.

### Claim 27 (depends on 21)

The method of claim 21, further comprising determining whether the secured launching agent is infected with malware.

### Claim 28 (depends on 21)

The method of claim 21, further comprising creating a backup copy of the security agent.

### Claim 29 (depends on 28)

The method of claim 28, further comprising updating the backup copy of the security agent.

### Claim 30 (depends on 21)

The method of claim 21, further comprising:
determining if the request involves a protected area of a storage device; and
if the request involves a protected area of the storage device, determining if the request is authorized.

### Claim 31 (depends on 30)

The method of claim 30, wherein the protected area includes one or more files associated with the security agent.

### Claim 32 (depends on 30)

The method of claim 30, wherein the protected area includes one or more files associated with the one or more operating systems.

### Claim 33 (depends on 30)

The method of claim 30, wherein the protected area includes a Master Boot Record.

### Claim 34 (depends on 30)

The method of claim 30, wherein the protected area includes one or more files associated with the secured launching agent.

### Claim 35 (depends on 21)

The method of claim 21, further comprising utilizing a disk mapping bitmap to determine if the security agent is infected with malware, wherein the disk mapping bitmap contains metadata corresponding to one or more files associated with the security agent.

### Claim 36 (depends on 35)

The method of claim 35, wherein the metadata specifies one or more sectors on a storage device where each of the one or more files are stored.

### Claim 37 (depends on 35)

The method of claim 35, wherein the metadata specifies a hash value for each of the one or more files for verifying the integrity of each of the one or more files.

### Claim 38 (depends on 21)

The method of claim 21, wherein the security agent is executing in a virtual machine monitor.

### Claim 39 (depends on 21)

The method of claim 21, wherein the security agent is executing in microcode of a processor of the electronic device.

### Claim 40 (depends on 21)

The method of claim 21, wherein the security agent is executing in firmware of a storage device.

### Claim 41

A non-transitory computer-readable medium encoded with logic, the logic, when executed by a processor, configured to:
boot a secured launching agent before booting one or more operating systems of an electronic device;
launch a security agent, wherein the security agent is configured to execute at a level below all of the one or more operating systems of the electronic device accessing the resource;
intercept, by the security agent, a request to access the resource of the electronic device, the request originating from the operational level of one of the one or more operating systems of the electronic device; and
determine if the request is indicative of malware.

### Claim 42 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to replace an existing Master Boot Record with an alternate Master Boot Record prior to booting the secured launching agent, wherein the alternate Master Boot Record is configured to boot the secured launching agent.

### Claim 43 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to determine whether the security agent is infected with malware prior to launching the security agent.

### Claim 44 (depends on 43)

The computer-readable medium of claim 43, wherein determining whether the security agent is infected with malware comprises determining whether one or more hash values associated with the security agent indicate that the security agent is infected with malware.

### Claim 45 (depends on 43)

The computer-readable medium of claim 43, wherein the logic is further configured to restore the security agent from a backup copy if the security agent is infected with malware.

### Claim 46 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to determine whether any of the one or more operating systems are infected with malware prior to booting any of the one or more operating systems.

### Claim 47 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to determine whether the secured launching agent is infected with malware.

### Claim 48 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to create a backup copy of the security agent.

### Claim 49 (depends on 48)

The computer-readable medium of claim 48, wherein the logic is further configured to update the backup copy of the security agent.

### Claim 50 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to:
determine if the request involves a protected area of a storage device; and
if the request involves a protected area of the storage device, determine if the request is authorized.

### Claim 51 (depends on 50)

The computer-readable medium of claim 50, wherein the protected area includes one or more files associated with the security agent.

### Claim 52 (depends on 50)

The computer-readable medium of claim 50, wherein the protected area includes one or more files associated with the one or more operating systems.

### Claim 53 (depends on 50)

The computer-readable medium of claim 50, wherein the protected area includes a Master Boot Record.

### Claim 54 (depends on 50)

The computer-readable medium of claim 50, wherein the protected area includes one or more files associated with the secured launching agent.

### Claim 55 (depends on 41)

The computer-readable medium of claim 41, wherein the logic is further configured to utilize a disk mapping bitmap to determine if the security agent is infected with malware, wherein the disk mapping bitmap contains metadata corresponding to one or more files associated with the security agent.

### Claim 56 (depends on 55)

The computer-readable medium of claim 55, wherein the metadata specifies one or more sectors on a storage device where each of the one or more files are stored.

### Claim 57 (depends on 55)

The computer-readable medium of claim 55, wherein the metadata specifies a hash value for each of the one or more files for verifying the integrity of each of the one or more files.

### Claim 58 (depends on 41)

The computer-readable medium of claim 41, wherein the security agent is executing in a virtual machine monitor.

### Claim 59 (depends on 41)

The computer-readable medium of claim 41, wherein the security agent is executing in microcode of a processor of the electronic device.

### Claim 60 (depends on 41)

The computer-readable medium of claim 41, wherein the security agent is executing in firmware of a storage device.
