Secure Firmware Interface via Mailbox Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is currently no secure way to remotely manage firmware in electronic devices, preventing remote activation and deactivation of OEM and third-party features.
Innovation Solution
A mailbox mechanism is used for secure communication, with content authenticated in the Driver Execution Environment (DXE) phase, enabling secure exchange of information between a server and the BIOS of a device, utilizing UEFI variables for secure storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a mailbox mechanism is used for remote firmware communication, then remote management capability is improved, but security vulnerability increases without authentication
Solution Approach 1:
The patent applies preliminary action by authenticating the mailbox content in the DXE phase before any firmware communication occurs. The authentication of the first mailbox content is performed during the Driver Execution Environment initialization, establishing security credentials before remote management operations begin. This ensures that subsequent communications are protected by pre-established authentication.
Solution Approach 2:
The patent uses an intermediary approach by introducing an authenticated mailbox mechanism as a mediator between the remote management system and the firmware. The mailbox serves as a secure intermediary channel where content is authenticated through cryptographic verification (hash comparison) before being processed, preventing direct unsecured access to firmware operations.
2Reliability
If UEFI variables are used for secure storage, then data security is improved, but storage flexibility decreases
Solution Approach 1:
The patent applies segmentation by dividing the storage system into two distinct parts: UEFI variables for secure storage of authentication credentials and hashed data, and regular memory for flexible temporary data storage. This segmentation allows each storage type to be used for its optimal purpose - UEFI variables provide secure persistent storage while regular memory provides flexible temporary storage, resolving the contradiction between security and flexibility.
Solution Approach 2:
The patent applies local quality by assigning different security characteristics to different storage locations. UEFI variables are used specifically for data requiring high security (authentication credentials, hashed mailboxes), while other memory areas are used for data requiring flexibility but not the same level of security. This localized application of security measures optimizes both security and flexibility where needed.
Data Source
AI summary
A mailbox mechanism is used for communication of secure messages from a server to the firmware of a device. Mailbox content provided by the server is authenticated in a driver execution environment of the device, using reboots across the communication sessions, and then stored in secure storage. The communication sessions include first receiving a signed server key, and then receiving a message from the server that is based on a hash of a nonce generated by the device.


