Great input, thanks!
My next step is to deploy on a normal ISP and not on a cloud provider. Just let it sit there.
I think we should give back to those companies as much as possible. OT is not where the big money is and all security experts are flocking to.
I've already started some actions in this direction btw.
The more people that can deploy it, the higher the chance of discovering something about the attacks. Also this gave me an incentive to look deeper into the real software.
New ideas are popping up. I started with fridges because of the recent attacks, but the code makes it easy to add personas. Electric car charing stations and coffee machines were my initial idea, but HVAC and building controllers are probably better ideas. Thanks!
Plot twist: the hackers are members of the Van Helsing Society and the supermarkets were just a trial run in their war against the International Vampire Cabal.
One thing keeps coming back, (and it's the story of industries where security and patching is an afterthought).
a supermarket has no security team.
If a fridge controller needs patching, a VPN and a strong password to be safe, that work has to come from the vendor or installer by default.
One would hope that all these come by default or as a feature on these devices. It could even be a selling feature and not part of an expensive maintenance contract. A supermarket manager cannot be expected to do this work.
This is how it should work: supermarket wants to use high tech stuff such as connected fridges, they get a cyber insurance policy as part of all the other insurances they have. The insurer then has domain experts to figure out what the insured needs to do to meet a risk threshold (or they adjust fees accordingly).
This model has worked fine for many other types of risks.
That's a problem for the insurance company (in a simplistic way): if they aren't efficient, they'll eventually get replaced by a company which is.
Obviously, the incompetent insurance company will entrench itself by lobbying for laws / making it harder for other companies to compete / get bailed out by a state or country when they fail.
Or, more likely, they will make a compliance checklist that is sufficiently difficult to comply with fully they'll have a means to deny most or all of the claims against the policy. I don't think the insurance industry is very efficient.
That seems pretty location dependant. In Australia at least the two major supermarket chains are not insignificant (e.g. EBITDA ~$5 billion and ~$2.6 billion) and have large internal tech and cyber teams.
I think this is more indicative of the plethora of technical debt and straight up technical negligence that's accompanied the past 10-15 years of internet connected everything. What's happening today is the predictable result of project based works funded by capex deploying assets (of all types) with no consideration of opex funding for the technology components.
Just because a webserver is running in some physical device (fridge, camera, vacuum, washing machine, pump controller, lighting system, audiovisual equipment, access control system etc) does not magically exempt it from the same sort of ongoing sysadmin and maintenance you'd expect as a baseline for something running on standard compute. That applies equally to manufacturers publishing firmware, and the asset owners/service companies that have the responsibility to apply.
Agree with all of what you're saying, wholeheartedly.
But I keep coming back to: why do supermarkets need networked freezers anyway? Most supermarkets are open most days, with long hours. Can't any adjustments just be done manually by staff on the rare occasions when that is needed? I've seen some people argue that the major usecase is defrosting. But when you're defrosting, you certainly have lots of people on site engaged in emptying the fridge in question. Surely flipping the thermostat is a rounding error as far as costs go?
Monitoring/logging/alerting can all be done without storing the network connected computer up to anything that can change the temperature settings. It can and should be a completely separate system.
I work at a company that sells security software, and one of our customers is a major grocery chain. They definitely have a security team, I’ve talked to them.
It's most certainly a form or hybrid warfare. While being very easy to perform, it's still quite effective. Empty supermarkets and supply chains being disturbed.
Hopefully this is a wakeup call for the industry.
> Hopefully this is a wakeup call for the industry.
Would be nice but none of the other events has been.
It seems like something horrific is going to have to happen before this is taken as seriously by government and private orgs as it should have been, that seems to be how it works with other stuff historically.
My view is that some companies installing this have not implemented any defense in depth and cut corners all around. Installing a firewall with a simple vpn service would probably have prevented lots of pain (unfrosting).
In general we also see almost every security expert working at banks or other high paying companies and not for supermarkets.
My feeling is that this 'niche' is probably interesting to spend some 'tokens' and time on.
What I meant is that I'd find some way of ensuring that I'd want to ensure that the responses you're serving up are real. If you are happy with what you have, we're good.
reply