Trends in Security Information
The HSD Trendmonitor is designed to provide access to relevant content on various subjects in the safety and security domain, to identify relevant developments and to connect knowledge and organisations. The safety and security domain encompasses a vast number of subjects. Four relevant taxonomies (type of threat or opportunity, victim, source of threat and domain of application) have been constructed in order to visualize all of these subjects. The taxonomies and related category descriptions have been carefully composed according to other taxonomies, European and international standards and our own expertise.
In order to identify safety and security related trends, relevant reports and HSD news articles are continuously scanned, analysed and classified by hand according to the four taxonomies. This results in a wide array of observations, which we call ‘Trend Snippets’. Multiple Trend Snippets combined can provide insights into safety and security trends. The size of the circles shows the relative weight of the topic, the filters can be used to further select the most relevant content for you. If you have an addition, question or remark, drop us a line at info@securitydelta.nl.
visible on larger screens only
Please expand your browser window.
Or enjoy this interactive application on your desktop or laptop.
IoT security challenge: product lifecycle support
and ISO/IEC 30111. The manufacturer should bear responsibility for an IoT device throughout its product lifecycle, including a responsibility to manage suppliers. Existing device lifecycle management protocols include OMA LWM2M. Cloud-based IoT platforms offer comprehensive, albeit unstandardised, device management functionality.
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.
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.

According to AIOTI182, device management is defined as software or firmware updates as well as configuration or fault and performance management. Device management can be performed using existing protocols e.g. BBF TR-069183 or OMA LWM2M184.
Vulnerability Disclosure
History shows that vulnerabilities are invariably found after a product is deployed – and often exploited in “zero-day” attacks. It is vital to be able to detect unforeseen vulnerabilities, anomalies and threats in live IoT deployments, and to respond quickly, recover and remediate. A strategy to deal with discovered threats and vulnerabilities includes a Coordinated Vulnerability Disclosure (CVD) program that balances security with the interests of manufacturers and stakeholders, as well as a clear understanding of liability. CVD is standardised by the ISO185 under ISO/IEC 29147 and ISO/IEC 30111. While CVD is currently used mainly by the IT industry, it is imperative for open, standardised vulnerability management to be implemented across all sectors where security is becoming a critical component of safety.
Platform-Based Device Lifecycle Management
The growth of IoT has led to the emergence of cloud-based IoT platforms from many cloud service providers (CSPs) such as Amazon’s AWS, Microsoft Azure and Google Cloud. Most of these offer comprehensive device management functions across the device lifecycle, e.g. device registration/ enrolment, identity management, provisioning, permissions, monitoring and troubleshooting, status queries, and overthe-air (OTA) firmware updates. Platforms allow IoT users scale device fleets and may help to reduce the cost and effort of managing large and diverse IoT device deployments. Microsoft Azure, in particular, has comprehensive device management functionality built into its IoT Hub.186 This includes the use of a “device twin” for each connected physical device that stores device metadata and essentially acts a proxy for the actual device.

5.7.2 Key Findings
– Keeping software up to date and allowing for patches and updates is critical for a secure IoT device. Updates should be delivered and deployed using a secure and verifiable methodology.
– Device manufacturers should adopt a secure software development lifecycle, with a documented vulnerability management process in accordance with ISO/IEC 29147 and ISO/IEC 30111.
– The manufacturer should bear responsibility for an IoT device throughout its product lifecycle, including a responsibility to manage suppliers.
– Existing device lifecycle management protocols include OMA LWM2M. Cloud-based IoT platforms offer comprehensive, albeit unstandardised, device management functionality.