Security on the Internet of Things is still more of a nice idea than an implementation. The category is still so nascent, with so many players trying to stake a claim, that there hasn’t really been much of a push to standardize on much. While market forces will probably sort this out in the long run, it’s a huge problem for consumers who have bought in early. While these are still early adopters, there’s a difference between a product not working or not being supported because it’s early days, and a product leaving a gaping hole in your privacy. It’s one thing to be an early adopter on MP3 players and get stuck with a bulky product or DRM. It’s another when you buy a IoT device with a camera that anyone with the IP address can view.
That’s why I’m heartened by Google’s promotion of Project Brillo into the more official but awkwardly named “Android Things”. Lazy naming aside, it should provide a reasonably secure, updatable and transparent network communication fabric for IoT device. The problem still is that it currently only supports platform boards, Intel Edison, NXP Pico, and the Raspberry Pi 3. Still, a player with Google’s clout goes a long way to pushing a standard.
Ars Technica comments:
- TELoIP and the SD-WAN Cook-off - April 21, 2017
- The Future of On-Prem in a Cloud World - April 21, 2017
- Rook is the New Flocker? - April 21, 2017
- Virtualization and Containers: All of This Has Happened Before - April 11, 2017
- TCP Terminators: An Expert Analysis - April 11, 2017
- Qumulo Secures Round C Prime Funding – My Conversation with Bill Richter - April 11, 2017
- CapEx on Cloud up 22% in 2016 - April 10, 2017
- IPv6 Hits the Weekend, Network Engineers are Programmers, and Epoch Rollover Considerations in Gestalt Networking News 17.5 - April 7, 2017
- Remembering the IBM 1403: Hammer Time - April 5, 2017
- AWS Coming to Sweden in 2018 - April 4, 2017