# US 2017/0286701 A1 · Secure driver platform

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

- Number: US 2017/0286701 A1
- Document ID: US20170286701A1
- Status: Published application
- Kind: A1
- Application number: 15/087,515
- Filed: 2016-03-31
- Published: 2017-10-05
- Earliest claimed: 2016-03-31
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Minsang Kim; Kumar Rajeev; Jason S. Wohlgemuth; Aacer H. Daken; Peter Wieland
- Web page: https://patentgrep.com/patent/US20170286701A1

## CPC

- G06F 21/606: {by securing the transmission between two devices or processes}
- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/74: operating in dual or compartmented mode, i.e. at least one secure mode
- G06F 2221/2113: Multi-level security, e.g. mandatory access control
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques described herein enable the implementation of a secure driver framework. In one example, a method includes managing an unsecure operating system execution environment comprising a first user mode and a first kernel mode. The method can also include managing a secure execution environment comprising a second user mode and a second kernel mode, and executing a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode, wherein the secure driver enables the unsecure driver to communicate with a secure device. Furthermore, the method can include providing one or more system services of the second kernel mode to the secure driver.

## Claims

### Claim 1

A system for providing a secure driver framework comprising:
a processor to:
manage an unsecure operating system execution environment comprising a first user mode and a first kernel mode;
manage a secure execution environment comprising a second user mode and a second kernel mode;
execute a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode; and
provide one or more system services of the second kernel mode to the secure driver.

### Claim 2 (depends on 1)

The system of claim 1, wherein the unsecure driver transmits the system call to the secure driver via a remote procedure call.

### Claim 3 (depends on 1)

The system of claim 1, wherein the processor is to enumerate a secure device by creating a secure device node and loading the secure driver in the second user mode of the secure execution environment.

### Claim 4 (depends on 1)

The system of claim 1, wherein the processor is to:
load advanced configuration and power interface tables in the second kernel mode of the secure execution environment;
parse a memory mapped table in the second kernel mode of the secure execution environment;
map a configuration space for the secure execution environment;
launch the unsecure driver in the first kernel mode of the unsecure operating system execution environment; and
enumerate a secure device in the first kernel mode.

### Claim 5 (depends on 4)

The system of claim 4, wherein the advanced configuration and power interface tables comprise a memory mapped configuration space base address description table (MCFG) and a secure device table.

### Claim 6 (depends on 5)

The system of claim 5, wherein the processor is to:
transmit a request for configuration space access from the first kernel mode of the unsecure operating system execution environment to the second kernel mode of the secure execution environment;
modify the secure configuration space of the secure execution environment; and
transmit a result of the modification of the secure configuration space to the first kernel mode of the unsecure operating system execution environment.

### Claim 7 (depends on 1)

The system of claim 1, wherein the processor is to:
detect an interrupt via the first kernel mode of the unsecure operating system execution environment; and
transmit a remote procedure call to the secure driver in the second user mode of the secure execution environment, wherein the remote procedure call indicates the detected interrupt.

### Claim 8 (depends on 1)

The system of claim 1, wherein the processor is to provide, via the second kernel mode of the secure execution environment, a direct memory access library to the second user mode, the direct memory access library enabling buffer allocation and direct read or write operations corresponding to a secure device.

### Claim 9 (depends on 1)

The system of claim 1, wherein the processor is to enable the unsecure driver to modify a subset of device memory.

### Claim 10 (depends on 1)

The system of claim 1, wherein the secure driver enables the unsecure driver to communicate with a secure device.

### Claim 11

A method for providing a secure driver framework comprising:
managing an unsecure operating system execution environment comprising a first user mode and a first kernel mode;
managing a secure execution environment comprising a second user mode and a second kernel mode;
executing a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode, wherein the secure driver enables the unsecure driver to communicate with a secure device; and
providing one or more system services of the second kernel mode to the secure driver.

### Claim 12 (depends on 11)

The method of claim 11, wherein the unsecure driver transmits the system call to the secure driver via a remote procedure call.

### Claim 13 (depends on 11)

The method of claim 11, comprising enumerating the secure device by creating a secure device node and loading the secure driver in the second user mode of the secure execution environment.

### Claim 14 (depends on 11)

The method of claim 11, comprising:
loading advanced configuration and power interface tables in the second kernel mode of the secure execution environment;
parsing a memory mapped table in the second kernel mode of the secure execution environment;
mapping a configuration space for the secure execution environment;
launching the unsecure driver in the first kernel mode of the unsecure operating system execution environment; and
enumerating the secure device in the first kernel mode.

### Claim 15 (depends on 14)

The method of claim 14, wherein the advanced configuration and power interface tables comprise a memory mapped configuration space base address description table (MCFG) and a secure device table.

### Claim 16 (depends on 15)

The method of claim 15, comprising:
transmitting a request for configuration space access from the first kernel mode of the unsecure operating system execution environment to the second kernel mode of the secure execution environment;
modifying the secure configuration space of the secure execution environment; and
transmitting a result of the modification of the secure configuration space to the first kernel mode of the unsecure operating system execution environment.

### Claim 17 (depends on 11)

The method of claim 11, comprising:
detecting an interrupt via the first kernel mode of the unsecure operating system execution environment; and
transmitting a remote procedure call to the secure driver in the second user mode of the secure execution environment, wherein the remote procedure call indicates the detected interrupt.

### Claim 18 (depends on 11)

The method of claim 11, comprising providing, via the second kernel mode of the secure execution environment, a direct memory access library to the second user mode, the direct memory access library enabling buffer allocation and direct read or write operations corresponding to the secure device.

### Claim 19 (depends on 11)

The method of claim 11, comprising detecting a level of security and loading the secure driver in the first user mode or the first kernel mode of the unsecure operating system execution environment based on the level of security.

### Claim 20 (depends on 11)

The method of claim 11, comprising dynamically loading and linking the unsecure driver and the secure driver.

### Claim 21

One or more computer-readable storage devices for implementing a secure driver framework comprising a plurality of instructions that, based at least on execution by a processor, cause the processor to
manage an unsecure operating system execution environment comprising a first user mode and a first kernel mode;
manage a secure execution environment comprising a second user mode and a second kernel mode;
execute a secure driver within the second user mode of the secure execution environment in response to a system call from an unsecure driver in the first kernel mode or the first user mode, wherein the secure driver enables the unsecure driver to communicate with a secure device; and
provide one or more system services of the second kernel mode to the secure driver.

### Claim 22 (depends on 21)

The one or more computer-readable storage devices of claim 21, wherein the plurality of instructions cause the processor to:
transmit a request for configuration space access from the first kernel mode of the unsecure operating system execution environment to the second kernel mode of the secure execution environment;
modify the secure configuration space of the secure execution environment; and
transmit a result of the modification of the secure configuration space to the first kernel mode of the unsecure operating system execution environment.
