Securing the Internet of Things
We can’t trust manufactures to build secure connected devices and so routers need to be updated to solve this problem once per network.
The distributed denial of service (DDOS) attack on Friday, October 21 was apparently caused by dodgy webcams. But next time it will be Nest or Alexa or Hue - not picking on Google, Amazon or Philips specifically here, those just happen to be the IOT devices currently plugged into my home network. My washing machine and drier would be as well but fortunately LG’s dismal app has saved me from myself by not working for toffee. Oh, I have some DropCams too. And my car is connected. The next attack will probably just come from me.
My fix: update routers to sandbox these devices. A Nest thermostat can only talk to nest.com. If it wants to DDOS Reddit too bad, no connection allowed no matter how badly the device is compromised.
When a new device is connected the router looks it up (MAC address registry?) and then puts it in the appropriate sandbox.
If Nest needs to connect to weather.gov to check the forecast then Google would need to proxy this via nest.com. If the device goes bad it’s only got one domain to attack (so there’s a pretty good incentive for the manufacturer to make sure it doesn’t).
The only downside is new routers or new router firmware. Given the current state of IOT I’d buy one.
As usual if any of my billionaire investor readers are interested get in touch.
Related Posts
- Routers to defend against rogue IoT devices
- Air Gap
- Leaving the Nest
- Overvalidation
- Chromecast won't connect to wifi - finally found the fix
(Published to the Fediverse as: Securing the Internet of Things #etc #iot #google #philips #lg #amazon A proposal to secure the internet of things via sandboxing to manufacturer owned URL by MAC address. No more DDOS from toasters. )
Add Comment
All comments are moderated. Your email address is used to display a Gravatar and optionally for notification of new comments and to sign up for the newsletter.