Firmware Integrity Verification via Chained Hashes and Layered Endorsements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems face challenges in verifying the integrity and trustworthiness of firmware updates, particularly when dealing with multiple components from different suppliers, as they lack a comprehensive method to ensure the firmware has not been compromised during the boot process.
Innovation Solution
A system that receives a chained cryptographic hash value from a trusted platform module, compares it with an event log, and retrieves layered endorsements associated with patch identities to determine the integrity of firmware updates, ensuring the system has booted into a trusted state by verifying hash values and event information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If firmware updates are installed on multiple components from different suppliers, then the system's functionality and adaptability are improved, but the difficulty of verifying firmware integrity and determining trustworthiness increases
Solution Approach 1:
The patent implements a nested structure where cryptographic hash values are chained together in a hierarchical manner. Each firmware component's hash is nested within a larger chain that ultimately verifies the entire system's integrity. The trusted platform module nests multiple hash measurements into a single chained hash value that represents the complete firmware state, allowing comprehensive verification through a unified structure.
Solution Approach 2:
The patent introduces layered endorsements as intermediary elements between the firmware components and the verification system. These endorsements act as mediators that provide cryptographic proof of firmware integrity from multiple trusted sources. The intermediary endorsement structure translates complex multi-component verification into a series of manageable cryptographic validations that can be systematically verified.
2Reliability
If comprehensive firmware verification is performed by comparing chained hash values with event logs and layered endorsements, then the reliability and security of the system are improved, but the complexity of the verification process increases
Solution Approach 1:
The patent segments the firmware verification process into distinct, manageable components: (1) individual firmware hash calculations for each component, (2) chaining these hashes into a unified structure, (3) creating layered endorsements from multiple trusted sources, and (4) comparing the chained hash against event logs. This segmentation transforms a monolithic complex verification task into modular steps that can be independently implemented and validated.
Solution Approach 2:
The patent performs preliminary actions by pre-calculating and storing layered endorsements from multiple trusted sources before the actual verification occurs. The event logs are pre-populated with expected chained hash values representing known good firmware states. This preliminary preparation allows the runtime verification to focus on simple comparison operations rather than complex calculations, reducing the operational complexity during the actual verification process.
Data Source
AI summary
In one or more embodiments, a first information handling system may: receive a chained cryptographic hash value determined by a trusted platform module (TPM) of a second information handling system; receive multiple patch identities associated with multiple updated firmware installed on multiple components of the second information handling system; receive an event log associated with output of the TPM as the TPM determined the chained cryptographic hash value; retrieve multiple layered endorsements respectively associated with the multiple patch identities; determine multiple hash values from multiple signatures stored in the multiple layered endorsements; compare the chained cryptographic hash value with the event log; compare multiple event information with the multiple hash values; and determine that the second information handling system has booted into a trusted state based at least on comparing the chained cryptographic hash value with the event log and comparing the multiple event information with the multiple hash values.


