BACKGROUND

In recent years, the number of types of smart Internet-connectable devices available, such as home appliances (washing machines, refrigerators, dishwashers, stoves/ovens etc.), digital assistant devices, smart sensors and the like has increased rapidly. Such devices may be referred to collectively as the “Internet of Things” or IoT, and applications built using such devices (such as an application that scans the contents of a smart refrigerator and produces a suggested grocery list, or automatically orders groceries) may be referred to as IoT applications. As more and more automation is introduced into the transportation sector (e.g., in the form of semi-autonomous or fully-autonomous vehicles), even cars, trucks and other vehicles are also gradually beginning to rely on, or becoming part of, the Internet of Things.

Often, an individual IoT device may comprise subcomponents produced by one or more semiconductor or chip manufacturers and other vendors, with the final version of the device being packaged and branded by a different business entity and provided to end users. Prior to its deployment for the end user, a given IoT device may have to go through various stages of development and testing, in respective ones of which firmware or software from a different entity (e.g., a semiconductor vendor, contractors involved in assembling the device, the IoT application owner, etc.) may sometimes have to be executed. Depending on the nature of the application for which the IoT device is designed and deployed, a given IoT device may remain in use for a long period, during which it may also have to obtain updates to its firmware or software from one or more sources.

With large numbers of IoT devices potentially distributed across homes, offices, and/or vehicles, enforcing appropriate security policies with respect to administering the IoT devices (e.g., by ensuring that firmware or software is obtained only from trusted sources) is an essential requirement for IoT applications. Satisfying such security requirements in a scalable, low-overhead manner remains a non-trivial technical challenge.

