Secure firmware integrity monitoring using rest over IPMI interface

• US 10,489,142 B1
• Filed: 02/09/2018
• Issued: 11/26/2019
• Est. Priority Date: 02/09/2018
• Status: Active Grant

• Current Assignee: American Megatrends International, LLC
• Original Assignee: American Megatrends International, LLC
• Inventors: Podgorsky, Oleksandr, Kulchytskyy, Igor
• Primary Examiner(s): St Leger, Geoffrey R
• Application Number:
  US15/893,561
• Time in Patent Office: 655 Days
• Field of Search: 717168-178
• CPC Class Codes: G06F 13/36 for access to common bus or bus system
• CPC Class Codes: G06F 21/572 Secure firmware programming, e.g. of basic input output system [BIOS]
• CPC Class Codes: G06F 21/575 Secure boot
• CPC Class Codes: G06F 2221/034 Test or assess a computer or a system
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

Technologies are described herein for a representational state transfer (“REST” or “RESTful”) over Intelligent Platform Management Interface (“IPMI”) interface for firmware to BMC communication and applications thereof. These applications include, but are not limited to, remote firmware configuration, firmware updates, peripheral device firmware updates, provision of management information such as system inventory data, cloning and batch migration of firmware configuration settings, and firmware integrity monitoring. This functionality can be provided in a way that enables communication between BMCs and firmware to utilize modern manageability interfaces while maintaining backward compatibility with previous IPMI implementations.

Claims

1. A non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by a computer, cause the computer to:

compute, by way of a first portion of a firmware executing on the computer, a current hash value for a second portion of the firmware;

transmit the current hash value for the second portion of the firmware from the first portion of the firmware to a baseboard management controller (BMC);

determine, by way of the BMC, whether the current hash value for the second portion of the firmware is the same as a reference hash value for the firmware;

transmit a first instruction from the BMC to the first portion of the firmware over a representational state transfer (REST) over intelligent platform management interface (IPMI) responsive to determining that the current hash value for the second portion of the firmware is the same as the reference hash value for the firmware;

receive the first instruction at the first portion of the firmware; and

execute the second portion of the firmware responsive to receiving the first instruction.

2. The non-transitory computer-readable storage medium of claim 1, having further computer-executable instructions stored thereupon to:

transmit a second instruction from the BMC to the first portion of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware;

receive the second instruction at the first portion of the firmware; and

prevent execution of the second portion of the firmware on the computer responsive to receiving the second instruction.

3. The non-transitory computer-readable storage medium of claim 1, wherein the BMC is configured to store the current hash value in a secure location.

4. The non-transitory computer-readable storage medium of claim 1, wherein the BMC is further configured to initiate an update of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware.

5. The non-transitory computer-readable storage medium of claim 1, wherein the first portion of the firmware comprises a portion of the firmware that cannot be modified.

6. The non-transitory computer-readable storage medium of claim 1, wherein the second portion of the firmware comprises a remainder of the firmware other than the first portion.

7. The non-transitory computer-readable storage medium of claim 1, wherein the reference hash value for the firmware is computed at a build time of the firmware and the current hash value for the firmware is computed at a boot time of the computer.

8. A computer-implemented method for verifying the integrity of a firmware of a computing system, comprising:

computing, by way of a first portion of a firmware executing on a computer, a current hash value for a second portion of the firmware;

transmitting the current hash value for the second portion of the firmware from the first portion of the firmware to a baseboard management controller (BMC);

determining, by way of the BMC, whether the current hash value for the second portion of the firmware is the same as a reference hash value for the firmware;

transmitting a first instruction from the BMC to the first portion of the firmware over a REST over IPMI interface responsive to determining that the current hash value for the second portion of the firmware is the same as the reference hash value for the firmware;

receiving the first instruction at the first portion of the firmware; and

executing the second portion of the firmware responsive to receiving the first instruction.

9. The computer-implemented method of claim 8, further comprising:

transmitting a second instruction from the BMC to the first portion of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware;

receiving the second instruction at the first portion of the firmware; and

preventing execution of the second portion of the firmware on the computer responsive to receiving the second instruction.

10. The computer-implemented method of claim 8, wherein the BMC is configured to store the current hash value in a secure location.

11. The computer-implemented method of claim 8, wherein the BMC is further configured to initiate an update of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware.

12. The computer-implemented method of claim 8, wherein the first portion of the firmware comprises a portion of the firmware that cannot be modified.

13. The computer-implemented method of claim 8, wherein the second portion of the firmware comprises a remainder of the firmware other than the first portion.

14. The computer-implemented method of claim 8, wherein the reference hash value for the firmware is computed at a build time of the firmware and the current hash value for the firmware is computed at a boot time of the computer.

15. A computing system, comprising:

one or more processors; and

at least one non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by the one or more processors, cause the system to;

compute, by way of a first portion of a firmware executing on a computer, a current hash value for a second portion of the firmware;

transmit the current hash value for the second portion of the firmware from the first portion of the firmware to a baseboard management controller (BMC);

determine, by way of the BMC, whether the current hash value for the second portion of the firmware is the same as a reference hash value for the firmware;

transmit a first instruction from the BMC to the first portion of the firmware over a REST over IPMI interface responsive to determining that the current hash value for the second portion of the firmware is the same as the reference hash value for the firmware;

receive the first instruction at the first portion of the firmware; and

execute the second portion of the firmware responsive to receiving the first instruction.

16. The computing system of claim 15, wherein the at least one non-transitory computer-readable storage medium has further computer-executable instructions stored thereupon to:

transmit a second instruction from the BMC to the first portion of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware;

receive the second instruction at the first portion of the firmware; and

prevent execution of the second portion of the firmware on the computer responsive to receiving the second instruction.

17. The computing system of claim 15, wherein the BMC is configured to store the current hash value in a secure location.

18. The computing system of claim 15, wherein the BMC is further configured to initiate an update of the firmware responsive to determining that the current hash value for the second portion of the firmware is not the same as the reference hash value for the firmware.

19. The computing system of claim 15, wherein the first portion of the firmware comprises a portion of the firmware that cannot be modified.

20. The computing system of claim 15, wherein the second portion of the firmware comprises a remainder of the firmware other than the first portion.