Embedded Controller Root of Trust for Secure IHS Booting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Establishing a hardware root of trust in Information Handling Systems (IHS) is challenging due to the need for manufacturers to support various root of trust schemes for different processor chipsets, which complicates the initialization and validation of hardware components.

Innovation Solution

An embedded controller within the IHS is configured to serve as a hardware root of trust, using ROM and RAM to read and authenticate firmware from flash memory, and authorize booting by verifying the integrity of SBIOS instructions through incremental signature calculation, thereby establishing a trusted anchor for the entire system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manufacturers implement hardware root of trust validation for each processor chipset, then system security is improved, but device complexity and initialization difficulty increase

Engineering Contradiction:
Improvesystem securityVSAvoidinitialization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an embedded controller as an intermediary component that mediates between the processor chipset and the firmware validation process. The embedded controller contains a hardcoded root of trust that serves as a neutral mediator to validate firmware integrity, eliminating the need for manufacturers to implement complex validation schemes for each chipset. This intermediary approach simplifies the overall system while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The embedded controller is designed with universal functionality that works across multiple processor chipsets. By implementing a standardized root of trust mechanism in the embedded controller that can validate firmware for different chipset architectures, the system achieves multi-functionality without increasing individual chipset complexity. The embedded controller serves as a universal validation point for various hardware configurations.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Reliability

If firmware integrity validation is performed during initialization, then system security is improved, but boot time increases

Engineering Contradiction:
Improvefirmware integrity assuranceVSAvoidboot time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-hardcoding the root of trust in the embedded controller during manufacturing. The validation credentials and verification logic are prepared in advance within the embedded controller's firmware, allowing rapid validation during system initialization. This preliminary preparation eliminates the need for complex runtime verification setup, reducing boot time while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces complex mechanical validation systems with streamlined electronic verification. Instead of using cumbersome multi-step validation protocols that would increase boot time, the system uses efficient cryptographic verification mechanisms embedded in the controller firmware. The electronic verification process validates firmware integrity in minimal time compared to traditional mechanical or software-based validation approaches.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11068599B2Secure initialization using embedded controller (EC) root of trust
Publication Date: 2021.07.20 DELL PROD LP
  • US11068599B2 patent drawing
  • US11068599B2 patent drawing
  • US11068599B2 patent drawing

AI summary

Embodiments support establishing an embedded controller comprised within an Information Handling System (IHS) as a hardware root of trust. With the booting of the IHS paused and based on instructions encoded in a ROM (Read-Only Memory) of the embedded controller, the firmware of the embedded controller is read from a flash memory, such as a SPI Flash, and stored to a RAM (Random Access Memory) of the embedded controller. The firmware is then authenticated based on instructions encoded in the ROM. Based on instructions included in the authenticated firmware, the embedded controller reads SBIOS (Startup Basic Input Output System) instructions from the flash memory and stores them to RAM where they are authenticated based on instructions included in the authenticated embedded controller firmware. If the SBIOS instructions are authenticated, the embedded controller authorizes booting of the IHS to resume using the authenticated SBIOS instructions.