Encrypted Boot Image Handling via Management Engine Secure Boot

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Firmware codes, such as BIOS or UEFI, are not securely protected during transit from storage to processor, as they are unencrypted, making them vulnerable to reverse engineering and security attacks, posing risks for high-security programs.

Innovation Solution

A method and system for transmitting an encrypted boot image to a system, decrypting it locally, and executing it on a processor, using a Management Engine (ME) to establish a communication channel with a security device, decrypt the image, and store it in a secured storage medium, with the ME generating a unique key for encryption based on the processor's unique material.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware codes are transmitted in unencrypted form, then the processor can execute them directly, but the firmware becomes vulnerable to reverse engineering and security attacks

Engineering Contradiction:
ImprovesecurityVSAvoidencryption/decryption process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The firmware is encrypted in advance before transmission to the processor. The Management Engine performs the encryption operation beforehand, so that when the firmware reaches the processor, it is already in protected form. This preliminary encryption action prevents the firmware from being exposed in plaintext during transmission and storage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The Management Engine acts as an intermediary between the firmware source and the processor. It handles the encryption and decryption operations, allowing the firmware to be transmitted in encrypted form while still enabling the processor to execute it after decryption. This intermediary resolves the conflict between security requirements and processor execution capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the processor executes unencrypted firmware, then the booting process is simple, but the firmware codes are exposed to security risks during transit

Engineering Contradiction:
Improvebooting processVSAvoidsecurity attacks
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The Management Engine serves as a mediator that handles the complex encryption/decryption operations, allowing the main processor to focus on execution. The intermediary manages the security complexity while keeping the processor's operation simple - it only needs to decrypt and execute, without needing to understand or implement cryptographic algorithms.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The Management Engine performs self-service by autonomously managing the encryption and decryption of firmware. It generates keys, encrypts firmware before transmission, and decrypts it during booting without requiring external intervention. This self-service capability maintains ease of operation while providing security protection.

Inventive Principle:
Principle #25Self-service

3Reliability

If encrypted firmware is used, then security is enhanced, but the processor must decrypt it first which adds complexity

Engineering Contradiction:
ImprovesecurityVSAvoiddecryption capability
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The Management Engine acts as an intermediary that assumes the decryption burden. Instead of requiring the main processor to have decryption capabilities, the Management Engine handles decryption and then provides the decrypted firmware to the processor for execution. This separates security functions from execution functions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system is segmented into two functional parts: the Management Engine responsible for security operations (encryption/decryption), and the main processor responsible for execution. This segmentation allows each component to be optimized for its specific function - the Management Engine for security and the processor for computation - reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11423150B2System and method for booting processors with encrypted boot image
Publication Date: 2022.08.23 NIGHTWING GROUP LLC
  • US11423150B2 patent drawing
  • US11423150B2 patent drawing
  • US11423150B2 patent drawing

AI summary

The concepts, systems and methods described herein are directed towards a method for secure booting. The method is provided to including: loading and executing a firmware in a Management Engine (ME) of a system; establishing, by the ME, a communication channel to a security device; receiving, by the ME, an encrypted boot image from the security device; decrypting, by the ME, the encrypted boot image; storing, by the ME, the decrypted boot image in a secured storage medium; and resetting the system using the decrypted boot image in the secured storage medium.