Secure boot assist for devices, and related systems, methods and devices
AssigneeMicrochip Technology Incorporated
InventorsKerry Maletsky, David Paul Arnold, Nicolas Auguste Constant Schieli, Bryan Hunt
Life of this patent
Estimating the term…
Loading patent…
AssigneeMicrochip Technology Incorporated
InventorsKerry Maletsky, David Paul Arnold, Nicolas Auguste Constant Schieli, Bryan Hunt
Estimating the term…
Systems, methods, and devices of the disclosure relate, generally, to secure boot assist for devices. In one or more embodiments, a first device includes firmware that needs to be verified as secure as part of a secure boot process, and a second device assists the first device to secure the secure boot process. In some embodiments the second device verifies security of the firmware responsive to security data provided by the first device, or verifies security of a program provided by the first device, the program for verifying security of the firmware. In some embodiments the second device provides a program for verifying security of the firmware to the first device.
A method, the method comprising:
A secure boot-assisted system, comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates…:…
User authentication: involving the use of external additional devices, e.g. dongles or smart cards
Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates…:…
Arrangements for executing specific programs: bootstrapping
About 13 years 1 month of term left · ends 7 Dec 2039 (estimated)
The present disclosure relates, generally, to ensuring firmware to be executed at a target device is secure; and more specifically, some embodiments relate, generally, to using a secure device external to a target device to ensure that a program for verifying firmware at the target device is secure; and more specifically still, some embodiments relate, generally, to using a secure device external to a target device to control at least some of a secure boot process at the target device to ensure firmware to be executed at the target device is secure.
Sometimes the firmware that runs devices such as microcontroller units (MCUs) needs to be updated “in-field” (i.e., after the device has left the factory), for example, because a manufacturer releases a new version of firmware to correct bugs or add functionality. Many devices use Flash memory or other non-volatile memory to store firmware because Flash memory may be modified by firmware itself.
While this disclosure concludes with claims particularly pointing out and distinctly claiming specific embodiments, various features and advantages of embodiments within the scope of this disclosure may be more readily ascertained from the following description when read in conjunction with the accompanying drawings, in which:
FIG. 1 is a simplified block diagram of a computing system in accordance with one or more embodiments of the disclosure;
FIG. 2 is a simplified block diagram of a system for ensuring authenticity of an MCU application, in accordance with one or more embodiments of the disclosure;
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which are shown, by way of illustration, specific examples of embodiments in which the present disclosure may be practiced. These embodiments are described in sufficient detail to enable a person of ordinary skill in the art to practice the present disclosure. However, other embodiments may be utilized, and structural, material, and process changes may be made without departing from the scope of the disclosure.
The illustrations presented herein are not meant to be actual views of any particular method, system, device, or structure, but are merely idealized representations that are employed to describe the embodiments of the present disclosure. The drawings presented herein are not necessarily drawn to scale. Similar structures or components in the various drawings may retain the same or similar numbering for the convenience of the reader; however, the similarity in numbering does not mean that the structures or components are necessarily identical in size, composition, configuration, or any other property.
It will be readily understood that the components of the embodiments as generally described herein and illustrated in the drawing could be arranged and designed in a wide variety of different configurations. Thus, the following description of various embodiments is not intended to limit the scope of the present disclosure, but is merely representative of various embodiments.