DZone Research: IoT Concerns

DZone 's Guide to

DZone Research: IoT Concerns

Intelligent apps making real-time decisions at the edge.

· IoT Zone ·
Free Resource

To understand the current and future state of IoT, we spoke to more than a dozen IT executives active in the space. Here's what they told us when we asked, "What are your biggest concerns regarding the state of IoT?"


  • 1) Security is a big one and needs to be considered by both the end product and the technology to power it. Every part of the application needs to have security in mind, with backend infrastructure and the device itself of equal importance. And upkeep of security is important as well – how do you ensure devices and apps stay secure as hacks become more sophisticated. For an example, check out how Virgil Security adds another layer of encryption on top of already secure cloud platforms. 2) Scalability is another big one. How do you ensure and maintain reliability as deployments grow? How do you ensure that users in one geographical region have the same fast, seamless experience as others? We’re relying more and more on IoT in our everyday lives, so IoT apps and products need to be ready for rapid growth and adoption. We’re built for scalability, so as apps and products take off, our infrastructure automatically scales with it, no matter where the app is located.
  • Security is still an issue. Easy to go fast and not think about it but keep seeing hacks. Breaches trust. Supporting all the different platforms and technologies is challenging. Ongoing battle. Consumers expect devices will work in a broader ecosystem.
  • Data security and privacy. Some of the big firms like IBM, Microsoft, and Google have been working on this space. We’re now hoping to participate and improve it with network security tech.
  • Security is always a top concern when you are dealing with connected devices, especially as IoT enabled products become more involved in our daily lives. There’s a lot of talk about IoT security, but there’s an important conversation not happening: who is responsible for keeping our connected devices secure? California took a stab at addressing these concerns this year, becoming the first state to create a cybersecurity law governing connected devices. Much more needs to be done to ensure consumer data is protected. Governments and companies will need to work together in this process. Ultimately though, it is up to the product creator and owner of the data to take the right steps (including user proper tools) to protect users.


  • Keep expectations on in line with what’s delivered.
  • Black boxes. We see so many vertical black box applications where you don’t have to think we’ll generate the insights. If data is unique in your organization, you need to use that to build a moat. Build capabilities to work on the data and build unique models no one else can see the value of. How to create data and skills as a durable asset.
  • Platforms are not as open as you would hope. Customers want seamless integration that’s part of a good UX. We need more collaboration.
  • Interoperability is a big concern. With the various competing or proprietary standards, it can be difficult to get new devices to work together. And then, this gets even more complicated when you add in legacy equipment and devices, which are still being used as well. This is something we’re working on continuously and solving through our software.
  • One of the biggest concerns is the maturity of many commercial IoT applications. IoT is still a relatively new technology area and companies are still learning a lot about how to best solve IoT-related problems. All good vendors are learning and evolving their solutions to take advantage of the new knowledge available to them as IoT applications go from pilot to production deployments.

Here’s who we spoke to:

cloud, data, data protection, edge, edge computing, iot, iot security, scalability, security, smart devices

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}