Remote Access to IoT Devices: Common Needs & Approaches
summary
Remote access in IoT must work over outbound-only connections, use TLS with per-device keys, and provide audit logs, access approval and role-based controls plus device-side restrictions. Practical options: WireGuard/OpenVPN give full SSH/port-forwarding but add a second encrypted tunnel and require an exposed SSH daemon; reverse SSH and raw sockets scale poorly. A working implementation uses WebSocket (device keeps an HTTPS-upgraded connection, server wires sessions via a message queue called nuts), reuses OTA creds, supports terminal, file transfer and port-forwarding, and shows very low bandwidth.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:38Risks
- 2:18Audit logs
- 2:43Customer requests
- 3:18Rolebased access control
- 4:30Summary
- 5:20Outbound connections
- 5:52Terminal access
- 6:36VPN
- 7:48Reverse SSH
- 9:46Raw Socket
- 10:52Web Socket
- 12:50Offtheshelf solutions
- 13:47MQTT
- 14:47Other Use Cases
- 15:10Off the Shelf Solutions
- 15:30VPN SSH
- 17:14WebSocket
- 18:31WebSocket Terminal
- 21:44Offtheshelf
- 22:46Questions
related talks
11mSecuring IoT Integrations with Third-Party Services
29mSecuring IoT/OT Against Modern Threats
57mSecuring the last mile of IoT solutions
01h 03mConnect remotely like a pro! Hack VPNs, avoid firewalls, connect even when your machine is down
32mCommon Attacks on IoT Devices
38mThe 'S' in IoT stands for Security
11mRethinking Remote Access in a Remote First World
17mIoT Archaeology: Dig Security Lessons