The site provides interesting info, but the graphs are more eye candy than helpful. The real interesting stuff is revealed in two text reports.
For what it's worth, I wonder if the Windows version will ever emerge, because this software does a lot of "hacker-like" things to get the data, and it may be tricky to get it to run under Windows without triggering firewalls and other security bells and whistles.
The arp spoofing it uses effectively makes it a man-in-the-middle (probably a proxy) between your IoT devices and their legitimate end-points - like WireShark. Because it is pushing traffic to the cloud like the IoT devices it's monitoring, it becomes a question of who's watching the watcher? I'm a bit uncomfortable leaving this running on my network. It's all in how much you trust Princeton.edu (my guess is this is a graduate student project, but what happens to the data later?)
I don't think I'm going to run this long-term, but I'll give it a few days before shutting it down. I might light it up again if I add new IoT devices.
A few things I've learned already:
- Amazon Echos, Harmony Hubs, and a few other common IoT devices don't encrypt their traffic. IoT-Inspector says it doesn't actually monitor the content of the packets (just the routing), but you're effectively installing a product that could see authentication and API keys for IoT platforms. If anything, you want to be sure to get the IoT-Inspector code from a reliable source and not a 3rd party site where it could be modified for malicious purposes.
- Roku devices hit a lot of advertising sites. If you're planning on setting up a Raspberry Pi and Debian to run IoT-Inspector, set up another and install Pi-Hole then set your DNS for every device in your home to it, including the Roku devices. The Pi-Hole sends all DNS requests for ad sites into a black hole (hence the name) and strips them from your web browsing, too.
- If you have an IoT device that can run locally with HS3 and you've never setup (or disabled) its cloud-communications capabilities thinking that will keep its traffic within the confines of your LAN, you're probably fooling yourself.
Leave a comment: