Join our Newsletter — 33% off our NHI Course

Are IoT device identities secure across the full lifecycle?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Lifecycle trust is the hard part of IoT device security, with DigiCert reporting that identity, encryption, integrity, and update assurance have to follow devices from manufacturing through retirement. Device identity management has to keep authentication, renewal, and revocation working as fleets move through provisioning, deployment, and updates.

Editorial analysis by NHI Mgmt Group, based on content published by DigiCert: “This IoT Day, Don’t Forget to Discuss Device Security”.

Key questions

Q: Why do IoT devices need more than two-factor authentication?

A: Two-factor authentication helps with access events, but IoT devices need cryptographic identity that survives manufacturing, updates, and cloud connectivity.

Q: What breaks when IoT identity is handled only at provisioning?

A: Provisioning-only identity leaves later stages ungoverned, so a device may be genuine at first use but unauthorised, stale, or unverifiable after deployment.

Q: How should security teams implement PKI for IoT devices without creating certificate sprawl and operational drag?

A: Security teams should treat PKI for IoT as a lifecycle programme, not just a certificate issuance task.

Practitioner guidance

  • Build certificate-backed device identity into product design Define how each device class will receive a unique identity, how that identity will be validated, and how it will be re-established after replacement or recovery.
  • Align provisioning with manufacturing reality Map certificate issuance to the actual production, supply-chain, or field-provisioning stage used for each device family, including offline or air-gapped environments.
  • Require signed and encrypted device updates Make firmware and OTA update workflows verify authenticity before installation and bind decryption to the intended device identity.

Bottom line: IoT device security weakens when authentication is separated from the rest of the device lifecycle, because trust has to survive manufacturing, deployment, updates, and retirement.

Glossary terms: Device Identity, Certificate Lifecycle Management, Secure Boot, Firmware Signing

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 4 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

PKI is the only scalable way to make IoT identity durable across the device lifecycle. IoT devices are not authenticated once and then forgotten. They move through design, production, provisioning, field operation, update cycles, and eventual retirement, which means their identity has to survive every phase. The security mistake is treating trust as a setup event rather than a lifecycle state. Practitioners should govern device identity as an ongoing control domain, not a one-time certificate issue.

A question worth separating out:

Q: What is the difference between secure boot and firmware signing in IoT devices?

A: Firmware signing protects the authenticity of the update package before it is installed, while secure boot checks trust at startup so the device only runs approved code. Together they cover two different moments in the lifecycle: delivery and execution. Both are needed because a trusted update is not enough if the device later boots untrusted software.

👉 Read our full editorial: IoT device security depends on PKI across the device lifecycle



   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.