This month provides me the opportunity to share several examples of recent IoT hacks, and demonstrate how one can introduce risks when adding smart devices to a network. Leveraging this survey of happenings in IoT security breaches, it serves as a reminder to the importance of security as IoT evolves. As we’ve talked about in recent posts, MQTT is one example of a standard that is evolving to help address some security concerns in the IoT space. However, as we’ll see in at least one example, if users of IoT devices are not willing to care about security themselves, no amount of fancy protocols will solve your all your problems. Without further delay, let’s read through some of the more interesting recent IoT hacks.
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
Like a kid at Christmas, IoT nerds everywhere can hardly contain their excitement for the upcoming release of the MQTT 5.0 connectivity protocol. For those of you who are past setting out cookies and carrots for the fat man and his deer and prefer to scrooge things up a bit, read on and learn about some of the exciting new features in MQTT 5.0.
In my last blog post, we discussed the use of the Publish-Subscribe design pattern. Near the end of that post we introduced MQTT, and in this blog post we shall go more in depth on MQTT. The motivation in exploring and learning about MQTT is that it is a standard used for IoT applications which addresses several concerns around the emerging IoT space; lack of standards, security, and privacy. Much of what is presented here about the standard can also be found across a variety of other websites including Wikipedia and the MQTT homepage, the latter of which is a wonderful resource for exploring the standard in depth.
In previous blog posts, I’ve spent a lot of time sharing info about precision agriculture. This month and in the months to come, I’ll be focusing on design patterns relevant to IoT. When it comes to solving problems in new domains or with new technologies, one often benefits by framing the problem in the context of problems already solved. Mathematicians are notorious for taking a seemingly new and challenging problem and applying a well-known technique to solve it. For example, going through integral calculus will lead a student to be exposed to both u-substitution and trig substitution. In both cases, we are taking what appears to be a hard problem and turning it into an easier problem we’ve previously solved. We are also using a type of design pattern - substitution in this case - to tackle hard problems. This exact same approach happens in software engineering as we apply well established design patterns when we work with new technologies, languages, and domains.