How we got rid of passwords in IoT
summary
A password is replaced by certificate-based identity: a factory configurator utility runs in the factory, injects root CA certificates (bootstrap and LwM2M) plus a firmware authority CA and either creates or relays device keypairs, then uploads the FCU root cert to Pelion so the cloud trusts factory-issued certs. Devices use mutual TLS to bootstrap, receive a globally unique device ID and a LwM2M client certificate, and thereafter authenticate to the Pelion LwM2M server. The flow supports on-device key generation and OTA updates via the manifest tool.
AI-written summary · about
chapters (8)
- 0:00Introduction to IoT security
- 2:05Mutual TLS authentication
- 4:37System architecture overview
- 7:15Establishing trust authorities
- 10:24Factory line setup
- 13:48Commissioning firmware updates
- 15:17Device injection process
- 19:31In-field registration flow
related talks
19mProviding appropriate trust for IoT devices
18mBeyond the Default Password: Building Trustworthy IoT Products
39mApplied IoT security for healthcare and industrial
43mDevice Security in IoT
19mSimplifying device deployment
40mTrusted Internet of Things Device Onboarding and Lifecycle Management
45mBuilding a Secure IoT Device
29mEnabling a secure IoT from design to deployment
