Firmware security deployment method and device, equipment, medium and program product

Abstract

The invention relates to a firmware security deployment method and device, equipment, a medium and a program product. The firmware security deployment method is applied to a security chip, and comprises the following steps: receiving a firmware deployment instruction sent by a firmware chip; performing firmware signature verification based on a first firmware manufacturer certificate corresponding to first manufacturer identification information in the firmware deployment instruction; after the firmware verification is passed, executing decryption processing of the encrypted firmware file; the method comprises the following steps: decrypting a firmware file to obtain a decrypted firmware file, performing re-encryption processing on the decrypted firmware file to obtain a re-encrypted firmware file, and sending the re-encrypted firmware file to a firmware chip to enable the firmware chip to execute firmware deployment operation based on the re-encrypted firmware file, so that firmware signature verification in the firmware deployment process can be performed by introducing a security chip; and an encryption mode is adopted for transmission, so that the security and reliability of firmware files and data in the firmware deployment process are ensured, and the security of firmware deployment is further improved.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a firmware security deployment method, device, equipment, medium and program product. Background Art

[0002] Currently, the operation of terminals relies on a variety of firmware, which is responsible for controlling device hardware and providing core functions. However, firmware often hides potential security vulnerabilities, which may cause the device to leak sensitive data during information transmission, thereby triggering forgery attacks and causing service interruptions. Therefore, how to achieve secure deployment of firmware is a technical problem that needs to be solved urgently. Summary of the invention

[0003] In order to solve the above technical problems, the present disclosure provides a firmware security deployment method, device, equipment, medium and program product.

[0004] A first aspect of an embodiment of the present disclosure provides a firmware security deployment method, which is applied to a security chip, including:

[0005] Receive a firmware deployment instruction sent by the firmware chip, where the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed;

[0006] Acquire a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate;

[0007] After the firmware signature is verified, the firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain the decrypted firmware file;

[0008] The decrypted firmware file is re-encrypted to obtain a re-encrypted firmware file, and the re-encrypted firmware file is sent to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

[0009] A second aspect of an embodiment of the present disclosure provides a firmware security deployment device, applicable to a security chip, including:

[0010] A firmware deployment instruction receiving module, used to receive a firmware deployment instruction sent by a firmware chip, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed;

[0011] A firmware signature verification module, used to obtain a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate;

[0012] The firmware processing module is used to obtain the firmware encryption key based on the firmware encryption key index after the firmware signature verification passes, and decrypt the encrypted firmware file according to the firmware encryption key to obtain the decrypted firmware file;

[0013] The firmware deployment module is used to re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

[0014] A third aspect of the embodiments of the present disclosure provides an electronic device, including:

[0015] processor;

[0016] A memory for storing executable instructions;

[0017] Among them, the processor is used to read executable instructions from the memory and execute the executable instructions to implement the firmware security deployment method provided by the first aspect above.

[0018] A fourth aspect of an embodiment of the present disclosure provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor implements the firmware security deployment method provided by the first aspect above.

[0019] A fifth aspect of an embodiment of the present disclosure provides a computer program product, which includes a computer program or instructions, and when the computer program or instructions are executed by a processor, the firmware security deployment method as described in the first aspect above is implemented.

[0020] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:

[0021] The firmware security deployment method, apparatus, device, medium and program product provided by the embodiments of the present disclosure can receive a firmware deployment instruction sent by a firmware chip, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and a first manufacturer identification information corresponding to the firmware to be deployed; after receiving the firmware deployment instruction, the firmware deployment instruction is parsed to obtain the first manufacturer identification information, and then the first firmware manufacturer certificate corresponding to the firmware to be deployed is obtained based on the first manufacturer identification information, and the firmware to be deployed is verified based on the first firmware manufacturer certificate; after the firmware verification passes, the firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain the decrypted firmware. firmware file; re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file, thereby enabling the firmware to be verified through the first firmware manufacturer certificate, and after the verification is passed, the firmware file is decrypted, and when the security chip sends the firmware file to the firmware chip, the decrypted firmware file is continuously encrypted and transmitted, that is, the firmware verification in the firmware deployment process is performed by introducing a security chip, and the firmware verification is passed and the firmware is transmitted in an encrypted manner, so as to ensure the security and reliability of the firmware files and data in the firmware deployment process, thereby improving the security of the firmware deployment. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0024] Figure 1 is a flowchart of a firmware security deployment method provided by an embodiment of the present disclosure;

[0025] Figure 2 is a schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0026] Figure 3 is a flow chart of another firmware security deployment method provided by an embodiment of the present disclosure;

[0027] Figure 4 is a flowchart of a firmware data security destruction method provided by an embodiment of the present disclosure;

[0028] Figure 5 It is a structural diagram of a firmware security deployment device provided by an embodiment of the present disclosure;

[0029] Figure 6 It is a structural schematic diagram of an electronic device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0030] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0031] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0032] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0033] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0034] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0035] Typically, firmware often hides potential security vulnerabilities, which may cause the device to leak sensitive data during information transmission, thereby triggering forgery attacks and causing service interruptions. Therefore, how to achieve secure deployment of firmware is a technical problem that needs to be solved urgently. To address this problem, the embodiments of the present disclosure provide a firmware security deployment method, which is described below in conjunction with specific embodiments.

[0036] Figure 1 This is a flowchart of a firmware security deployment method provided by an embodiment of the present disclosure. The method can be executed by a firmware security deployment device. The firmware security deployment device can be implemented in software and / or hardware. The firmware security deployment device can be configured in an electronic device, such as a server or a terminal, wherein the terminal specifically includes a mobile phone, a computer or a tablet computer, etc. In addition, the method can be applied to Figure 2 The application scenario shown includes a firmware management system 10 and a terminal device 20, wherein the firmware management system 10 and the terminal device 20 can communicate with each other. It can be understood that the firmware security deployment method provided in the embodiment of the present disclosure can also be applied in other scenarios.

[0037] like Figure 2 As shown, the firmware management system 10 can be understood as a server that interacts with the terminal device 20, which can be used to manage the firmware to ensure the normal operation of the terminal device 20; it can also be used to generate a firmware manufacturer certificate based on a private key, and send the firmware manufacturer certificate to the firmware manufacturer, so that the firmware manufacturer certificate presets the firmware manufacturer certificate into the security chip 22; it can also be used to perform hash calculations on firmware files based on a preset hash algorithm to generate a hash value, and determine the hash value as the firmware index corresponding to the firmware file; it can also be used to generate an encryption key index corresponding to the firmware file based on a preset random function, and so on.

[0038] The terminal device 20 includes a software development kit 21 , a security chip 22 , a firmware chip 23 , and a Flash memory 24 .

[0039] The software development kit 21 can be used to create, test, deploy and manage software applications.

[0040] The security chip 22 can be used to verify the firmware based on the firmware manufacturer's certificate, ensure the trust relationship between the firmware management system 10 and the firmware chip 23, and perform authentication during the interaction with the firmware chip 23 to further ensure the security of firmware deployment.

[0041] The firmware chip 23 is a hardware device for storing firmware, and is used for firmware deployment, which may specifically include firmware installation and firmware upgrade.

[0042] The Flash memory 24 is used to store firmware files, which may specifically include storing encrypted and signed firmware files; it may also be used to store data related to the firmware.

[0043] Specifically, the firmware management system 10 can send firmware deployment instructions and / or data destruction instructions to the firmware chip 23. After receiving the firmware deployment instructions and / or data destruction instructions, the firmware chip 23 sends them to the security chip 22. The security chip 22 verifies the signature of the firmware corresponding to the firmware deployment instructions and / or data destruction instructions, and then, after the signature verification is passed, authenticates with the firmware chip 23, and executes operations related to the firmware deployment instructions and / or data destruction instructions after the authentication is passed.

[0044] Combine the following Figure 2 The application scenario shown is Figure 1 The firmware security deployment method shown is introduced, for example, Figure 2 The security chip 22 in the embodiment can execute the method. Figure 1 As shown, the firmware security deployment method provided in this embodiment includes the following steps.

[0045] S110. Receive a firmware deployment instruction sent by a firmware chip, where the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed.

[0046] In the embodiments of the present disclosure, the firmware deployment instruction may be a firmware installation instruction for installing the firmware and a firmware upgrade instruction for upgrading the firmware. The firmware deployment instruction may be an instruction sent to the firmware chip by the firmware management system when it is determined that firmware deployment is required. After receiving the firmware deployment instruction, the firmware chip sends it to the security chip.

[0047] The firmware to be deployed may be firmware to be installed or firmware to be upgraded.

[0048] Firmware files are the carriers that store firmware programs.

[0049] The firmware encryption key index is used to search and manage the encryption key corresponding to the firmware to be deployed. The firmware encryption key index is determined by the firmware management system corresponding to the firmware chip based on a preset random function. Specifically, the firmware management system determines a group of encryption keys for encrypting and decrypting the firmware file of the firmware to be deployed corresponding to the firmware deployment instruction from the pre-set multiple groups of encryption keys based on the preset random function, and determines the corresponding index as the firmware encryption key index.

[0050] The first manufacturer identification information may be the manufacturer's ID or the manufacturer's unique identifier.

[0051] Specifically, the security chip can receive the firmware deployment instruction sent by the firmware chip in real time.

[0052] S120: Obtain a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate.

[0053] In the embodiment of the present disclosure, the first firmware manufacturer certificate may be generated by the firmware management system based on a private key provided by the firmware manufacturer and pre-set in the security chip.

[0054] Specifically, after receiving the firmware deployment instruction, the security chip parses the firmware deployment instruction, obtains the first manufacturer identification information corresponding to the firmware to be deployed in the firmware deployment instruction, obtains the first firmware manufacturer certificate based on the first manufacturer identification information, and after obtaining the first firmware manufacturer certificate, obtains its corresponding public key from the first firmware manufacturer certificate, and performs firmware verification on the firmware to be deployed based on the public key, so as to determine whether the firmware to be deployed is from the manufacturer. Among them, the process of firmware verification is similar to the specific implementation method of the existing verification process, which will not be repeated here.

[0055] S130: After the firmware signature verification passes, a firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain a decrypted firmware file.

[0056] Specifically, after determining that the firmware signature has passed, the security chip obtains the firmware encryption index from the firmware deployment instruction, obtains the firmware encryption key based on the firmware encryption index, and then decrypts the encrypted firmware file in the firmware deployment instruction based on the firmware encryption key to obtain the decrypted firmware file, thereby ensuring the security and reliability of the firmware file by encrypting and decrypting the encrypted firmware file.

[0057] S140: re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

[0058] In the embodiment of the present disclosure, the firmware deployment operation may include a first installation operation of the firmware, and may also include an upgrade operation of the installed firmware.

[0059] Specifically, after obtaining the decrypted firmware file, the security chip re-encrypts the decrypted firmware file to obtain a re-encrypted firmware file to ensure the security of the firmware file during transmission to the firmware chip, and sends the re-encrypted firmware file to the firmware chip, so that the firmware chip performs firmware deployment operations based on the re-encrypted firmware file.

[0060] In an embodiment of the present disclosure, a firmware deployment instruction sent by a firmware chip can be received, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and a first manufacturer identification information corresponding to the firmware to be deployed; after receiving the firmware deployment instruction, the firmware deployment instruction is parsed to obtain the first manufacturer identification information, and then the first firmware manufacturer certificate corresponding to the firmware to be deployed is obtained based on the first manufacturer identification information, and the firmware to be deployed is verified based on the first firmware manufacturer certificate; after the firmware verification passes, the firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain the decrypted firmware file; the decrypted firmware is The firmware file is re-encrypted to obtain a re-encrypted firmware file, and the re-encrypted firmware file is sent to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file. As a result, the firmware can be verified through the first firmware manufacturer certificate, and the firmware file is decrypted after the verification is passed. When the security chip sends the firmware file to the firmware chip, the decrypted firmware file is continuously encrypted and transmitted. That is to say, the firmware verification in the firmware deployment process is performed by introducing a security chip, and the firmware is transmitted in an encrypted manner based on the firmware verification. This ensures the security and reliability of the firmware files and data in the firmware deployment process, thereby improving the security of the firmware deployment.

[0061] In the embodiment of the present disclosure, the firmware deployment instruction also includes a firmware index, and the firmware index is used by the terminal device to search and manage the firmware to be deployed.

[0062] The firmware index is determined by a hash value obtained by hashing a firmware file corresponding to the firmware to be deployed according to a preset hash algorithm by a firmware management system corresponding to the firmware chip.

[0063] Specifically, after acquiring the firmware file corresponding to the firmware to be deployed, the firmware management system performs hash processing on the firmware file based on a preset hash algorithm to obtain a hash value, and determines the hash value as the firmware index for uniquely identifying the firmware file.

[0064] In some embodiments of the present disclosure, after obtaining the firmware deployment instruction, the security chip can parse the firmware deployment instruction to obtain the firmware index, and after obtaining the decrypted firmware file, perform hash processing on the decrypted firmware file based on a preset hash algorithm to obtain a target hash value, and compare the target hash value with the firmware index to determine the integrity of the firmware file.

[0065] In the disclosed embodiment, by attaching a firmware index in the firmware deployment instruction, the terminal device's management efficiency of the firmware can be improved. At the same time, it is convenient for the security chip to further verify the integrity of the firmware file, thereby improving the security of the firmware upgrade.

[0066] In the disclosed embodiment, before the security chip receives the firmware deployment instruction sent by the firmware chip, session authentication is performed to further improve the security of data transmission.

[0067] Figure 3 is a flowchart of another firmware security deployment method provided by an embodiment of the present disclosure, such as Figure 3 As shown, the firmware security deployment method may specifically include the following steps:

[0068] S310: Receive an authentication session request sent by a firmware chip, where the authentication session request includes a first encrypted random number obtained by encrypting a first random number by the firmware chip based on an authentication session key.

[0069] In the disclosed embodiment, an authentication session key is preset in the security chip for authentication with the firmware chip.

[0070] Specifically, before sending the firmware deployment instruction to the security chip, the firmware chip encrypts the first random number based on the authentication session key to obtain a first encrypted random number, generates an authentication session request based on the first encrypted random number, and sends it to the security chip. The security chip can receive the authentication session request sent by the firmware chip in real time.

[0071] S320. Decrypt the first encrypted random number based on the authentication session key to obtain a second random number, and return the second random number to the firmware chip, so that the firmware chip determines whether the authentication is successful based on the first random number and the second random number, and sends a firmware deployment instruction to the security chip after determining that the authentication is successful.

[0072] Specifically, after receiving the authentication session request, the security chip parses the authentication session request, obtains a first encrypted random number, and then decrypts the first encrypted random number based on a preset authentication session key to obtain a second random number, and sends the second random number to the firmware chip, so that the firmware chip determines whether the authentication is successful based on the first random number and the second random number, and sends a firmware deployment instruction to the security chip after determining that the authentication is successful, and does not send a firmware deployment instruction to the security chip if the authentication fails.

[0073] S330: Receive a firmware deployment instruction sent by the firmware chip, where the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed.

[0074] S340: Obtain a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate.

[0075] S350: After the firmware signature is verified, a firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain a decrypted firmware file.

[0076] It should be noted that the specific implementation of steps S330-S350 is similar to the specific implementation of steps S110-S130 in the above embodiment of the present disclosure, and will not be repeated here.

[0077] S360: re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

[0078] In the disclosed embodiment, re-encrypting the decrypted firmware file to obtain the re-encrypted firmware file may specifically include: re-encrypting the decrypted firmware file based on the target session key to obtain the re-encrypted firmware file.

[0079] The target session key is generated by negotiation between the security chip and the firmware chip during the authentication process. The specific target session key negotiation generation process is similar to the existing implementation method of generating a session key during the authentication process, and will not be described in detail here.

[0080] Specifically, after obtaining the decrypted firmware file, the security chip re-encrypts the decrypted firmware file based on the target session key generated during the authentication process to obtain the re-encrypted firmware file, and sends the re-encrypted firmware file to the firmware chip. After receiving the re-encrypted firmware file, the firmware chip decrypts the re-encrypted firmware file based on the target session key, and executes the firmware deployment operation to complete the firmware deployment.

[0081] In the disclosed embodiment, before receiving the firmware deployment instructions sent by the firmware chip, it is possible to authenticate with the firmware chip, establish a secure channel after authentication, and then execute the transmission and interaction of firmware deployment instructions, firmware files and related data, thereby further improving the security of firmware deployment.

[0082] In the disclosed embodiment, after the firmware chip performs the firmware deployment operation based on the re-encrypted firmware file, the terminal device or the firmware management system will respond to the preset conditions by sending a destruction instruction to the firmware chip to cause the firmware chip and / or the security chip to execute the firmware data security destruction to further ensure the security of the firmware. The preset conditions may be a user clicking a data destruction button, reaching a preset time interval, etc.

[0083] Figure 4 is a flowchart of a firmware data security destruction method provided by an embodiment of the present disclosure, such as Figure 4 As shown, the firmware data security destruction method may specifically include the following steps:

[0084] S410: Receive a target authentication session request sent by a firmware chip, where the target authentication session request includes a third encrypted random number obtained by encrypting a third random number by the firmware chip based on an authentication session key.

[0085] S420. Decrypt the third encrypted random number based on the authentication session key to obtain a fourth random number, and return the fourth random number to the firmware chip, so that the firmware chip determines whether the authentication is successful based on the third random number and the fourth random number, and sends a data destruction instruction to the security chip after determining that the authentication is successful.

[0086] Specifically, when the firmware management system or terminal device determines that it is necessary to execute firmware data security destruction, it sends a data destruction instruction to the firmware chip. Before sending the data destruction instruction to the security chip, the firmware chip sends a target authentication session request to the security chip for authentication to ensure reliability with the security chip.

[0087] It should be noted that steps S410-S420 are similar to the specific implementation of the authentication between the firmware chip and the firmware chip before receiving the firmware deployment instruction sent by the firmware chip in the above embodiment of the present disclosure, and will not be repeated here.

[0088] S430: Receive a data destruction instruction sent by the firmware chip, where the data destruction instruction includes a target firmware index corresponding to the data to be destroyed, second manufacturer identification information corresponding to the data to be destroyed, and command identification information.

[0089] In the embodiment of the present disclosure, the target firmware index can be understood as the index of the firmware corresponding to the data to be destroyed, that is, determining which firmware's related data is to be destroyed.

[0090] The second manufacturer identification information may be understood as unique identification information of the manufacturer corresponding to the firmware corresponding to the data to be destroyed, such as the manufacturer ID.

[0091] The command identification information is used to determine whether to agree to execute the data destruction instruction. Data destruction can only be executed when the command identification information is agreed.

[0092] Specifically, when the authentication is successful, the security chip receives the data destruction instruction sent by the firmware chip in real time.

[0093] S440: Obtain a second firmware manufacturer certificate based on the second manufacturer identification information, and perform firmware signature verification based on the second firmware manufacturer certificate.

[0094] It should be noted that the specific implementation of the firmware signature verification in step S440 is similar to the specific implementation of obtaining the first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information in step S120 in the above embodiment of the present disclosure, and performing firmware signature verification on the firmware to be deployed based on the first manufacturer identification information, and will not be repeated here.

[0095] S450: After the firmware signature is verified, determine the target firmware corresponding to the data destruction instruction based on the target firmware index, and determine the data to be destroyed according to the target firmware.

[0096] Specifically, after determining that the firmware signature verification has passed, the security chip determines that the data destruction instruction corresponds to the target firmware according to the target firmware index, and determines the relevant data corresponding to the target firmware as the data to be destroyed.

[0097] S460, performing a destruction operation on the data to be destroyed based on the command identification information, where the data to be destroyed includes a target firmware file corresponding to the target firmware, a target encryption key, a second firmware manufacturer certificate, and a target authentication session key.

[0098] The destruction operation can be understood as deleting the data to be destroyed stored internally.

[0099] Specifically, after determining the data to be destroyed, the security chip parses the command identification information, and when determining that the identifier corresponding to the command identification information is an approval identifier, the data to be destroyed is destroyed.

[0100] S470: Return the self-destruction instruction to the firmware chip, so that the firmware chip performs a self-destruction operation on the data to be destroyed based on the self-destruction instruction after receiving the self-destruction instruction.

[0101] Specifically, after the security chip executes the destruction operation and the destruction is completed, it returns the destruction completion information to the firmware chip and returns the self-destruction instruction to the firmware chip, so that after receiving the self-destruction instruction, the firmware chip deletes the data to be destroyed stored in it based on the self-destruction instruction, and clears the data to be destroyed in the Flash memory corresponding to the firmware chip at the same time, so as to achieve the firmware being irreversible.

[0102] In the embodiments of the present disclosure, the firmware deployment operation can be performed on the firmware chip, and after the firmware is deployed, the relevant data of the firmware can be destroyed. Before the data destruction instruction is transmitted, authentication is performed between the security chip and the firmware chip, thereby improving the reliability of data transmission. By destroying the relevant data of the firmware, the effect of avoiding data leakage or data attack is achieved, thereby further improving the security of the firmware.

[0103] Figure 5 It is a structural diagram of a firmware security deployment device provided by an embodiment of the present disclosure.

[0104] In the embodiments of the present disclosure, the firmware security deployment device can be set in an electronic device and is understood as a part of the functional modules in the above electronic device. Specifically, the electronic device can be a server or a terminal, wherein the terminal specifically includes a mobile phone, a computer or a tablet computer, etc., which is not limited here.

[0105] like Figure 5 As shown, the firmware security deployment device 500 is suitable for a security chip, and may specifically include a firmware deployment instruction receiving module 510 , a firmware signature verification module 520 , a firmware processing module 530 and a firmware deployment module 540 .

[0106] The firmware deployment instruction receiving module 510 can be used to receive a firmware deployment instruction sent by a firmware chip, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed.

[0107] The firmware signature verification module 520 may be configured to obtain a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate.

[0108] The firmware processing module 530 can be used to obtain a firmware encryption key based on a firmware encryption key index after the firmware signature verification passes, and decrypt the encrypted firmware file according to the firmware encryption key to obtain a decrypted firmware file.

[0109] The firmware deployment module 540 can be used to re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

[0110] In an embodiment of the present disclosure, a firmware deployment instruction sent by a firmware chip can be received, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and a first manufacturer identification information corresponding to the firmware to be deployed; after receiving the firmware deployment instruction, the firmware deployment instruction is parsed to obtain the first manufacturer identification information, and then the first firmware manufacturer certificate corresponding to the firmware to be deployed is obtained based on the first manufacturer identification information, and the firmware to be deployed is verified based on the first firmware manufacturer certificate; after the firmware verification passes, the firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain the decrypted firmware file; the decrypted firmware is The firmware file is re-encrypted to obtain a re-encrypted firmware file, and the re-encrypted firmware file is sent to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file. As a result, the firmware can be verified through the first firmware manufacturer certificate, and the firmware file is decrypted after the verification is passed. When the security chip sends the firmware file to the firmware chip, the decrypted firmware file is continuously encrypted and transmitted. That is to say, the firmware verification in the firmware deployment process is performed by introducing a security chip, and the firmware is transmitted in an encrypted manner based on the firmware verification. This ensures the security and reliability of the firmware files and data in the firmware deployment process, thereby improving the security of the firmware deployment.

[0111] In some embodiments of the present disclosure, an authentication session key is pre-installed in the security chip.

[0112] The firmware security deployment device 500 may further include an authentication module.

[0113] The authentication module may be used to receive an authentication session request sent by the firmware chip before receiving the firmware deployment instruction sent by the firmware chip, wherein the authentication session request includes a first encrypted random number obtained by encrypting the first random number by the firmware chip based on the authentication session key;

[0114] The first encrypted random number is decrypted based on the authentication session key to obtain a second random number, and the second random number is returned to the firmware chip so that the firmware chip determines whether the authentication is successful based on the first random number and the second random number, and sends a firmware deployment instruction to the security chip after determining that the authentication is successful.

[0115] In some embodiments of the present disclosure, the firmware deployment instruction also includes a firmware index, which is used to search and manage the firmware to be deployed; the firmware index is determined by a hash value obtained after a firmware management system corresponding to the firmware chip hashes the firmware file corresponding to the firmware to be deployed according to a preset hash algorithm; the firmware encryption key index is determined by the firmware management system based on a preset random function.

[0116] In some embodiments of the present disclosure, the firmware deployment module 540 can be specifically used to re-encrypt the decrypted firmware file based on the target session key to obtain a re-encrypted firmware file, wherein the target session key is generated by the security chip and the firmware chip during the authentication process.

[0117] In some embodiments of the present disclosure, the firmware security deployment device 500 may further include a data destruction module.

[0118] The data destruction module can be used to re-encrypt the decrypted firmware file to obtain the re-encrypted firmware file, send the re-encrypted firmware file to the firmware chip, so that the firmware chip performs the firmware deployment operation based on the re-encrypted firmware file, and then receive the data destruction instruction sent by the firmware chip, the data destruction instruction including the target firmware index corresponding to the data to be destroyed, the second manufacturer identification information corresponding to the data to be destroyed, and the command identification information;

[0119] Acquire a second firmware manufacturer certificate based on the second manufacturer identification information, and perform firmware signature verification based on the second firmware manufacturer certificate;

[0120] After the firmware signature is verified, the data destruction instruction corresponds to the target firmware based on the target firmware index, and the data to be destroyed is determined according to the target firmware;

[0121] A destruction operation is performed on the data to be destroyed based on the command identification information, where the data to be destroyed includes a target firmware file corresponding to the target firmware, a target encryption key, a second firmware manufacturer certificate, and a target authentication session key.

[0122] In some embodiments of the present disclosure, the firmware security deployment device 500 may further include a self-destruction instruction sending module.

[0123] The self-destruction instruction sending module can be used to return the self-destruction instruction to the firmware chip after executing the destruction operation on the data to be destroyed based on the command identification information, so that the firmware chip executes the self-destruction operation of the data to be destroyed based on the self-destruction instruction after receiving the self-destruction instruction.

[0124] It should be noted that Figure 5 The firmware security deployment device 500 shown can execute each step in the above method embodiment and realize each process and effect in the above method embodiment, which will not be described in detail here.

[0125] Figure 6 It is a structural schematic diagram of an electronic device provided by an embodiment of the present disclosure.

[0126] In the disclosed embodiment, Figure 6 The electronic device shown may be a server or a terminal, wherein the terminal specifically includes a mobile phone, a computer or a tablet computer, etc., which is not limited here.

[0127] like Figure 6 As shown, the electronic device may include a processor 610 and a memory 620 storing computer program instructions.

[0128] Specifically, the processor 610 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.

[0129] The memory 620 may include a large capacity memory for information or instructions. By way of example and not limitation, the memory 620 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a tape, or a universal serial bus (USB) drive or a combination of two or more of these. Where appropriate, the memory 620 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 620 may be inside or outside the integrated gateway device. In a particular embodiment, the memory 620 is a non-volatile solid-state memory. In a particular embodiment, the memory 620 includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (Electrically Erasable Programmable ROM, EEPROM), an electrically rewritable ROM (EAROM) or a flash memory, or a combination of two or more of these.

[0130] The processor 610 reads and executes the computer program instructions stored in the memory 620 to perform the steps of the firmware security deployment method provided in the embodiment of the present disclosure.

[0131] In one example, the electronic device may further include a transceiver 630 and a bus 640. Figure 6 As shown, the processor 610, the memory 620 and the transceiver 630 are connected via a bus 640 and communicate with each other.

[0132] The bus 640 includes hardware, software, or both. For example, but not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 640 may include one or more buses.

[0133] The embodiments of the present disclosure also provide a computer-readable storage medium, which may store a computer program. When the computer program is executed by a processor, the processor implements the firmware security deployment method provided by the embodiments of the present disclosure.

[0134] The above-mentioned storage medium may, for example, include a memory 620 of computer program instructions, and the above-mentioned instructions may be executed by the processor 610 of the electronic device to complete the firmware security deployment method provided in the embodiment of the present disclosure. Optionally, the storage medium may be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium may be a ROM, a random access memory (Random Access Memory, RAM), a compact disc read-only memory (Compact DiscROM, CD-ROM), a magnetic tape, a floppy disk, and an optical data semi-virtualized storage device, etc.

[0135] The embodiments of the present disclosure also provide a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, the firmware security deployment method provided by the embodiments of the present disclosure is implemented, and the various processes and effects in the above-mentioned embodiments of the present disclosure can be implemented, which will not be repeated here.

[0136] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A firmware security deployment method, characterized in that: Applied to security chips, including: Receive a firmware deployment instruction sent by the firmware chip, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed; Acquire a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate; After the firmware signature verification passes, a firmware encryption key is obtained based on the firmware encryption key index, and the encrypted firmware file is decrypted according to the firmware encryption key to obtain a decrypted firmware file; The decrypted firmware file is re-encrypted to obtain a re-encrypted firmware file, and the re-encrypted firmware file is sent to the firmware chip, so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

2. The method according to claim 1, characterized in that: The security chip is pre-installed with an authentication session key; Before receiving the firmware deployment instruction sent by the firmware chip, the method further includes: Receiving an authentication session request sent by the firmware chip, wherein the authentication session request includes a first encrypted random number obtained by encrypting the first random number by the firmware chip based on the authentication session key; The first encrypted random number is decrypted based on the authentication session key to obtain a second random number, and the second random number is returned to the firmware chip so that the firmware chip determines whether the authentication is successful based on the first random number and the second random number, and sends the firmware deployment instruction to the security chip after determining that the authentication is successful.

3. The method according to claim 1, characterized in that The firmware deployment instruction also includes a firmware index, which is used to search and manage the firmware to be deployed; the firmware index is determined based on a hash value obtained after the firmware management system corresponding to the firmware chip hashes the firmware file corresponding to the firmware to be deployed according to a preset hash algorithm; the firmware encryption key index is determined by the firmware management system based on a preset random function.

4. The method according to claim 1, characterized in that The re-encrypting the decrypted firmware file to obtain the re-encrypted firmware file includes: The decrypted firmware file is re-encrypted based on a target session key to obtain a re-encrypted firmware file, wherein the target session key is generated by the security chip and the firmware chip during the authentication process.

5. The method according to claim 1, characterized in that After re-encrypting the decrypted firmware file to obtain a re-encrypted firmware file, and sending the re-encrypted firmware file to the firmware chip so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file, the method further includes: receiving a data destruction instruction sent by the firmware chip, wherein the data destruction instruction includes a target firmware index corresponding to the data to be destroyed, second manufacturer identification information corresponding to the data to be destroyed, and command identification information; Acquire a second firmware manufacturer certificate based on the second manufacturer identification information, and perform firmware signature verification based on the second firmware manufacturer certificate; After the firmware signature is verified, the target firmware corresponding to the data destruction instruction is determined based on the target firmware index, and the data to be destroyed is determined according to the target firmware; A destruction operation is performed on the data to be destroyed based on the command identification information, where the data to be destroyed includes a target firmware file corresponding to the target firmware, a target encryption key, a second firmware manufacturer certificate, and a target authentication session key.

6. The method according to claim 5, characterized in that After performing the destruction operation on the to-be-destroyed data based on the command identification information, the method further includes: A self-destruction instruction is returned to the firmware chip, so that after receiving the self-destruction instruction, the firmware chip performs a self-destruction operation on the data to be destroyed based on the self-destruction instruction.

7. A firmware security deployment device, characterized in that: Applicable to security chips, including: A firmware deployment instruction receiving module, used to receive a firmware deployment instruction sent by a firmware chip, wherein the firmware deployment instruction includes an encrypted firmware file corresponding to the firmware to be deployed, a firmware encryption key index, and first manufacturer identification information corresponding to the firmware to be deployed; A firmware signature verification module, used to obtain a first firmware manufacturer certificate corresponding to the firmware to be deployed based on the first manufacturer identification information, and perform firmware signature verification on the firmware to be deployed based on the first firmware manufacturer certificate; A firmware processing module, configured to obtain a firmware encryption key based on the firmware encryption key index after the firmware signature verification passes, and decrypt the encrypted firmware file according to the firmware encryption key to obtain a decrypted firmware file; The firmware deployment module is used to re-encrypt the decrypted firmware file to obtain a re-encrypted firmware file, and send the re-encrypted firmware file to the firmware chip so that the firmware chip performs a firmware deployment operation based on the re-encrypted firmware file.

8. An electronic device, characterized in that: include: processor; A memory for storing executable instructions; The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the firmware security deployment method described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by the processor, the processor implements the firmware security deployment method described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program or instructions, characterized in that: When the computer program or instruction is executed by a processor, the firmware security deployment method according to any one of claims 1 to 6 is implemented.

Images