Concerns Regarding IoT

DZone 's Guide to

Concerns Regarding IoT

We spoke with 20 executives in different industries in the IoT space. They let us know what their primary concerns are—specifically, privacy, security, and interoperability.

· IoT Zone ·
Free Resource

We asked this question of 20 business executives in different industries. While the primary concerns revolve around privacy and security, several folks brought a very real concern of who supports these devices when they go down because we’ll become just as reliant on our IoT devices as we have the internet.

  1. We’re so dependent on it, what happens if it goes down?
  2. Always have to be on the lookout for hackers. They will try to screw things up. We are consulting with our clients to determine what’s the worst thing that can happen and then do everything we know to prevent it.
  3. Security. Xively has a thorough workflow for identity and access management to authorize and verify users. How do we manage security when it’s no longer one-to-one? How do we scale to use data for the good of the individual while protecting personal data?
  4. Security. The risk posed for remote threats to breach your home network through an IoT device.
  5. Some people will benefit greatly. People on assembly lines will lose their jobs. People become too reliant on certain systems. They assume all of the data is correct. We must build systems that inform us and ensure they’re delivering the information we need accurately.
  6. As a consumer, I’m concerned about privacy and security. Companies are taking an expedient approach and not taking privacy and security into consideration. We’ve thought about it from the beginning. Devices don’t get hijacked because of authorization and encryption. Lock tight user security.
  7. Data security and privacy. Access to the data. Having meaningful use cases and applications.
  8. No concerns. They’re helping us live better. Some people are afraid of the rise of machines but machines without people are stupid. Many people are losing their jobs.
  9. Ensure we use machines as a tool and remember that they can’t think and analytics can’t replace humans.
  10. It’s moved faster than privacy and security can keep up with. Need standardization of messaging platform. There are dozens. I see a Cisco or Amazon leading the way. This will be network driven. From the network layer out - industrially based.
  11. Security of the data and use of the data.
  12. Enabling the world in a different way - people will build malicious products to hack and scam the system. There will be a level of maturity and sophistication to remove the malicious things. As technologists are evolving, you will see a repetition of best practices that’s transferred from industry to industry.
  13. Yes, there are a lot of smart, but inexperienced people building products. They haven’t had the time to learn from their mistakes, how to solve problems, how to prevent security issues. Over the past 25 years I’ve learned by making mistakes. We ran into a problem with security scanning at one of our clients with software running at night. We replicated the situation in our lab and fixed the problem and will be able to avoid that problem in future situations.
  14. It's growing so quickly. There’s overhype on things that aren’t critical and things that can, and should be done right, are not. Eight years ago WPA was the security standard. Today it’s easily hacked but that’s what many IoT products are using. We use AAA and it doesn’t cost any more than WPA but people haven’t taken the time to do the research. If an IoT product gets hacked like the Target database, it will hurt all IoT products. People looking to do it themselves have a lot to learn with all aspects of development - especially how to scale from 500 to one million units.
  15. Interoperability and security don’t get left behind. Define standards to build the platform. Have a well known security model that everyone adopts. Some vendors are jumping the gun just to get a product to market quickly. Standards need to get a stamp of approval. In industrial IoT OPC drives standards. IIC (Industrial Internet Consortium) is also a significant standards body. It will need to be a collaboration of many. Don’t know who does this in the consumer space.
  16. It’s the wild west. Need standards. The security issues alone are crazy. Privacy. Singularity when machines can talk among each other. If the government requires backdoor access to IoT devices. The concept of IoT is infiltrating our lifestyle.
  17. Privacy and security. If people can hack your lights, they can hack your home. Security will be handled as we learn more about the technology. It’s a matter of time of adoption and the importance to users. Privacy is gone with social media in the U.S. Germany is more strict. They recently sued Google on the collection of data. There’s a much stronger sense of privacy in Europe than in the U.S.
  18. We are vigilant around security and privacy. It is not acceptable for prying eyes to have access to data or for anyone to have unauthorized access into systems. GE bought Wurldtech to advance their IoT security. We design security and privacy through implementation. The value of being connected is worth more than the risk of losing data or being hacked; however, the risk is approaching a break even point. We are well past the tipping point on personal intelligence as people get far more value from Google than they care what information is being collected about them.
  19. Security is the biggest issue but support isn’t far behind. Who do you call when an IoT device goes down? IT is now getting calls because the radiology department just bought four portable x-ray machines that connect to the internet. United airlines went down when the software app for the pilots’ ipad with flight plans was upgraded and crashed the system.
  20. Ensure you have a good sense for what part of the system should do what. Simplify IT devices collecting data with logic to process motion detection. Send to gateway for security, access control, identity management, interpret the data and the event. The underlying business logic must be very specific based on the situation. Keep concerns separated to deploy actions quickly and correctly based on the threat or need. You can always go back and look at the data and see if the process worked as planned. If the human doesn’t respond, the process is in place to take action. Write rules in such a way that recognizes we’re human beings, not machines. Identify the best practice to alleviate concerns. Map to a world that’s a connected IoT world, not the world as we knew it.

Do you have concerns about IoT that are similar to, or different from, those shared here?

concerns, data, interoperability, iot, privacy, security

Opinions expressed by DZone contributors are their own.

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

{{ parent.tldr }}

{{ parent.urlSource.name }}