4 ms·

We'll start seeing this becoming more common, until the best-practices suggest that IoT/embedded frameworks have to be on a network completely separate from the

We'll start seeing this becoming more common, until the best-practices suggest that IoT/embedded frameworks have to be on a network completely separate from the common/public internet. (This will not just mean a network to VPN into, but physically separate, with no device-intermingling.)

drcode 10y ago
That will never become best practices, simply because there is too much benefit in being able to control IoT/embedded devices through the web. The only realistic solution is to develop technology (and associated practices) that are more secure against hacking- And yes, there will be lots and lots of pain on the way to reaching that goal.
userbinator 10y ago
Electronic locks have been around for a long time, and the earlier systems were not Internet connected because it would've been additional cost at essentially no advantage. Now it seems like hardware/software has become so cheap (and unfortunately more complex, thus more likely to contain non-obvious bugs and misfeatures) that in some ways it's easier to develop products based on Internet standards than isolated proprietary protocols, putting the "does this really need to be connected to the Internet?" question mostly out of mind. I don't think it's about "best practices" or any sort of dogma, but more of a common-sense evaluation: do you really need your lock systems accessible from anywhere on the planet, which connecting to the Internet enables?
- anilgulecha 10y ago
  > it's easier to develop products based on Internet standards than isolated proprietary protocols Building on TCP/IP is just fine (in-fact recommended) -- just keep that network physically isolated to the location it's implemented at.
  - mypalmike 10y ago
    I wonder how many of these lock systems rely on cloud services, making physical isolation impossible without some redesign.

drcode 10y ago

That will never become best practices, simply because there is too much benefit in being able to control IoT/embedded devices through the web. The only realistic solution is to develop technology (and associated practices) that are more secure against hacking- And yes, there will be lots and lots of pain on the way to reaching that goal.

userbinator 10y ago

Electronic locks have been around for a long time, and the earlier systems were not Internet connected because it would've been additional cost at essentially no advantage. Now it seems like hardware/software has become so cheap (and unfortunately more complex, thus more likely to contain non-obvious bugs and misfeatures) that in some ways it's easier to develop products based on Internet standards than isolated proprietary protocols, putting the "does this really need to be connected to the Internet?" question mostly out of mind. I don't think it's about "best practices" or any sort of dogma, but more of a common-sense evaluation: do you really need your lock systems accessible from anywhere on the planet, which connecting to the Internet enables?

anilgulecha 10y ago
> it's easier to develop products based on Internet standards than isolated proprietary protocols Building on TCP/IP is just fine (in-fact recommended) -- just keep that network physically isolated to the location it's implemented at.
- mypalmike 10y ago
  I wonder how many of these lock systems rely on cloud services, making physical isolation impossible without some redesign.