# US 2022/0358222 A1 · System And Method For Firmware Security Event Mitigation

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

- Number: US 2022/0358222 A1
- Document ID: US20220358222A1
- Status: Published application
- Kind: A1
- Application number: 17/739,832
- Filed: 2022-05-09
- Published: 2022-11-10
- Earliest claimed: 2021-05-10
- Assignees: Insyde Software Corp.
- Applicants: Insyde Software Corp.
- Inventors: Timothy Andrew Lewis
- Web page: https://patentgrep.com/patent/US20220358222A1

## CPC

- G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57)
- G06F 21/572: {Secure firmware programming, e.g. of basic input output system [BIOS]}
- 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/554: {involving event detection and direct action}
- G06F 21/562: {Static detection}
- 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

Systems and methods for performing security event mitigation with firmware are discussed. A firmware-based security event framework receives notifications of security events occurring in a firmware-controlled operating environment on a computing platform, logs information related to the event and optionally performs mitigation operations to address the security event.

## Claims

### Claim 1

A non-transitory medium holding executable instructions for performing security event mitigation with firmware on a computing platform equipped with one or more processors, the instructions when executed causing the computing platform to:
receive notification of detection of an occurrence of a security event caused by code executing within a firmware-controlled operating environment;
log, with the firmware, information regarding the event in a non-volatile storage location;
generate, with the firmware, a notification of the security event; and
perform, with the firmware, a mitigation of the security event.

### Claim 2 (depends on 1)

The medium of claim 1, wherein the instructions when executed, further:
reset the computing platform based on the detection before performing a mitigation of the security event.

### Claim 3 (depends on 2)

The medium of claim 2, wherein the mitigation blocks a firmware module from executing after the reset of the computing platform.

### Claim 4 (depends on 1)

The medium of claim 1, wherein the mitigation re-flashes an entire BIOS image, a firmware volume that contains a module causing the security event, or a specific driver causing the security event.

### Claim 5 (depends on 1)

The medium of claim 1, wherein the code causing the security event executes in the firmware-controlled operating environment when one or more processors of the computing platform are in System Management Mode.

### Claim 6 (depends on 1)

The medium of claim 1, wherein the code causing the security event executes in the firmware-controlled operating environment during a boot sequence for the computing platform.

### Claim 7 (depends on 1)

The medium of claim 1, wherein the security event is detected using CPU and chipset resources

### Claim 8 (depends on 1)

The medium of claim 1, wherein the security event is detected at runtime using code injected by a compiler during build time.

### Claim 9 (depends on 1)

The medium of claim 1, wherein the security event is pre-specified behavior that is detected occurring in the firmware kernel.

### Claim 10 (depends on 1)

The medium of claim 1, wherein the security event is an OEM-defined security event detected using OEM code during a boot sequence for the computing platform.

### Claim 11 (depends on 1)

The medium of claim 1, wherein the security event is detected based on a security status reported during device authentication for a motherboard device.

### Claim 12

A method for performing security event mitigation with firmware on a computing platform equipped with one or more processors, comprising:
receiving notification of detection of an occurrence of a security event caused by code executing within a firmware-controlled operating environment;
logging, with the firmware, information regarding the event in a non-volatile storage location;
generating, with the firmware, a notification of the security event; and
performing, with the firmware, a mitigation of the security event.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
resetting the computing platform based on the detection before performing a mitigation of the security event.

### Claim 14 (depends on 13)

The method of claim 13, wherein the mitigation blocks a firmware module from executing after the reset of the computing platform.

### Claim 15 (depends on 12)

The method of claim 12, wherein the mitigation re-flashes an entire BIOS image, a firmware volume that contains a module causing the security event, or a specific driver causing the security event.

### Claim 16 (depends on 12)

The method of claim 12, wherein the code causing the security event executes in the firmware-controlled operating environment when one or more processors of the computing platform are in System Management Mode.

### Claim 17 (depends on 12)

The method of claim 12, wherein the code causing the security event executes in the firmware-controlled operating environment during a boot sequence for the computing platform.

### Claim 18 (depends on 12)

The method of claim 12, wherein the security event is detected using CPU and chipset resources

### Claim 19 (depends on 12)

The method of claim 12, wherein the security event is detected at runtime using code injected by a compiler during build time.

### Claim 20 (depends on 12)

The method of claim 12, wherein the security event is pre-specified behavior that is detected occurring in the firmware kernel.

### Claim 21 (depends on 12)

The method of claim 12, wherein the security event is an OEM-defined security event detected using OEM code during a boot sequence for the computing platform.

### Claim 22 (depends on 12)

The method of claim 12, wherein the security event is detected based on a security status reported during device authentication for a motherboard device.

### Claim 23

A computing platform, comprising:
one or more processors; and
firmware including a security event framework, the security event framework including one or more firmware modules that when executed:
receive notification of an occurrence of a security event caused by code executing within a firmware-controlled operating environment;
log, with the firmware, information regarding the event in a non-volatile storage location;
generate, with the firmware, a notification of the security event; and
perform, with the firmware, a mitigation of the security event.
