IoT TLS: Why It's Hard
summary
Explains why TLS on constrained IoT devices with tens of kilobytes of RAM and ~100 KB flash is barely possible: certificate stores are hundreds of kilobytes, common TLS needs a 16KB record buffer, RSA and entropy generation are CPU- and time‑heavy, and poor RNGs break security. Describes using embedded TLS and putting a socket API with TLS underneath in Zephyr (merged for TCP; DTLS and full MQTT/JWT integration are pending), and warns hardware offloads often skip root verification.
AI-written summary · about
chapters (7)
- 0:00IoT TLS challenges
- 4:00IoT and security risks
- 10:57TLS handshake in practice
- 17:23TLS hard for IoT devices
- 23:25TLS API pitfalls
- 28:26Zephyr simplifies TLS
- 30:17Q&A
related talks
35mIoT Cornerstones of Security
28mSecuring the IoT: High-speed cryptography and Edward Snowden
20mPost-Quantum Cryptography for the Internet of Things
18mIoT Security's Toughest Challenges: Root of Trust, TEEs, & Firmware Updates
57mSecuring the last mile of IoT solutions
31mSecuring the Internet of Things
14mLoRaTLS: Approaching BSI compliances
50mSecuring IoT Data with Pervasive Encryption