Firmware Map Data Integrity Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no reliable and simple method to detect or verify the integrity of system ROM firmware in computing devices without re-flashing, making it difficult to ensure that the firmware has not been tampered with by hackers.
Innovation Solution
A firmware inspector module uses a mapping table and hash code calculations to verify the authenticity of system ROM firmware by comparing hash codes generated from static portions with master hash codes, allowing for automated detection of tampering during production or updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional firmware verification methods are used, then firmware integrity can be verified, but the process requires re-flashing which is complex and time-consuming
Solution Approach 1:
The patent pre-calculates and stores hash codes for all static portions of firmware in a mapping table during firmware creation. This preliminary action eliminates the need for complex re-flashing verification later, as the verification process simply compares newly calculated hash codes against these pre-stored values, significantly simplifying the verification process while maintaining reliability.
2Reliability
If manual firmware verification is performed, then tampering can be detected, but the process is time-consuming and not automated
Solution Approach 1:
The system performs self-verification by automatically calculating hash codes for static firmware portions and comparing them against pre-stored master hash codes in the mapping table. This automated self-service mechanism eliminates manual verification steps and significantly reduces verification time while maintaining reliable tampering detection capabilities.
Solution Approach 2:
The verification process implements feedback by comparing calculated hash codes with pre-stored master hash codes and generating verification results. This automated feedback mechanism provides immediate tampering detection without manual intervention, reducing verification time while ensuring reliable detection.
3Reliability
If complete firmware verification is performed, then all tampering can be detected, but the process becomes complex and requires verifying entire firmware images
Solution Approach 1:
The patent segments the firmware into static and variable portions, creating a mapping table that identifies only the static portions requiring verification. This segmentation approach maintains comprehensive tampering detection for critical firmware sections while avoiding the complexity of verifying entire firmware images, including variable portions that change legitimately.
Solution Approach 2:
The patent extracts and isolates only the static portions of firmware that require verification, separating them from variable portions. This extraction approach enables comprehensive verification of critical firmware elements without the complexity of processing entire firmware images, maintaining reliability while reducing verification complexity.
Data Source
AI summary
An example method includes retrieving, based on firmware map data stored in a firmware map, first portions of a system firmware while omitting retrieval of second portions to form a combined portion. The firmware map data is indicative of the first portions of the system firmware that remain unchanged over a normal lifetime of the system firmware, and the firmware map data is also indicative of the second portions of the system firmware that may vary over the normal lifetime of the system firmware. The method further includes calculating at least one master hash code based on the combined portion, and storing the at least one master hash code in a hash code table in association with the firmware map data.