The biggest issue is that many of these IoT devices are badly secured. I spent years trying to convince people to build more secure IoT systems, but they always preferred cheap and easy solutions.
The biggest issue is that many of these IoT devices are badly secured. I spent years trying to convince people to build more secure IoT systems, but they always preferred cheap and easy solutions.
For me this has always been true of systems in general all across the decades that I've worked with technology. It's like pulling teeth to convince anyone in charge that backups or security are even a little bit important until after there's been a costly disaster, then it's all about "Why didn't you warn me this could happen?" - Umm... You mean like every single day for many months until you told me to shut up about it because my paranoia doesn't justify the tiny expense of ensuring you don't lose many tens of thousands of dollars or years of irreplaceable work or important records?
https://www.danfoss.com/en/service-and-support/fix-and-troub...
They highlight connection through a firewall, mention secure remote access methods, monitoring for data breaches, strong access controls, etc. Reasonable, but these are just recommendations, so the stores could have followed all of them or none at all.
An article about Danfoss vulnerabilities mentioned in a different comment (https://claroty.com/team82/research/freeze-the-controller-de...) says
> we searched publicly available internet-wide scanning platforms, including Shodan and Censys, for signatures associated with its management interface. It didn't take long to find what we were looking for. Numerous controllers [2765] were directly accessible from the public Internet.
So none at all is a possibility.
... And then the customer demands it be turned off, and the customer is always right...
Though I'm afraid things are getting worse, or at least it looked so a few years ago, back when I worked in this space. The hot thing in IIoT / Industry 4.0 was basically taking all webshit technologies and deploying them on industrial hardware, to "leverage mature innovation and OSS ecosystem" or such nonsense. The problem (one of many) being, once the engineers were done trimming excessive security measures that negatively impacted safety, they were still left with node.js running on industrial controllers, now even less secure in general than it was originally.
Did you know that buildings have doors that cannot be locked to prevent them from being opened from inside, because otherwise in case of a fire (or in the US, active shooter), people will die if they cannot exit the building?
Did you know that many industrial plants intentionally disable certificate revocation checks, because having a certificate expire on you for whatever reason is a sure-fire way to break the plant (and in some case possibly kill people), and overall a nuisance when trying to keep the plant running, while the threat it protects against can be handled elsewhere in the stack?
Security and safety are very often at odds - not just in emergency, but during regular operations.
So you can find one, log in, and have a look for yourself.
You shouldn't.
But you can.
But you shouldn't. Okay? Don't.