Autonomous Firmware Recovery via Segmented Backup Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The proprietary and large size of firmware subsystems in computing devices pose challenges for secure backup and recovery, particularly due to limited storage space and the need to protect proprietary information, while ensuring integrity and security against errors or unauthorized modifications.
Innovation Solution
A computing device architecture that includes a separate autonomous management firmware subsystem, with a controller and secure memory isolated from the main processor, uses recovery information and updates to initiate and complete firmware recovery, minimizing storage needs and maintaining proprietary information security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware subsystem is backed up securely, then recovery capability is improved, but secure storage space requirement increases
Solution Approach 1:
The backup storage is segmented into two distinct parts: a small secure storage area that stores only recovery information (integrity data, recovery algorithms) and a larger non-secure storage area that stores the actual firmware backup data. This segmentation allows the system to maintain reliable recovery capability while minimizing the space occupied in secure storage.
Solution Approach 2:
The essential recovery information is extracted from the complete firmware backup and stored separately in secure memory. This extracted information contains only the critical elements needed for verification and recovery initiation, while the bulk firmware data is stored in non-secure memory, thereby reducing secure storage requirements.
2Reliability
If complete firmware backup is stored securely, then recovery integrity is improved, but storage cost and complexity increase
Solution Approach 1:
The backup system is divided into two functional components: secure storage for integrity verification data and non-secure storage for firmware payload. This segmentation simplifies the secure storage system by removing the burden of protecting large volumes of data, while still ensuring recovery integrity through cryptographic verification of the segmented components.
Solution Approach 2:
A secure controller acts as an intermediary that manages the interaction between secure and non-secure storage areas. It performs integrity verification by combining data from both storage areas and executes recovery operations, thereby simplifying the overall system architecture while maintaining security and integrity.
3Object-affected harmful factors
If proprietary firmware information is protected, then security is improved, but accessibility for recovery operations is reduced
Solution Approach 1:
Firmware information is segmented into proprietary sensitive data stored in non-secure memory and recovery-critical data stored in secure memory. This allows the system to protect proprietary information from unauthorized access while maintaining easy accessibility of the recovery data needed for firmware restoration operations.
Solution Approach 2:
The secure controller serves as an intermediary that mediates access between the secure storage area and the firmware subsystem. It enables recovery operations by retrieving and verifying data from non-secure storage while protecting proprietary information, thus balancing security requirements with operational accessibility.
Data Source
AI summary
An example computing device includes a controller to control operation of a firmware subsystem of the computing device. The controller is separate from a main processor of the computing device. A memory stores subsystem data that is useable by the controller. The subsystem data includes recovery information executable by the controller to initiate recovery of the subsystem. The computing device further includes recovery coordination instructions. The recovery coordination instructions determine integrity of the recovery information as stored on the memory and. In response to determining that the recovery information lacks integrity, the recovery coordination instructions initiate recovery of the firmware subsystem using a backup of the recovery information and perform recovery of the firmware subsystem using an update to the firmware subsystem.