Secure Boot Signature Switching Against Cryptographic Compromise
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure boot systems are vulnerable to compromise when cryptographic algorithms are compromised by advanced cryptanalysis, particularly with the advent of quantum computers, leading to significant security weaknesses.
Innovation Solution
An information processing apparatus with a computation unit and storage unit that supports multiple signature verification methods, allowing easy transition to a different cryptographic algorithm and enabling robust secure boot processes through double-bank configurations and program updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a fixed cryptographic algorithm is used for secure boot, then the secure boot process is simple and reliable, but the system becomes vulnerable when the algorithm is compromised by advanced cryptanalysis
Solution Approach 1:
The patent implements dynamic selection of cryptographic algorithms by storing multiple signature verification methods (first, second, and third methods) in the storage unit. The computation unit can dynamically choose which algorithm to use based on the signature type of the control program, allowing the system to adapt when cryptographic vulnerabilities are discovered without hardware changes.
Solution Approach 2:
The system changes the cryptographic parameter (algorithm type) based on the signature type embedded in the control program. The startup program contains multiple signature verification methods with different cryptographic algorithms, and the system selects the appropriate method by matching the signature type, enabling flexible adaptation to different security requirements and cryptographic standards.
2Adaptability or versatility
If multiple signature verification methods are provided, then the system can transition to different cryptographic algorithms, but the startup program complexity increases
Solution Approach 1:
The patent segments the signature verification functionality into distinct, independent methods (first signature verification method, second signature verification method, third signature verification method). Each method is stored as a separate module in the storage unit, allowing the system to select and execute only the necessary verification method based on the control program's signature type, thereby managing complexity through modular organization.
Solution Approach 2:
The system performs preliminary classification by embedding signature type information in the control program beforehand. The startup program reads this signature type and automatically selects the corresponding verification method, eliminating the need for complex runtime decision-making and simplifying the execution flow through pre-configured matching.
3Device complexity
If a single normal boot program is used, then the boot process is simple, but the system lacks redundancy and becomes vulnerable when the boot program is compromised
Solution Approach 1:
The patent applies local quality by associating different cryptographic algorithm strengths with different control program types. Not all control programs require the same level of verification - the system matches the verification method to the specific program's signature type, providing appropriate security redundancy where needed while maintaining simplicity where sufficient.
Solution Approach 2:
The system creates a composite security structure by combining multiple signature verification methods with different cryptographic algorithms within the same startup program. This composite approach provides layered security redundancy, where if one algorithm is compromised, other algorithms within the composite structure remain available for verification.
Data Source
AI summary
A computation unit that performs a computation process for a program and a storage unit that stores a first control program and a first startup program that executes signature verification for the first control program are provided. The first startup program can execute a plurality of signature verification methods, and executes a process for determining, among the plurality of signature verification methods, a signature verification method that corresponds to a signature type for the first control program and obtaining a result of executing signature verification by the signature verification method.