have a microcontroller rather than a full-fledged
microprocessor, and speeds in MHz rather than GHz.
Additionally, the low cost of these devices means razor-thin
margins for the supplier and less to spend on security.
Nevertheless, security should be part of an IoT device from
an early design stage and is something that should never
be passed over in the interest of decreasing manufacturing
costs or time to market.
Once designed, IoT devices are mass-produced. There
may be thousands to millions of similar IoT devices. With
consideration for the requirements and capabilities of
these devices, the design should be fundamentally secure.
Cryptographic identifiers are a common approach, but
these are vulnerable because many devices manage secret
keys with software, which if breached can expose the key.
This leads to the challenge (as identified by ENISA 187 and
MITRE188) of establishing a chain of trust based on a root of
trust embedded in the device.
5.8.1 Current Landscape and Recent Developments
Recent developments focus on the device elements that
are important from a security viewpoint: root of trust (which
can physically reside in the processor or storage, or on a
separate chip), firmware, and storage.
Root of Trust
A root of trust (RoT) is a hardware or software component
that is inherently trusted189 due to its immutability. A RoT
must be secure by design, should be small and protected
and ideally implemented in hardware or protected by
hardware. RoTs are trusted to perform or support one or
more security-critical functions, e.g. verify software, protect
cryptographic keys, and perform device authentication190.
In fact, a RoT anchors several of the security functionalities
that we discuss below and in subsequent sections. The
main uses of the RoT include the following.
– Identity: The RoT can securely hold a device identifier that
can be queried by communicating entities.
– Authentication: Secure communication is available after
successfully completing an authentication and key
exchange protocol, typically using an ephemeral
symmetric session key for encryption and an HMAC key
for authentication. These keys can be generated and
stored in the RoT, keeping them protected from on-chip
attacks.
– Data Encryption: Encryption can protect data stored
locally on the device as well as data transmitted over
networks. The RoT can store encryption keys. Only
indirect access to these keys is allowed and managed by
permissions and policies on the application layer.
– Secure Boot: Validation of the code and/or data on the
device following power-up, based on trusted material
stored within the RoT. This prevents the execution of
unauthorised code and the exposure of embedded boot
code and software IP.
Identity
Authentication
ROOT OF TRUST
Secure Boot
Figure 15: Root of Trust Functionalities
60
187
188
189
190
ENISA ‘Baseline Security Recommendations for IoT’, November 2017
https://www.mitre.org/research/mitre-challenge/mitre-challenge-iot
https://blog.nxp.com/security/getting-to-the-root-of-trust
https://www.synopsys.com/designware-ip/technical-bulletin/
understanding-hardware-roots-of-trust-2017q4.html
Data Encryption
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents