# US 11,836,254 B2 · System and method for securing a series of firmware function calls using session tokens

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

- Number: US 11,836,254 B2
- Document ID: US11836254B2
- Status: Granted
- Kind: B2
- Application number: 16/130,039
- Filed: 2018-09-13
- Published: 2019-03-14
- Granted: 2023-12-05
- Earliest claimed: 2017-09-14
- Assignees: Insyde Software Corp.
- Applicants: Insyde Software Corp.
- Inventors: Timothy Andrew Lewis
- Web page: https://patentgrep.com/patent/US11836254B2

## CPC

- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- G06F 9/4411: {Configuring for operating with peripheral devices; Loading of device drivers}
- G06F 9/545: {where tasks reside in different layers, e.g. user- and kernel-space}
- G06F 21/44: Program or device authentication
- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 21/606: {by securing the transmission between two devices or processes}
- H04L 9/0869: {involving random numbers or seeds}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- 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

A mechanism for securing a series of related function calls for firmware services using session tokens is discussed.

## Claims

### Claim 1

A non-transitory medium holding computer-executable instructions for authenticating related firmware service calls in a computing device that includes firmware and at least one processor, the firmware when executed causing the computing device to:
receive a request with the firmware to open a session from an operating system-based calling entity, the request accompanied by authentication data;
authenticate the operating system-based calling entity based on the authentication data;
establish the session between the operating system-based calling entity and the firmware, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed;
receive a firmware service call from the operating system-based calling entity accompanied by the session token as a calling parameter;
verify the session token and that the privilege level is adequate for the firmware service call;
perform the firmware service call based on the verifying;
return an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number;
receive a subsequent related firmware service call accompanied by the updated session token as a calling parameter;
verify the updated session token and that the privilege level is adequate for the subsequent related firmware service call; and
perform the subsequent related firmware service call based on the verifying of the updated session token and the privilege level.

### Claim 2 (depends on 1)

The medium of claim 1, wherein the calling entity is an operating system (OS) application or OS driver.

### Claim 3 (depends on 1)

The medium of claim 1, wherein the firmware receives the firmware service call and subsequent related firmware service call via a System Management Mode (SMM) interface.

### Claim 4 (depends on 3)

The medium of claim 3, wherein the firmware when executed further:
locks the SMM interface by rejecting additional session requests after establishing the session, the locking continuing until the established session is closed.

### Claim 5 (depends on 1)

The medium of claim 1, wherein the randomly generated number is provided by a CPU instruction in an x86 instruction set.

### Claim 6 (depends on 1)

The medium of claim 1, wherein a software System Manage Interrupt (SMI) is used to make at least one of the firmware service call or subsequent firmware service call.

### Claim 7 (depends on 1)

The medium of claim 1, wherein at least one of the session token or updated session token are stored in a CPU register.

### Claim 8

A method for authenticating firmware service calls in a computing device equipped with at least one processor, comprising:
receiving a request with the firmware to open a session from an operating system-based calling entity, the request accompanied by authentication data;
authenticating with the firmware the operating system-based calling entity based on the authentication data;
establishing the session between the operating system-based calling entity and firmware executing on the computing device, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed;
receiving with the firmware a firmware service call from the calling entity accompanied by the session token as a calling parameter;
verifying the session token and that the privilege level is adequate for the firmware service call;
performing the firmware service call with the firmware based on the verifying;
returning an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number;
receiving a subsequent related firmware service call accompanied by the updated session token as a calling parameter;
verifying the updated session token and that the privilege level is adequate for the subsequent related firmware service call; and
performing the subsequent related firmware service call with the firmware based on the verifying of the updated session token and the privilege level.

### Claim 9 (depends on 8)

The method of claim 8, wherein the operating system-based calling entity is an operating system (OS) application or OS driver.

### Claim 10 (depends on 8)

The method of claim 8, wherein the firmware receives the firmware service call and subsequent related firmware service call via a System Management Mode (SMM) interface.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
locking the SMM interface with the firmware by rejecting additional session requests after establishing the session, the locking continuing until the established session is closed.

### Claim 12 (depends on 8)

The method of claim 8, wherein the randomly generated number is provided by a CPU instruction in an x86 instruction set.

### Claim 13 (depends on 8)

The method of claim 8, wherein a software System Manage Interrupt (SMI) is used to make at least one of the firmware service call or subsequent firmware service call.

### Claim 14 (depends on 8)

The method of claim 8, wherein at least one of the session token or updated session token are stored in a CPU register.

### Claim 15

A computing device configured to securely handle related function calls to firmware, the computing device comprising:
at least one processor;
an operating system; and
firmware, the firmware when executed:
receiving a request to open a session from an operating system-based calling entity, the request accompanied by authentication data,
authenticating the operating system-based calling entity based on the authentication data,
establishing the session between the operating system-based calling entity and the firmware, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed,
receiving a firmware service call from the operating system-based calling entity accompanied by the session token as a calling parameter,
verifying the session token and that the privilege level is adequate for the firmware service call,
performing the firmware service call based on the verifying,
returning an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number,
receiving a subsequent related firmware service call accompanied by the updated session token as a calling parameter,
verifying the updated session token and that the privilege level is adequate for the subsequent related firmware service call, and
performing the subsequent related firmware service call based on the verifying of the updated session token and the privilege level.

### Claim 16 (depends on 15)

The computing device of claim 15, wherein the operating system-based calling entity is an operating system (OS) application or OS driver.

### Claim 17 (depends on 15)

The computing device of claim 15, wherein at least one of the session token or updated session token are stored in a CPU register.
