Secure Storage Element for Peripheral Code Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Peripheral components connected to the internet, such as printers and routers, are vulnerable to hacker attacks and viruses due to a lack of hardening against such threats, and existing security measures like ROM-based root of trust are impractical as they can become worthless if the private key is corrupted.
Innovation Solution
A secure storage element independent of firmware and hardware is used to authenticate and validate data, with a separate block for storing validation keys and update data, allowing only the manufacturer to update the secure storage with a validated private key, ensuring the integrity of the code and keys without compromising the root of trust.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a ROM-based root of trust is used to validate code, then code integrity can be ensured, but the system becomes vulnerable if the private key is corrupted or the hash changes
Solution Approach 1:
The patent divides the validation system into separate functional components: a secure storage element for holding validation keys, a separate code storage area for holding executable code, and a validation mechanism that operates independently. This segmentation ensures that compromise of one component does not necessarily compromise the entire system.
Solution Approach 2:
The patent introduces a secure storage element as an intermediary between the code validation process and the execution process. This intermediary securely holds validation keys and enables validation without requiring the keys to be permanently embedded in ROM, thus preventing direct exposure of cryptographic material while maintaining validation capability.
2Ease of operation
If validation keys are stored in ROM, then validation can be performed, but the ROM becomes worthless if the private key is corrupted
Solution Approach 1:
The patent uses a secure storage element that can be programmed with validation keys, allowing the system to create and update copies of validation information without permanently embedding them in ROM. This enables key updates and replacements without requiring reprogramming of the entire ROM.
Solution Approach 2:
The patent transitions from static ROM-based key storage to a dynamic secure storage element that can be updated and reconfigured. The secure storage element can receive new validation keys and maintain them securely, allowing the validation system to adapt to changing cryptographic requirements without hardware changes.
3Adaptability or versatility
If peripheral components are connected to the internet, then functionality and connectivity are improved, but security against hacker attacks and viruses deteriorates
Solution Approach 1:
The patent implements preliminary validation of code before it is executed on the peripheral device. The secure storage element pre-stores validation keys that can authenticate code sources before the code reaches the device, preventing malicious code from ever being executed even if the device is connected to untrusted networks.
Solution Approach 2:
The patent employs disposable validation mechanisms where validation keys can be rotated and updated independently of the main device. If a key is compromised, it can be discarded and replaced without affecting the entire device, similar to using disposable security tokens that can be regenerated without system reconfiguration.
Data Source
AI summary
Methods and apparatus for validating a system include reading protected record data for a section of the system from a secure storage element, and verifying integrity of the section of the system using the record data. The secure storage element independently verifies that all record data and data to be written to the system is valid.