I posted an article recently on ServiceTechMag.com. Please take a look and share!
Since the advent of the smartphone—brief as its introduction was in 1992 with IBM’s Simon; complete in its ubiquity with Apple’s 2007 iPhone launch—computers have taken over as the operation centers of our most commonly used devices. Today, the most current cars, refrigerators, thermostats, washers, dryers, ovens, televisions and more don’t rely on wiring, but rather depend on programming to operate. Internet of Things (IoT) devices have Application Programming Interfaces (APIs), which enable remote management and connectivity. Through these APIs, they can interoperate. The IoT holds the promise of a world where, for instance, a thermostat equipped with motion sensor technology can connect to a home or business network, receive constant updates on the outside temperature, adjust indoor room temperature automatically by controlling heating and cooling systems through APIs … and tell the coffee maker to turn on when someone walks into the kitchen. Connected cars already offer APIs for remote unlocking and location services. And the list goes on; the IoT is already here. By enabling this level of interconnectivity, the IoT promises the highest degree of efficiency in terms of time and energy in our daily lives, as well as the closest levels of machine-to-machine, person-to-machine and person-to-person connectivity the world has ever known. But to make these connections positive and productive, the IoT has to be secure. In its infancy, it simply has not yet achieved the necessary level of security. Hack upon hack into smart devices, their applications and the networks on which they run prove the IoT has holes. The holes exist at the level of the APIs that form the backbone of these interconnections. Patching the holes at the API level is the key to overcoming these security hurdles and achieving success in today’s IoT landscape.