Customer-Controlled Firmware Digest Signing via BIOS
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems face challenges in allowing customers to securely manage and verify their own device firmware, particularly for I/O device firmware, due to complexities and dependencies on third-party suppliers for Secure Boot processes.
Innovation Solution
The system enables users to select, sign, and verify pre-boot code modules, including I/O device firmware, by exporting and importing digests through a BIOS, using a Secure Boot policy with customizable keys and databases, allowing customers to manage their own trust and authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional Secure Boot mechanisms are used with third-party CAs, then device firmware authentication is established, but customer control and ownership of trust is lost
Solution Approach 1:
The patent introduces a customer-controlled signing key as an intermediary between the firmware and the Secure Boot mechanism. Instead of directly trusting third-party CAs, the customer's signing key acts as a mediator that signs firmware images, allowing customers to maintain control over which firmware is authenticated while still using the existing Secure Boot infrastructure.
Solution Approach 2:
The patent enables customers to self-manage their own signing keys and authentication processes. Customers can generate, store, and use their own signing keys to authenticate firmware images, eliminating dependency on third-party CAs and giving customers full control over their trust infrastructure.
2Adaptability or versatility
If custom keys are used for device firmware, then customer ownership of trust is achieved, but complexity of key management increases
Solution Approach 1:
The patent extracts the key management complexity from the core Secure Boot process by separating the signing key generation and management into a distinct customer-controlled process. The BIOS/UEFI firmware handles only the verification of signatures, while customers manage their own signing keys externally, simplifying the embedded system's complexity.
Solution Approach 2:
The signed firmware image acts as an intermediary that carries the customer's trust relationship. Instead of managing complex key pairs within the embedded system, the trust relationship is embedded in the firmware image itself through digital signatures, reducing in-system complexity.
3Reliability
If traditional supplier-based firmware updates are used, then firmware authenticity is maintained, but deployment and maintenance time increases
Solution Approach 1:
The patent performs preliminary signing of firmware images by customers before deployment. By signing firmware images in advance with customer-controlled keys, the authentication process is prepared beforehand, eliminating the need for time-consuming supplier interactions during deployment and enabling faster firmware updates.
Solution Approach 2:
Customers can independently sign and deploy firmware images without requiring supplier involvement in the authentication process. This self-service capability allows customers to rapidly deploy and update firmware across multiple devices without coordinating with multiple suppliers, significantly reducing deployment and maintenance time.
Data Source
AI summary
Systems and methods for providing and verifying customer-owned trust of device firmware are described. In some embodiments, an Information Handling System (IHS), may include a processor and a Basic Input/Output System (BIOS) coupled to the processor, the BIOS having program instructions stored thereon that, upon execution, cause the IHS to: receive, from a user, selection of a pre-boot code module; export a digest of the pre-boot code module to the user; and import the digest signed by the user.