5.9.2 Key Findings
– The diversity of operating systems, cloud solutions and
application development frameworks that populate the
IoT market is large. An in-depth evaluation is required on
the security claims made for each solution.
– Standards are required for software development,
deployment and operation processes to secure the OS,
cloud back-ends, and applications.
– IoT-specific secure software development life cycle
(SDLC) guidelines need to be defined for developers of
IoT applications.
5.10
SECURE COMMUNICATIONS AND
INFRASTRUCTURE
IoT devices transmit information to a back-end for
processing and analytics. Depending on the computational
capabilities of the devices, it may be possible to filter some
of the data before transmission or even to take immediate
action locally without sending any data at all; however, all
IoT systems do, at some point, send data over a network to
a back-end. There are numerous ways to achieve this
connectivity, ranging from direct cellular or satellite
connections to low-power WANs with gateways to reach the
back-end. Security is paramount since IoT devices based on
different technologies and acquired from various suppliers
on the global market communicate via heterogeneous
network interfaces in an open network that is untrustworthy
and potentially hostile.
5.10.1 Current Landscape and Recent Developments
When a device connects to the back-end, a gateway or other
devices, it must authenticate and establish trust. Once
trust is established, devices, users and services can
securely communicate, interact and transact information.
This challenge encompasses all elements that route and
transport endpoint data traffic securely over the infra
structure, whether control, management or actual data
traffic.
72
239 https://www.globalsign.com/en-sg/blog/iot-vs-traditional-pki-deployments/
240 https://www.sics.se/projects/certificate-enrollment-in-billions-of-things
Authentication and Authorisation
Authentication in IoT networks should establish mutual
trust between devices, users, gateways, back-ends,
networks, and services. Classically, the authentication
process relies on the authenticating entity demonstrating
knowledge ("something you know"), possession
("something you have"), and/or inherent/behavioural
("something you are") factors, with multiple factors often
recommended for stronger authentication. While these
factors are applicable to users of IoT devices (e.g. to log in
to a management console), the "things" themselves are
essentially restricted to possession factors relying on a
shared secret or asymmetric key. As discussed in previous
chapters, the provisioning of a trusted identity is normally
done at the time of manufacturing or via key injection.
Public-key infrastructure (PKI) has been used to
authenticate machines and servers for decades, and offers
an established open standard for interoperability. However,
PKI needs to evolve in order to support the scale and hetero
geneity inherent in IoT usecases.239 Specifically, lightweight
certificate enrollment procedures should prove useful; the
Swedish CEBOT (Certificate Enrollment in Billions of Things)
project addresses how lightweight enrollment can be
achieved.240 Additionally, certificate validity periods and
future-proof algorithms need to be considered. If implemented
carefully using the device's root of trust, PKI-based
identities can provide a basis for strong authentication.
The authorisation layer controls the extent of access
provided to a device or, more generally, a process. This
layer builds upon the core authentication layer by leveraging
the identity information of an entity to determine what
actions it is allowed to perform. The principle of least
privilege dictates that we should only allow the bare
minimum of access to an entity, such as a device or
process, to allow it to perform the functionality needed of
it. With authentication and authorisation in place, a trust
relationship is established between IoT devices to exchange
appropriate information.
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents