Firmware Signature Conversion for Fast SSD Boot and PQC Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Solid state drives (SSDs) incorporating NAND flash memory lack hardware accelerators capable of performing signature verification for post-quantum cryptography, leading to prolonged boot times and vulnerability to unauthorized firmware updates.
Innovation Solution
Incorporating a controller with a hardware accelerator for Elliptic Curve Digital Signature Algorithm (ECDSA) and a CPU-based Post-Quantum Cryptography (PQC) signature verifier, along with an ECDSA signature generator, to facilitate rapid signature verification and encryption of firmware using common key cryptography, ensuring compatibility with post-quantum cryptography.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a hardware accelerator for ECDSA signature verification is incorporated, then signature verification speed is improved and boot time is reduced, but the system cannot perform signature verification for firmware using post-quantum cryptography digital signatures
Solution Approach 1:
The controller is designed to support multiple digital signature schemes (both ECDSA and post-quantum cryptography schemes) within the same hardware architecture. The signature verification unit can adaptively select and execute different verification algorithms based on the type of digital signature present in the firmware, enabling the system to handle both traditional and post-quantum cryptographic standards without requiring separate hardware accelerators for each scheme.
2Reliability
If signature verification is performed using post-quantum cryptography digital signatures, then security against quantum computer attacks is improved, but signature verification time increases and boot time is prolonged
Solution Approach 1:
The system performs signature verification using post-quantum cryptography digital signatures during the firmware update process before the firmware is actually executed. By completing the time-consuming verification operation in advance during the update phase rather than during boot, the system ensures security without significantly impacting the boot time experienced by the user.
3Reliability
If firmware is updated with new digital signatures, then security is maintained, but the verification process becomes more complex and time-consuming
Solution Approach 1:
The signature verification unit is designed with dynamic adaptability to handle different digital signature schemes. When firmware is updated with new digital signatures, the verification process automatically adjusts to the appropriate algorithm without requiring manual reconfiguration or increasing operational complexity for the user. The system dynamically selects the verification method based on the signature type embedded in the firmware.
Data Source
AI summary
According to one embodiment, a controller includes a CPU and an accelerator which performs signature verification using a first signature of a first scheme. When updating first firmware to second firmware to which a second signature of a second scheme is assigned, the controller performs the signature verification of the second firmware based on the second signature assigned to the second firmware by the CPU, generates the first signature for the second firmware, and replaces the second signature assigned to the second firmware with the generated first digital signature. When booting the second firmware, the controller performs the signature verification of the second firmware based on the first signature assigned to the second firmware by the accelerator.