Partitioning Platform Firmware for Secure Multi-Party SoC Trust
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern processors implemented as system on chip (SoC) face challenges in protecting IP blocks, firmware, and other assets from unauthorized access due to multiple parties involved in their development and deployment, leading to difficulties in securing these assets across various platforms.
Innovation Solution
The solution involves partitioning platform firmware into SoC vendor-owned and OEM-owned portions, with a root of trust (RoT) manifest that decouples trust dependencies between entities, allowing secure separation of responsibilities and enabling dynamic delegation of RoT, thereby protecting SoC vendor assets while allowing OEMs to innovate and securely develop platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple parties are involved in SoC development and deployment, then system functionality and adaptability are improved, but security and protection of assets from unauthorized access deteriorate
Solution Approach 1:
The patent segments the firmware into multiple distinct portions (first portion associated with SoC vendor, second portion associated with OEM) with separate verification mechanisms. Each portion has its own key and verification process, allowing multiple parties to contribute functionality while maintaining independent security boundaries that prevent unauthorized access to proprietary assets.
Solution Approach 2:
The patent introduces a manifest as an intermediary data structure that contains verification information for both firmware portions. This manifest acts as a mediator that coordinates the verification process between the SoC vendor's firmware and the OEM's firmware, enabling secure multi-party collaboration without direct trust dependencies between the parties.
2Reliability
If firmware is partitioned into multiple portions with separate verification, then asset protection is improved, but system complexity increases
Solution Approach 1:
The patent merges the verification information for multiple firmware portions into a single manifest structure. This consolidation allows the complex verification logic to be centralized in one data structure rather than scattered across multiple separate verification mechanisms, reducing overall system complexity while maintaining comprehensive asset protection.
Solution Approach 2:
The manifest serves multiple functions simultaneously: it stores verification information for the SoC vendor's firmware, verification information for the OEM's firmware, and coordinates the trust establishment process. This multi-functionality reduces the need for separate verification mechanisms and simplifies the overall firmware structure.
Data Source
AI summary
In one embodiment, a processor has at least one core to execute instructions, a security engine coupled to the at least one core, a first storage to store a first immutable key associated with a vendor of the processor, and a second storage to store a second immutable key associated with an original equipment manufacturer (OEM) of the system. A first portion of firmware is to be verified based at least in part on the first immutable key and a second portion of firmware is to be verified based at least in part on the second immutable key, the first portion of firmware associated with the vendor and the second portion of firmware associated with the OEM. Other embodiments are described and claimed.