Firmware Verification via SVN Hash in SoC Security Controllers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
System on Chip (SoC) platforms face security vulnerabilities due to the integration of various components, which can lead to integrity issues with firmware, particularly with the management of security version numbers (SVNs), as traditional methods like One Time Programmable (OTP) memory are costly and inflexible, preventing effective verification and refurbishment.
Innovation Solution
A mechanism is implemented using a security controller with a trusted platform module (TPM) to verify the integrity of firmware by generating and storing a security version number (SVN) hash, ensuring that only verified firmware is downloaded and allowing for SVN rollback and refurbishment, while using a hash algorithm to secure the SVN management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If One Time Programmable (OTP) memory is used to store security version numbers, then the security integrity is improved, but the cost and flexibility deteriorate
Solution Approach 1:
The patent uses a copy of the security version number (SVN) stored in non-volatile memory rather than OTP memory. The SVN is copied to a trusted platform module (TPM) for verification, allowing the same memory to be reused multiple times without the cost and inflexibility of OTP memory, while maintaining security integrity through cryptographic verification.
Solution Approach 2:
The patent changes the storage parameter from OTP memory to non-volatile memory with cryptographic protection. By using hash algorithms to generate and verify SVN hashes in a TPM, the system achieves comparable or superior security without the manufacturing costs and flexibility constraints of OTP memory.
2Reliability
If One Time Programmable (OTP) memory is used to store security version numbers, then the security integrity is improved, but the flexibility for refurbishment deteriorates
Solution Approach 1:
The patent implements a dynamic verification system where the SVN is stored in non-volatile memory and verified through cryptographic hash comparison in a TPM. This dynamic approach allows the system to verify firmware integrity multiple times and supports refurbishment operations, unlike static OTP memory that cannot be rewritten or verified repeatedly.
Solution Approach 2:
The patent uses feedback from the TPM verification process to determine whether firmware updates are safe to apply. The SVN hash generated from the firmware is compared with the stored hash, providing feedback that enables secure refurbishment and updates while maintaining security integrity, something OTP memory cannot provide.
3Device complexity
If traditional verification methods are used, then the simplicity is maintained, but the security against malicious firmware deteriorates
Solution Approach 1:
The patent introduces a trusted platform module (TPM) as an intermediary between the firmware verification process and the main system. The TPM handles cryptographic operations and SVN verification, providing strong security against malicious firmware while keeping the overall system architecture manageable by isolating security functions in a dedicated module.
Data Source
AI summary
An apparatus to verify firmware in a computing system, comprising a non-volatile memory, including firmware memory to store agent firmware associated with each of a plurality of interconnect protocol (IP) agents and version memory to store security version numbers (SVNs) included in the agent firmware, a security controller comprising verifier logic to verify an integrity of the version memory by applying a hash algorithm to contents of the version memory to generate a SVN hash, and a trusted platform module (TPM) to store the SVN hash.