Secure Boot Handoff via Encrypted Data Blocks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing boot process of processors lacks confidentiality protection for OEM silicon initialization code and data handoff, making it vulnerable to malware attacks and intellectual property exposure, despite efforts for integrity protection through encryption of chip manufacturer's code.
Innovation Solution
Creating secure enclaves for both chip manufacturer and OEM initialization codes, using an encrypted handoff block for secure data transfer between enclaves, and employing trusted execution environments for UEFI variables and user input, ensuring only trusted entities can decrypt and access the data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the chip manufacturer's silicon initialization code is encrypted, then confidentiality of the code is improved, but the complexity of the boot process increases
Solution Approach 1:
The patent segments the boot process into distinct phases: chip manufacturer initialization phase and OEM initialization phase. Each phase has its own encrypted code stored in separate memory regions, with controlled handoff between phases. This segmentation allows independent encryption and execution of different code portions, managing complexity through structured organization.
Solution Approach 2:
The chip manufacturer's initialization code performs preliminary actions by encrypting and storing the OEM initialization code in memory before the OEM phase executes. The encrypted code is prepared in advance with proper memory addresses and encryption keys, so that when the handoff occurs, the OEM code can be directly decrypted and executed without additional preparation steps.
2Ease of operation
If the boot process is made open and accessible, then ease of operation is improved, but security against malware attacks deteriorates
Solution Approach 1:
The patent introduces an intermediary mechanism - the encrypted handoff block - that mediates between the chip manufacturer's initialization code and the OEM initialization code. This intermediary structure allows controlled data exchange while maintaining security boundaries, preventing direct access to encrypted code regions and blocking malware injection paths.
Solution Approach 2:
Different regions of the boot process have different security qualities. The chip manufacturer's initialization code region is encrypted and protected, while the handoff data region has controlled accessibility. The OEM initialization code is encrypted in its own region. This local quality differentiation allows each component to operate with appropriate security levels without requiring full system openness.
3Reliability
If the HSTI interface is made non-modifiable, then integrity protection is improved, but adaptability for OEM customization deteriorates
Solution Approach 1:
The patent segments the HSTI interface functionality into distinct components: the chip manufacturer's secure configuration register (integrity-protected) and the OEM initialization code (customizable). By separating these functions and using encrypted handoff blocks, the system maintains integrity of the secure configuration while allowing OEM customization in the initialization code without modifying the HSTI interface itself.
Solution Approach 2:
The encrypted handoff block serves as an intermediary that carries customized OEM initialization parameters without requiring modifications to the HSTI interface. The HSTI interface maintains its integrity-protected, non-modifiable nature, while the intermediary handoff block enables OEM customization by transporting encrypted data and control information between the chip manufacturer's code and the OEM code.
Data Source
AI summary
A disclosed example apparatus includes memory; and at least one processor to execute first instructions, the first instructions obtained from first encrypted firmware, the at least one processor to: encrypt handoff data with an original equipment manufacturer key to generate encrypted handoff data; decrypt second encrypted firmware based on the original equipment manufacturer key to generate second instructions; and provide access to the encrypted handoff data to the second instructions, the second instructions to perform initialization of a computer based on the handoff data obtained from the encrypted handoff data.