FPSoC Secure Boot Authentication Against Differential Power Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Embedded devices, such as systems-on-chip (SoCs), face vulnerabilities to device loss, theft, data theft, cloning, reverse engineering, and denial of service attacks due to inadequate security measures during boot and operation, particularly in securing the loading of malware and maintaining integrity of information.
Innovation Solution
A system-on-chip (SoC) with dedicated hardware including a processing unit, internal memories, an authentication engine, and a decryption engine, coupled with a storage device containing boot code for secure boot operations, which executes to validate boot information and load a secure boot image, ensuring the integrity and authenticity of the boot process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional boot processes are used in embedded devices, then device simplicity and ease of operation are maintained, but security vulnerabilities allow malware insertion, device cloning, and data theft
Solution Approach 1:
The boot process is divided into multiple authenticated stages: a first stage boot loader that authenticates against a root of trust, and a second stage boot loader that is authenticated by the first stage. Each stage independently validates the previous stage's integrity before executing, creating segmented security zones that prevent malware from compromising the entire system.
Solution Approach 2:
The system performs preliminary authentication of boot images before execution. The first stage boot loader authenticates the second stage boot loader image against a root of trust stored in non-volatile memory, and the second stage boot loader authenticates application images before loading them into memory, preventing malware insertion at any stage.
2Reliability
If boot images are stored in non-volatile memory, then data persistence is achieved, but the boot images become vulnerable to unauthorized modification and cloning
Solution Approach 1:
The system performs preliminary authentication of boot images stored in non-volatile memory before execution. The first stage boot loader authenticates the second stage boot loader image against a root of trust, and the second stage boot loader authenticates application images before loading them into memory, preventing malware insertion at any stage.
Solution Approach 2:
The authentication engine acts as an intermediary between the non-volatile memory storage and the execution environment. It validates cryptographic signatures of boot images against stored roots of trust, mediating the transition from persistent storage to executable memory and preventing unauthorized modifications.
3Reliability
If authentication engines and decryption engines are added to the SoC, then security against differential power analysis and malware is improved, but device complexity and manufacturing cost increase
Solution Approach 1:
The authentication engine and decryption engine are merged into the existing SoC architecture, working together with the processing unit and memory subsystems. The authentication engine validates cryptographic signatures while the decryption engine decrypts boot images, and both work seamlessly with the existing boot loader stages to provide comprehensive security without requiring entirely separate hardware systems.
Data Source
AI summary
A system generally relating to an SoC, which may be a field programmable SoC (“FPSoC”), is disclosed. In this SoC, dedicated hardware includes a processing unit, a first internal memory, a second internal memory, an authentication engine, and a decryption engine. A storage device is coupled to the SoC. The storage device has access to a boot image. The first internal memory has boot code stored therein. The boot code is for a secure boot of the SoC. The boot code is configured to cause the processing unit to control the secure boot.