Firmware authentication and security boot system and method based on hardware

Abstract

The invention relates to the technical field of computers, and discloses a hardware-based firmware authentication and security boot system and method and a medium, the system comprises a trusted root, a hardware authentication module, a firmware storage unit and a boot loader, through cooperation of the trusted root module, the hardware authentication module and the boot loader, effective protection of device firmware is realized, and the security of the device firmware is improved. And the safety and the reliability of the system are obviously improved. According to the method, firmware authentication and safe guiding are achieved through hardware, the firmware is difficult to bypass or tamper by an attacker, the firmware is authenticated during starting, monitoring can be conducted during running, it is ensured that the firmware is always in a trusted state, dependence on a main CPU is reduced through a hardware module, and the overall efficiency of the system is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a hardware-based firmware authentication and secure boot system and method. Background Art

[0002] With the development of computer hardware and software technology, the traditional BIOS (Basic Input / Output System) has been gradually replaced by the more powerful UEFI (Unified Extensible Firmware Interface). However, the existing UEFI firmware still has room for improvement in terms of boot speed and security. The existing boot process is relatively complicated, resulting in a long boot time, and it also faces many challenges in security, such as malware intrusion. Therefore, there is an urgent need for a boot system that can improve boot speed and enhance security. With the popularity of embedded systems and IoT devices, it is particularly important to ensure the security and reliability of the device during the boot process. Traditional software-level security measures are vulnerable to various attacks, such as tampering, forgery, and malware injection. Therefore, hardware-based firmware authentication and secure boot have become key technologies to ensure system integrity and security.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present application, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical components or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] In view of the defects of the prior art, the present invention provides a hardware-based firmware authentication and secure boot system and method, which ensures through hardware means that the firmware loaded by the device during the startup process is verified and not tampered with, thereby improving the overall security of the system.

[0006] In order to solve the technical problem, the technical solution adopted by the present invention is: a hardware-based firmware authentication and secure boot system, comprising:

[0007] A root of trust, which is a hardware security module that stores and manages cryptographic keys used for data encryption, authentication, and digital signatures;

[0008] A firmware storage unit, used for persisting firmware images and data of storage devices;

[0009] The hardware authentication module is connected to the firmware storage unit and the trusted root, and is used to read and verify the integrity and authenticity of the firmware and authenticate the firmware when the device is started;

[0010] The boot loader is connected to the firmware storage unit and loads and starts the firmware after the firmware passes the authentication.

[0011] Furthermore, the hardware authentication module performs periodic checks on the authenticated firmware to ensure that the firmware has not been tampered with; the periodic checks are hash checks, and a hash value corresponding to the firmware is generated by a hash algorithm. When the firmware is modified, the corresponding hash value changes. The firmware is detected whether it has been tampered with by comparing the hash values, and the current hash value is compared with the hash value at the time of authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken.

[0012] Furthermore, the trusted root stores the device's unique private key and the manufacturer's public key certificate, and generates and verifies digital signatures.

[0013] Furthermore, the firmware storage unit adopts a secure NOR flash memory, and the firmware stored in the firmware storage unit is encrypted and signed.

[0014] Furthermore, the boot loader is stored in the read-only memory and is used to initialize the hardware and load the operating system kernel into the memory when the system starts.

[0015] Furthermore, the encryption keys within the root of trust require authorized access.

[0016] The present invention discloses a hardware-based firmware authentication and secure boot system, comprising the following steps:

[0017] S01, start initialization, when the device passes or restarts, the trusted root and the firmware storage unit perform initialization operations, after the trusted root initialization is completed, the encryption key and security policy stored in the trusted root are loaded and activated;

[0018] S02, firmware authentication, the hardware authentication module reads the firmware to be started from the firmware storage unit, and then uses the public key of the signature authentication managed by it to verify the digital signature of the firmware. If it is successful, the startup process is terminated and an alarm is issued. If it is verified, the next step is continued;

[0019] S03, boot loading, after the firmware passes the authentication, the boot loader starts to run, loads the authenticated firmware image into the memory, and then detects whether the hardware components are working properly. If the hardware components are working properly, it continues to perform the initialization task and then starts the operating system or application;

[0020] S04, periodic inspection: During the operation of the firmware, the hardware authentication module performs periodic inspection on the firmware to ensure that it has not been tampered with.

[0021] Furthermore, the periodic check is a hash check, which generates a hash value corresponding to the firmware through a hash algorithm. When the firmware is modified, the corresponding hash value changes. The firmware is detected whether it has been tampered with by comparing the hash value. The current hash value is compared with the hash value during authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken.

[0022] Furthermore, when the hash check fails, the measures taken are rebooting or entering a safe mode.

[0023] The present invention also discloses a storage medium storing program instructions, which, when running, execute the hardware-based firmware authentication and secure booting method as described above.

[0024] The hardware-based firmware authentication and secure boot system, method and medium provided by the embodiments of the present disclosure can achieve the following technical effects: High security: Firmware authentication and secure boot are implemented through hardware, which is difficult to be bypassed or tampered with by attackers.

[0025] Real-time protection: Not only does it authenticate the firmware at boot time, it also monitors it during operation to ensure that the firmware is always trusted.

[0026] Low overhead: The use of hardware modules reduces the dependence on the main CPU and improves the overall efficiency of the system.

[0027] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] One or more embodiments are exemplarily described by corresponding drawings, which do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements, and the drawings do not constitute a scale limitation, and wherein:

[0029] Figure 1 is a functional block diagram of the system described in Example 1;

[0030] Figure 2 It is a flow chart of the method described in Example 2. DETAILED DESCRIPTION

[0031] In order to be able to understand the features and technical contents of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The attached drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and devices can be simplified for display.

[0032] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B indicates: A or B.

[0033] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0034] The term "correspondence" may refer to an association relationship or a binding relationship. The correspondence between A and B means that there is an association relationship or a binding relationship between A and B.

[0035] Example 1

[0036] This embodiment discloses a hardware-based firmware authentication and secure boot system, which aims to ensure that the firmware loaded by the device during the boot process is verified and not tampered with by hardware means, thereby improving the overall security of the system. Specifically, by designing a trustworthy hardware platform to verify and load firmware, it is ensured that only authenticated firmware is executed, thereby preventing the device from being tampered with, forged, and attacked by malicious software. Figure 1 As shown, it includes the following modules:

[0037] The root of trust is implemented through a hardware security module (HSM), which is a dedicated hardware device designed to provide a high level of security for cryptographic operations and key management. HSM protects the encryption process by generating, protecting and managing keys used to encrypt and decrypt data and create digital signatures and certificates. It is used to protect sensitive data and keys and ensure information security. In this embodiment, the root of trust provides physical isolation so that sensitive information and critical operations can be run in a safer environment, denying direct access to the main processor. The root of trust is responsible for managing encryption keys, which are used for security operations such as data encryption, identity authentication, and digital signatures. Specifically, the HSM internally stores the device's unique private key and the manufacturer's public key certificate, generates and verifies digital signatures, and ensures the authenticity and integrity of the firmware. The keys stored in the root of trust are only authorized for access to prevent unauthorized access.

[0038] Firmware storage unit: A storage area for persistent storage of firmware images and data for a device. In this embodiment, secure flash memory, such as secure NOR flash, is used to provide hardware-protected secure storage for security keys, certificates, hash passwords, specific application data, configuration data, code version information, and biometric sensor data. Firmware needs to be encrypted and signed when stored. The hardware authentication module reads the firmware data at startup and uses the public key provided by the trusted root module to perform digital signature verification.

[0039] Hardware Authentication Module: The hardware authentication module relies on a root of trust to perform its functions. During the secure boot process, key security checks are performed, such as verifying the firmware signature, and the root of trust provides the necessary secure storage and processing capabilities to ensure the security of this process. The existence of the root of trust ensures that the hardware authentication module can operate in a secure environment, preventing any potential interference or deception with the authentication process. This module is responsible for reading and verifying the integrity and authenticity of the firmware and is responsible for authenticating the firmware when the device starts. When the device starts, the hardware authentication module first checks whether there are any signs of hardware tampering, such as physical intrusion. If no anomalies are found, the module will start to verify the firmware.

[0040] The hardware authentication module periodically performs hash verification on key parts of the firmware. Hash algorithms (such as SHA-3) are widely used in digital signatures, message authentication, and other fields due to their fast computing speed and low resource usage. These algorithms can generate a hash value of a fixed length to represent the uniqueness of the data. When the firmware is modified, its hash value will also change, so by comparing the hash value, it is effective to detect whether the firmware has been tampered with. The current hash value is compared with the hash value at the time of authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken, such as rebooting or entering safe mode.

[0041] Boot loader: This program is responsible for loading and starting the firmware after it has been authenticated. Designed as a lightweight, secure component stored in read-only memory (ROM), the boot loader is a critical component in embedded systems that is responsible for initializing the hardware and loading the operating system kernel into memory when the system boots up. The basic functions of the boot loader include initializing the hardware, loading the operating system kernel into memory, and may include performing some specific operating system startup tasks. These functions ensure that the operating system can start and run in the correct hardware environment and also prevent itself from being tampered with. It is responsible for loading authenticated firmware and transferring control to the firmware.

[0042] Example 2

[0043] This embodiment discloses a hardware-based firmware authentication and secure boot method, such as Figure 2As shown, the following steps are included:

[0044] S01, start initialization, when the device passes or restarts, the trusted root and the firmware storage unit perform initialization operations, after the trusted root initialization is completed, the encryption key and security policy stored in the trusted root are loaded and activated;

[0045] S02, firmware authentication, the hardware authentication module reads the firmware to be started from the firmware storage unit, and then uses the public key of the signature authentication managed by it to verify the digital signature of the firmware. If it is successful, the startup process is terminated and an alarm is issued. If it is verified, the next step is continued;

[0046] S03, boot loading, after the firmware passes the authentication, the boot loader starts to run, loads the authenticated firmware image into the memory, and then detects whether the hardware components are working properly. If the hardware components are working properly, it continues to perform the initialization task and then starts the operating system or application;

[0047] S04, periodic inspection: During the operation of the firmware, the hardware authentication module performs periodic inspection on the firmware to ensure that it has not been tampered with.

[0048] In this embodiment, the periodic check is a hash check, and a hash value corresponding to the firmware is generated by a hash algorithm. When the firmware is modified, the corresponding hash value changes. The firmware is detected whether it has been tampered with by comparing the hash value. The current hash value is compared with the hash value during authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken, such as rebooting or entering safe mode.

[0049] Example 3

[0050] An embodiment of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to execute the above-mentioned method for ...

[0051] The computer-readable storage medium mentioned above may be a transient computer-readable storage medium or a non-transitory computer-readable storage medium.

[0052] The present invention provides a hardware-based firmware authentication and secure boot system, method and mechanism, which realizes effective protection of device firmware through the collaboration of trusted root, hardware authentication module and boot loader, and significantly improves the security and reliability of the system. The method is applicable to various embedded systems and IoT devices that require high security. Such as smart home devices, industrial control systems, etc., to ensure that these devices are protected from malware attacks during startup and operation. It can also be applied to embedded systems: such as automotive electronic systems, medical equipment, etc., to ensure their security and reliability.

[0053] The technical solution of the embodiment of the present disclosure can be embodied in the form of a software product, which is stored in a storage medium and includes one or more instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiment of the present disclosure. The aforementioned storage medium may be a non-transient storage medium, including: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes, or a transient storage medium.

[0054] The above description and the accompanying drawings fully illustrate the embodiments of the present disclosure so that those skilled in the art can practice them. Other embodiments may include structural, logical, electrical, process and other changes. The embodiments represent only possible changes. Unless explicitly required, separate components and functions are optional, and the order of operation may vary. The parts and features of some embodiments may be included in or replace the parts and features of other embodiments. Moreover, the words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and the claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of listings containing one or more associated ones. In addition, when used in the present application, the term "comprise" and its variants "comprises" and / or comprising refer to the presence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof. In the absence of further restrictions, the elements defined by the sentence "comprising a ..." do not exclude the presence of other identical elements in the process, method or device comprising the elements. In this article, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can refer to the description of the method part.

Claims

1. A hardware-based firmware authentication and secure boot system, characterized in that: include: A root of trust, which is a hardware security module that stores and manages cryptographic keys used for data encryption, authentication, and digital signatures; A firmware storage unit, used for persisting firmware images and data of storage devices; The hardware authentication module is connected to the firmware storage unit and the trusted root, and is used to read and verify the integrity and authenticity of the firmware and authenticate the firmware when the device is started; The boot loader is connected to the firmware storage unit and loads and starts the firmware after the firmware passes the authentication.

2. The hardware-based firmware authentication and secure boot system according to claim 1, characterized in that: The hardware authentication module performs periodic checks on the authenticated firmware to ensure that the firmware has not been tampered with; the periodic checks are hash checks, and a hash value corresponding to the firmware is generated by a hash algorithm. When the firmware is modified, the corresponding hash value changes. The firmware is detected whether it has been tampered with by comparing the hash values, and the current hash value is compared with the hash value at the time of authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken.

3. The hardware-based firmware authentication and secure boot system according to claim 1, characterized in that: The trusted root stores the device's unique private key and the manufacturer's public key certificate, and generates and verifies digital signatures.

4. The hardware-based firmware authentication and secure boot system according to claim 1, characterized in that: The firmware storage unit adopts secure NOR flash memory, and the firmware stored in the firmware storage unit is encrypted and signed.

5. The hardware-based firmware authentication and secure boot system according to claim 1, characterized in that: The boot loader is stored in read-only memory and is used to initialize the hardware and load the operating system kernel into memory when the system starts.

6. The hardware-based firmware authentication and secure boot system according to claim 1, characterized in that: Cryptographic keys within the root of trust require authorized access.

7. A hardware-based firmware authentication and secure boot system, characterized in that: The following steps are involved: S01, start initialization, when the device passes or restarts, the trusted root and the firmware storage unit perform initialization operations, after the trusted root initialization is completed, the encryption key and security policy stored in the trusted root are loaded and activated; S02, firmware authentication, the hardware authentication module reads the firmware to be started from the firmware storage unit, and then uses the public key of the signature authentication managed by it to verify the digital signature of the firmware. If it is successful, the startup process is terminated and an alarm is issued. If it is verified, the next step is continued; S03, boot loading, after the firmware passes the authentication, the boot loader starts to run, loads the authenticated firmware image into the memory, and then detects whether the hardware components are working properly. If the hardware components are working properly, it continues to perform the initialization task and then starts the operating system or application; S04, periodic inspection: During the operation of the firmware, the hardware authentication module performs periodic inspection on the firmware to ensure that it has not been tampered with.

8. The hardware-based firmware authentication and secure boot method according to claim 7, characterized in that: The periodic check is a hash check, which generates a hash value corresponding to the firmware through a hash algorithm. When the firmware is modified, the corresponding hash value changes. The firmware is detected whether it has been tampered with by comparing the hash value. The current hash value is compared with the hash value during authentication. If inconsistency is found, a security alarm is triggered and corresponding measures are taken.

9. The hardware-based firmware authentication and secure boot method according to claim 8, characterized in that: The measures taken when the hash check fails are rebooting or entering safe mode.

10. A storage medium storing program instructions, characterized in that: When the program instructions are executed, the hardware-based firmware authentication and secure boot method according to any one of claims 7 to 9 is executed.

Images