Control Device Secure Boot Verification via Pre-computed Hashes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing control devices face challenges in achieving high security strength and rapid secure boot processing times, especially when detecting tampering in large programs and data, as they require manual selection of application programs and increased data verification, which can lead to prolonged processing times despite the use of hardware security modules.
Innovation Solution
A control device with isolated processing environments, where a verification value is generated and stored before the control device is stopped, allowing for advanced verification upon activation, ensuring high security strength and reduced secure boot processing time by comparing expected and generated verification values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the amount of program and data for which tampering is detected is increased, then security strength against tampering is improved, but the period of time for secure boot processing is increased
Solution Approach 1:
The patent applies preliminary action by generating verification values for all application programs in advance, before the secure boot processing occurs. During normal operation, verification values are pre-computed and stored. When secure boot is needed, the system only needs to retrieve and compare these pre-generated values against the actual program data, rather than computing verification values from scratch during the boot process. This shifts the computational burden to a time when the system is already running and has more flexibility.
Solution Approach 2:
The patent uses copying by creating and storing verification values (such as hash values or digital signatures) as separate data structures that replicate the essential security properties of the original application programs. These verification values are copied and stored in a verification data structure that can be quickly compared against the actual programs during secure boot, without requiring re-computation of the entire verification process.
2Reliability
If data to be used in verification is updated every time an event occurs, then security strength is improved, but system complexity is increased
Solution Approach 1:
The patent implements feedback by establishing a mechanism where verification data is automatically updated in response to specific events (such as program updates or security incidents). The system monitors for these events and triggers verification value regeneration and updates accordingly. This event-driven feedback loop ensures that the verification data remains current and reflects the actual state of the system, while avoiding unnecessary updates that would increase complexity.
3Loss of time
If manual selection of application programs for verification is performed, then secure boot processing time is reduced, but security coverage is reduced
Solution Approach 1:
The patent applies universality by designing a verification system that can handle multiple application programs simultaneously through a unified verification data structure. The system is configured to verify all application programs by default, but can be extended to verify additional programs without requiring manual selection or reconfiguration. The verification mechanism is universal and applies to any program that is registered in the system, providing both broad security coverage and efficient processing through automated inclusion of all programs.
Data Source
AI summary
A first processing environment includes: a control processing unit configured to execute control processing on a control subject; a first storage area for storing data for controlling the control subject; and a verification determination unit. A second processing environment includes: a second storage area for storing an expected value; a verification value generation unit; and a verification execution unit. The verification value generation unit generates the verification value before the control processing is stopped. The verification execution unit executes comparison processing of comparing the expected value and the verification value before the control processing is activated. When the comparison result indicates a verification success, the verification determination unit executes determination processing of determining that the control processing is to be activated, and executes determination processing of determining that activation of the control processing is to be stopped when the comparison result indicates a verification failure.