malicious code, and poor manufacturing and development
practices throughout the SDLC.
5.6.2 Key Findings
– IoT hardware and software manufacturers and suppliers
should adopt a cyber supply chain risk management
framework (ISO28000, NIST).
– Cybersecurity requirements, risk and liability should be
cascaded into the supply chain via contractual
agreements. Organisations wield both contractual and
economic power over suppliers.
– It is important to encourage the use of open frameworks
and provide transparency for supply chain security
information flows.
5.7
PRODUCT LIFECYCLE SUPPORT
Building a device today that will stand up to the everevolving security requirements of the next several years
without any updates or modifications may well be
impossible; in the absence of patching and device
management, devices quickly become outdated from a
security perspective. However, updates typically require
changes in device firmware – this makes it difficult for
regular users to manage these devices. Remote update
capability needs to be designed into the device to allow
security updates, yet, the specialised operating systems
used for embedded devices may not support this by default.
Further, the life cycle for IoT devices varies widely in
duration: industrial devices may be in the field for decades,
consumer products such as smart home appliances or
autonomous vehicles could run for about 10 years, and
wearables may be in use for only a year or two. Clearly,
managing IoT device lifecycles is a tremendous challenge.
56
179 IoT Security: From Design to Life Cycle Management, ABI Research
180 IoT Device Lifecycle – a Generic Model and a use case for Cellular Mobile
Networks, Soos et al, Conference Paper Aug 2018
181 Device Life Cycle Overview, Steven Hsu, Trend Micro Whitepaper, https://
www.trendmicro.com/us/iot-security/content/main/document/IoT%20
Security%20Whitepaper.pdf
5.7.1 Current Landscape and Recent Developments
As ABI Research identifies179, lifecycle device management
offers manufacturers the ability to continue providing value
long after a device has been sold and even re-sold;
however, that management service only has value if it can
be tied securely back to the device. Secure hardware (such
as secure elements and secure MCUs) is at the forefront of
providing this trust. Without this process, any future service
provisioning for the device post-market is vulnerable. The
increased recognition that this opportunity cannot be
realised without trust is a potential driver for industry
adoption of secure hardware.
Soos et al180 present a model for IoT device lifecycle
management that maps the phases of the IoT device
lifecycle to three broad life stages: Beginning of Life (BoL),
Middle of Life (MoL) and End of Life (EoL). Figure 12
depicts the security features and functions that should be
in place during each step of a device’s lifecycle.181 During
initialisation or boot-up, a firmware integrity check and
secure boot process should be used to ensure that
firmware and bootloader software have not been modified
or tampered with. Once initialisation is complete, the
communication between device and device, device and the
Internet, or device and user interface (through mobile apps
or web apps) should be encrypted. Authentication should
use a second factor wherever possible, and default
passwords must be changed. During normal operation,
monitoring, analytics and audit procedures should be in
place. The device should detect abnormal events and
operations and provide a warning to the backend and/or
end user. Secure firmware-over-the-air (FOTA) updates
should themselves be integrity-checked and verified before
installation.
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents