DICE 3-Layer Architecture for Firmware Updates Without DeviceID Reissue
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing DICE architecture requires issuance of a new DeviceID certificate for firmware updates, which wastes resources and increases deployment complexity, and ad hoc issuance can lead to security issues.
Innovation Solution
Implementing a DICE 3-layer architecture where firmware updates occur at DICE layer 1, maintaining the DeviceID and associated DICE identity key unchanged, while updating the DICE alias key, thereby preserving the Chain of Trust and avoiding the need for new DeviceID certificates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a new DeviceID certificate is issued for each firmware update, then the Chain of Trust can be maintained, but resource consumption increases and deployment complexity increases
Solution Approach 1:
The firmware is divided into two distinct layers: DICE layer 0 containing the DeviceID and DICE identity key, and DICE layer 1 containing the DICE alias key. This segmentation allows independent updates of layer 1 without affecting layer 0, thereby maintaining Chain of Trust integrity while reducing deployment complexity by avoiding frequent reissuance of DeviceID certificates.
2Reliability
If a new DeviceID certificate is issued for each firmware update, then security can be maintained, but resource consumption increases
Solution Approach 1:
By segmenting firmware into DICE layer 0 (with DeviceID) and DICE layer 1 (with DICE alias key), the system enables selective updates of layer 1 without triggering DeviceID certificate reissuance. This reduces computational resources and energy consumption associated with certificate generation and validation while maintaining security through the preserved Chain of Trust.
3Adaptability or versatility
If ad hoc DeviceID certificate issuance is allowed, then deployment flexibility is improved, but security issues arise
Solution Approach 1:
The system pre-establishes a structured firmware update mechanism where DICE layer 1 can be updated independently using predetermined procedures. This preliminary structuring eliminates the need for ad hoc DeviceID certificate issuance while maintaining deployment flexibility, as updates follow predefined paths that preserve Chain of Trust integrity and prevent security issues.
Data Source
AI summary
Implementations described herein relate to a device identifier composition engine (DICE) 3-layer architecture. In some implementations, a device may include a secure computing environment including a hardware root of trust (HRoT) DICE component. The secure computing environment may include a DICE layer 0 component configured to derive a DICE identity key. The secure computing environment may include a DICE layer 1 component configured to derive a DICE alias key based on the DICE identity key. The secure computing environment may include a controller configured to receive an update to firmware of a component. The controller may be configured to update the firmware of the component based on receiving the update. The controller may be configured to update one or more keys of the component or one or more keys of one or more components above the component in a layer stack.