Marios PriftiCTO & CPTO Book intro call

Cybersecurity Is Not an Unexpected Expense

Security gets funded in waves and dropped when the headlines move on. The supermarket fridge cyberattacks show what that costs.

Security

Every time another company suffers a cyberattack, the reaction is the same: surprise, urgency, emergency meetings, and a scramble to understand how it happened.

But in most cases, the warning signs were already there.

The wave: what the supermarket fridge cyberattacks show

While a wave of attacks is in the news, security suddenly becomes a priority. Everyone agrees that solid architecture, careful engineering, proper specifications, consistent processes, documentation, testing and experienced technical judgement matter. Budgets appear. Audits get booked. The people who have been asking for this work for years are finally listened to.

Right now we are in one of those waves. In October and again on 2 November, attackers switched supermarket fridges and freezers across Europe to defrost mode, heating some to around 50°C and forcing stores in France, Belgium, the Netherlands, Sweden, Ireland and beyond to throw away food.

Nothing about it was sophisticated. It was a failure of basic cyber hygiene and IoT security: the refrigeration controllers were reachable from the internet, many ran outdated software, and the UK's National Cyber Security Centre said they had been left with default passwords.

And the warning signs really were there. Back in 2019, researchers showed that supermarket refrigeration systems could be defrosted remotely using default passwords published in the manufacturer's own manual. It made the news. Then the news moved on.

Why cybersecurity budgets fade after an attack

That is the pattern I want to talk about. Not the attack itself, but what happens in the months after it.

Too often, security quietly goes back to being a "nice to have". Architecture becomes something to revisit later. Engineering discipline is traded for speed. Preventive work, from patch management to access reviews, loses its funding because it does not produce an immediate, visible return.

The data suggests this is the norm, not the exception. In an IANS survey of security budgets, only 3% of security leaders named a breach as a reason their budget had grown. Even a major breach brought, on average, a 9% increase. The urgency is real, but it does not last long enough to change how the work is funded.

Until the next incident.

Why security investment loses to new features

Prevention has a presentation problem. When it works, nothing happens, and nothing does not look like a return on investment. That is why cybersecurity ROI is so hard to argue in a budget meeting.

A new feature has a launch date, a demo and a revenue forecast. A patched server, a removed default password or a system moved off the public internet has none of those. In a roadmap meeting, the feature wins almost every time. Each individual decision looks reasonable. Together, they build up exactly the kind of exposure that attackers look for.

There is a second, quieter cost. The engineers and architects who insist on doing things properly start to be seen as the people slowing the business down. They are the ones asking for specifications, pushing back on shortcuts and asking who will maintain the thing after launch. In a calm period, that can look like caution for its own sake. After an incident, it looks like foresight.

Secure by design: security is a responsibility, not a reaction

Security is not a temporary response to bad headlines. It is an ongoing business responsibility. The US cybersecurity agency's Secure by Design guidance treats it the same way: built into design, development, deployment and operations from the start, and owned at executive level, not added after something goes wrong.

The same applies to sound engineering decisions in general.

  • Consistency is not bureaucracy. It is what makes the exception visible. When every system is set up the same way, the one that is not stands out before an attacker finds it.
  • Documentation is not overhead. You cannot patch, replace or isolate a system you do not know you have, and in an incident it is what lets someone other than the original author act quickly.
  • Testing is not a delay. Every weakness found before release is one an attacker cannot use, and one you do not have to fix at 3am under pressure.
  • Clear specifications are not unnecessary detail. Who can access a system, from where and how, is a security decision. If nobody writes it down, nobody makes it, and the default makes it for you.
  • Good architecture is not an academic exercise. It decides how far an attacker gets once inside, and whether a problem stays in one system or spreads to the whole business.

These are ways of reducing risk before it becomes downtime, financial loss, legal exposure, reputational damage and lost customer trust. The people who insist on these principles are not slowing the business down. They are helping to prevent it from being brought to a standstill.

How to fund cybersecurity as an ongoing responsibility

If security is an ongoing responsibility, it should be funded like one, not like a project that starts after an incident and ends when the headlines do. For a CTO and the board, that means:

  1. A baseline that does not move with the news. Patching, access reviews, documentation and testing get a fixed share of engineering time, every quarter.
  2. An owner at executive level. Someone with the authority and budget to say no to a shortcut, and to explain the risk to the board.
  3. Valuing the people who insist. Treat the engineer who asks "who can access this?" as a source of value, not friction.
  4. Measuring what did not happen. Track known vulnerabilities, time to fix them and systems still on default settings, so prevention has numbers too.

The real question

So perhaps the real question is not whether companies can afford experienced engineers, robust architecture and disciplined development practices.

It is whether they can afford to keep undervaluing them, until the next attack reminds them why they mattered.

More from the blog

Keep reading

Contact

Have a technology decision worth discussing?

Every engagement is scoped and priced to the case. A 15-minute intro call is the quickest way to find out what yours needs, and whether deeper work is worth it.

  • 15 minutes
  • By video
  • Confidential, NDA on request
  • Europe & US time zones