Similarly, I don't think it's unreasonable to hold IoT manufacturers accountable for releasing blatant security vulnerabilities into the wild (like that webcam that DDoS'd all those sites).
This isn't an "aww, growing pains" kinda moment of care for the poor budding IoT industry. They need to realize that they must be held accountable.
Edit: "bulletproof" isn't even what's being asked, but putting some thought into the security of their IoT devices is something we must demand of manufacturers
If a product desperately needs network connectivity, but is still prohibitively expensive to secure, I'm sympathetic. (Not forgiving, mind, but I understand the difficulty.) But when you're releasing a wifi teakettle, or a networked lightswitch that's talking to one other switch 5 feet away? At that point I think there's basically no excuse at all. Teakettles work great as is, adding insecure network support creates a product substantially worse than one without any software at all.
More theoretically, I can imagine an IoT product so good that they should just pay for the externalities they cause and keep manufacturing. But most insecure products out there today are creating far more externality than value, and wouldn't exist if they had to deal with the harm they cause.
IoT manufacturers don't have to contract Linus Torvald to review their code, but it's entirely reasonable to expect IoT manufacturers to use existing best practices to secure these products.
"Are all your device privates derived from the same key? Do you ask your users to install your public root to get past security warnings?"
Yet they clearly don't understand PKI 101 and think what they are doing is completely appropriate because they are "following standards" while of course missing the bigger picture entirely.
Hell, the Ring issue wouldn't even require one direct employee to avoid. You could solve that in a 30 minute call to an "is this obviously terrible?" hotline.
The only realistic solution I can think of is creation of the open communication and security protocols with easily available standard libraries. A good example is HTTPS, which is far from perfect now, but is common today thanks to TLS and OpenSSL. We need something like Linux kernel - free, widespread, well understood, easy to port and use. Few big companies could make it work, but the problem is that there's not much money in creating open protocols and FOSS libraries. Maybe some IoT orientated Linux kernel branch with minimal set of functionality, safer of out-of-box configuration and basic security solutions preinstalled?
There is also the open-source Zephyr RTOS for IoT, of Intel WindRiver lineage, under Linux Foundation governance, https://www.zephyrproject.org
Edit: See http://mender.io for OTA updates (open-source client and server). If IoT device vendors separate their application code from the base operating system, e.g. via containers or virtualization, it may be possible for a vendor-authorized subscription service (like Mender) to deliver OTA updates for security-critical components.
To drive a car or keep people's Credit Card information you need certain certification. What makes no sense for me is to assume that keeping kids records on a public DB because someone has no clue on what they are doing is reasonable (for example). Or that needing an internet connection for turning off your heater is reasonable.
We need to understand IoT is not a toy, we should require certification, fines or both.
When I got to make a website, I don't say I can't make it secure because I can't afford to be an expert in security at every level of the OSI. I say I'm not an expert in every level of the OSI so I rely on accepted best practices and community standards to make my site secure.
I don't replace HTTPS with my own standard because I can't afford to make an adequate and secure replacement. If IoT makers can't make their own custom solutions secure then they need to build their devices out of standardized pieces that are secure.
That's exactly the problem with IoT-- there's no standard, out-of-box solutions right now. Try to google for "IoT security": you will find a bunch of (mostly proprietary) competing solutions with no clear leaders among them. See my other comment on this thread, were I've provided HTTPS as an example for IoT ecosystem. I'm an experienced embedded developer and most often, when it comes to security, I still have resort back to "invent my own" security solution, because I can't find anything that fits project needs.
note: I know you were not suggesting HTTPS as a solution only as an example of a standard used other places. I'm only pointing it out as another example of an issue IoT has which is lack of solutions .
The only solution I know of is Plex's solution which was to partner with a CA for $$$$$$
https://blog.filippo.io/how-plex-is-doing-https-for-all-its-...
What's wrong with using the mbed security stack as a standard for mcu's ?
Try to find a piece of hardware in your home that was not built by a software company where the software is even close to decent.
Sorry, but this is complete and utter nonsense.
Nobody is asking IoT manufacturers to provide perfect security. It's about the absolute minimum basics. There's one single security mechanism that's totally obvious that would have completely prevented the whole Mirai botnet: Don't use default passwords. It's not too much to ask for that.
A self-updating debian install with a unique random password you deliver in a piece of paper inside the box should be enough.
If it isn't then there's something very odd with the legal processes, as your team of experts wouldn't be able to deliver it either.
i built a system that other people will be able to use to secure their IoT products; in fact, if you can write a simple arduino sketch, you can secure it very quickly
http://ardiri.com/blog/stockholm_terror_attack_how_iot_could...
To me it is unreasonable to ever expect that all of them will be linux specialists, expert cryptographers, network specialists, etc.
Fundamentally we are at the convergence of software and hardware, but the software is too complicated, give people too many ways to shoot themselves in the foot.
I'd argue we need better software, not IoT manufacturers sinking ressources in hundreds of unrelated expertises.