Why the Internet of Things is Failing

Let’s take a second to step back into reality, suspending the influence of the Silicon Valley's hype machine, and taking the time to analyze the current situation of the Internet of Things (IoT). If I had to give Silicon Valley a grade for how well they have influenced consumer's awareness of the IoT, it would be an “F,” and I don't think I would be the only person to deliver that evaluation. Silicon Valley has failed to maintain the excitement around the "The Internet of Things," with consumers understanding very little about how these connected devices will benefit them, and more importantly, not really caring. Before you can convince the world that a network of connected devices is the future of productivity, you first have to convince them of a number of smaller, more tangible points.

Networking Woes

If you're [Silicon Valley] going to take on the task of connecting every device known to man, I think it would be a good idea to start with trying to make devices easier to connect to a network. My background is littered with networking horror stories from a variety of consumer electronics retailers, and right now, consumer's frustration level with basic networking could potentially be the single greatest hurdle to a world of connected devices. The Networking equipment category is consistently one of the most frustrating for retailers, with return rates always ranking among the highest in store, and it poses a customer service nightmare for every party involved.

You see, networking is one of the only categories in retail that enlist a number of third parties in an effort to safely and securely create a home network. A best-case scenario limits the interactions to three entities: the retailer who sold the connected device, the internet service provider (ISP), and the manufacturer of the networking equipment. Any business transactions that involve more than two parties open themselves up to a plethora of problems (I'm looking at you Uber), and in this case, three is definitely a crowd.

To alleviate this problem, manufacturers of networking equipment have decided the easiest thing to do is engineer themselves across the finish line (a typical response from geeks). Innovation after innovation has been applied to networking equipment, starting with connection wizards, peeking with Wi-Fi Protected Setup (WPS), and sadly ending with auto-connecting mesh routers. Personally, I probably would have given up when consumers weren't able to figure out one-touch connections with WPS, but the industry keeps trudging along.

Security Woes

When customers have been able to successfully connect the latest generation of connected devices, things haven't always gone as planned, as demonstrated by a string of highly publicized security breaches dominating the headlines. In October of 2016, one of the largest internet outages ever witnessed was caused by hacked IoT devices. 2017 was ushered in by the release of Brickerbot, an attack specifically designed to permanently disable poorly designed IoT devices, a process known as "bricking." All of these instances can be linked back to the one specific goal - maintaining the bottom line.

Manufacturing IoT devices happen in the manner as any other product, which means manufacturers adhere to the same priorities, with the goal being to manufacture these products at the lowest possible price point. This translates into lower memory capacity, less built-in security, and minimal investment devoted to human IT resources. The end result has been a large quantity of these devices running in their default configuration when they are shipped to customers, and customers not having the knowledge, or patience, to change their configurations.


Shell Interface
Shell Interface
So what's wrong with the default configuration? To put this into layman's terms, it's the equivalent of breaking the first rule of Fight Club. Everyone knows the rule, it should be easy to follow, but it continues to be broken. The first rule of internet security is to never leave your device's username and password on the default settings, as doing this leaves the device accessible to anyone who has ever read the manual for that particular device [you should be thinking about your own security right now]. 


Talking Solutions

I'm not here to bitch-n-moan about the world without offering up some solutions. As a former corporate trainer in the consumer electronics space, I understand the importance of consumer education and how much better off a situation can become by applying a bit of knowledge to it. RTR Digital offers a Networking Basics course at our learning site, RTR Learning, but if you're not going to enroll, we'll still provide some basic tips.


  1. Change the Default Settings - Every device is shipped with a default username and password (usually on a sticker on the device) that is designed as a way for users to access the setup menu, configure the device, and then change the password so no one else can access the administrator settings. Never leave the username or password set to "admin" or "password1234".
  2. Name Your Wireless Network Something Abstract - When configuring your wireless network, don't include any personally identifiable information (e.g. name, street number, house color). If someone is determined to access a network, physical proximity is the key, and associating the network work with its location is giving up way too much information.
  3. Use the Guest Network Feature - If your networking equipment is equipped with the guest network feature – use it. The guest network feature will enable you to hand out the password to your wireless network without exposing your personal information in the process. Devices on the guest network are given internet access but are in a separate part of the network than devices that are connected to the primary network.
  4. Create Unique Passwords - When creating passwords, every device should have a different password, which means you can't use your kids' birthdays every time. It may seem like a hassle, but to make it easier, you should come up with a system that enables you to remember them. You can try something like...the first three letters of the manufactures name...followed by the month and year the device was purchased. 
Ultimately, it will be up to retails, manufacturers, and consumers to take control of their own responsibilities when dealing with connected devices. There are three parties involved with future of the IoT and all three of them will have to decide how bad they want the world that was promised to them. Feel free to leave comments or questions on this post and we'll be sure to respond.

Comments

  1. This article clearly explains that IOT initiatives should not be compromised by lack of software development skills and security woes. Thus, the need for proper IOT training arises. To improve awareness educational institutions can also provide IOT projects for engineering students , which can create better future engineers who can understand the working of the internet of things.

    ReplyDelete
  2. We are fully committed to the IoT, but we believe the IoT must be secured for its promise to be realized. . We have pumped in all that we have learnt into this
    iot training

    ReplyDelete
  3. Well analyzed situation of IoT Applications & Software Development. IOT can make business much more easy. It is a very strong software.

    ReplyDelete

Post a Comment