IoT Module Secure Boot Memory Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Internet of Things (IoT) devices face security risks due to low-cost security systems and the potential for boot firmware hacking or unintended rollback, especially when manufactured by different entities using the same IoT module, which lacks unique security keys and secure boot functions.
Innovation Solution
An IoT module with a memory structure including a boot area for boot firmware and a security area for storing firmware release versions and authentication keys, utilizing a processor to perform secure boot and rollback protection by comparing firmware versions and authentication information, and generating a hardware unique key for secure access to the security area.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If low-cost security systems are used in IoT modules to reduce manufacturing costs, then manufacturing cost is reduced, but security reliability deteriorates making boot firmware vulnerable to hacking and rollback attacks
Solution Approach 1:
The memory is divided into two distinct areas: a boot area for storing boot firmware and a security area for storing security information including authentication keys and firmware version. This segmentation allows the security area to be protected with restricted access while the boot area remains accessible, providing cost-effective security without requiring expensive dedicated security hardware.
Solution Approach 2:
The processor performs preliminary security checks during the boot process by reading security information from the security area, verifying authentication keys, and comparing firmware versions before executing boot firmware. This preliminary verification prevents hacking and rollback attacks before they can compromise the system, maintaining security reliability without additional hardware costs.
2Ease of manufacture
If different manufacturers produce IoT modules with the same boot firmware to reduce module costs, then module cost is reduced, but security reliability deteriorates as boot firmware can be easily hacked or rolled back
Solution Approach 1:
Each IoT module is configured with a unique authentication key stored in its security area, while sharing the same boot firmware in the boot area. This local differentiation through unique authentication keys allows multiple manufacturers to use the same boot firmware image while maintaining individual security identities, preventing unauthorized hacking and rollback attacks across different module instances.
Solution Approach 2:
The processor reads the firmware version from the security area and compares it with the boot firmware during the boot process. This feedback mechanism detects any unauthorized modifications or rollback attempts by verifying version consistency, ensuring boot firmware security even when modules from different manufacturers use the same firmware image.
3Reliability
If a security area with restricted access is implemented to prevent hacking, then security reliability is improved, but device complexity increases
Solution Approach 1:
The processor performs multiple security functions using the same security area structure: storing authentication keys, storing firmware version information, and performing verification comparisons. This multi-functional use of a single security area avoids the need for separate dedicated security hardware components, improving security reliability while minimizing increases in device complexity.
Data Source
AI summary
An Internet of Things module includes a memory including a boot area for storing boot firmware and first security information and a security area for storing a firmware release version and second security information, and a processor to perform a boot process of the Internet of Things module using the boot firmware in the boot area and to determine whether the boot process of the Internet of Things module is progressed or stopped through comparing the first security information in the boot area with the second security information in the security area and through comparing a version of the boot firmware in the boot area with the firmware release version in the security area.