BEGINNING OF LIFE MIDDLE OF LIFE Design Compliance Risk Assessment Development – Secure software development – Trusted supply chain – Secure production and assembly Configuration/ Provisioning Testing END OF LIFE Retirement – Recycle/scrap Deprovisioning – Disconnect – Delete/wipe Power-Up – Device boots up and reaches operational state – Firmware integrity check – Secure boot Operation – Device performs its intended purpose continually – Authenti­ cation and authorisation – Encrypted communi­ cation – Monitoring Update – Device receives and installs patch/ update, possibly reinitializing during the process – Secure firmwareover-the-air updates Figure 12: Security Considerations Through the Device Lifecycle 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. 182 Alliance for Internet of Things Innovation - https://aioti.eu 183 https://www.broadband-forum.org/standards-and-software/technicalspecifications/tr-069-files-tools 184 http://openmobilealliance.org/iot/lightweight-m2m-lwm2m 185 ISO Vulnerability Disclosure, https://www.iso.org/standard/72311.html 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 57

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents