Implementing a third layer of security (do we need it?)
summary
Argues for a concrete third layer: device-to-server end-to-end encryption using public/private key exchange, with private keys kept in a hardware ATECC508 secure element (newer 8x608 keeps derived secret inside). Shows an Explorer board with Bluetooth provisioning to load keys securely, explains tradeoffs (LoRa 51‑byte payload limit, 63% of experts worry about physical endpoints), reports the prototype works and chips cost less than one euro.
AI-written summary · about
chapters (11)
- 0:00Start
- 5:36Security Threats
- 6:10LoRa security model
- 7:22LoRaWAN Security
- 8:07Symmetric Keys
- 10:24LoRa encryption in practise
- 12:02Physically Unsecure Endpoints
- 12:54A Solution
- 18:37Diffie-hellman key exchange
- 21:04Now what's the difference?
- 22:42Secure element
related talks
43mShhh - Stop Sharing Secrets, a Secure Mindset for Embedded Development
21mApplications and practicality for device security
29mEnabling a secure IoT from design to deployment
45mBuilding a Secure IoT Device
22mSecure Element: Provisioning made EASY
40mKeeping secrets in your opponent's hands
35mIoT Cornerstones of Security
21mEnhanced Security for LoRaWAN devices