Cyber Security
•
29 October 2026

Why patching and tested backups are a board level production issue

Server rack in a factory comms room with a maintenance window schedule on the door.

Why patching and tested backups are a board-level production issue

Because they decide how long production stays down. Unpatched systems are a common way in for attackers, and a backup that has never been restored is a hope, not a plan. Both need budget, maintenance windows and sometimes a decision to accept risk. That’s why they belong on the board’s agenda, not only IT’s.

How common are patching gaps in UK manufacturing?

Common. Make UK’s 2026 survey found only 36% of UK manufacturers use patch management, against 92% with firewalls and 80% with malware protection. Across all UK businesses, only 34% have a policy to apply security updates within 14 days. Most firms have bought the defences, but fewer keep the systems behind them up to date.

Make UK calls the patching figure “a potential vulnerability” and says keeping systems up to date remains one of the most effective protections against ransomware. The 34% comes from the government’s Cyber Security Breaches Survey 2025/2026.

In a factory the reasons are understandable:

  • the ERP server can’t restart during a shift;
  • a machine builder says not to update the PC attached to its kit;
  • there’s one IT person, and patching happens when they get a quiet weekend.

None of those are IT problems alone. They’re production and commercial decisions, which is the point.

Why is patching a board decision and not just an IT task?

Because the hard part isn’t installing updates. It’s agreeing when systems can go down, what happens to kit that can’t be updated, and who accepts the risk if it isn’t. The NCSC’s vulnerability management guidance says a decision not to update is a senior-level risk decision. That makes it the board’s call, with IT’s advice.

The pressure is rising. In May 2026 the NCSC’s CTO warned of a “vulnerability patch wave”: AI is helping skilled attackers find and exploit old weaknesses at scale, so organisations should expect more urgent updates, more often. The NCSC’s advice:

  • update by default, and turn on automatic updates where they’re available;
  • deal with internet-facing systems first, then work inwards;
  • replace, or bring back into support, anything end of life;
  • speed up when a critical flaw is being actively exploited.

There’s a commercial edge too. Under the April 2026 Cyber Essentials changes, for assessments opened after 26 April 2026, high-risk or critical updates not installed within 14 days mean an automatic fail. The director who signs the declaration also confirms you’ll stay compliant for the whole certification period. If customers ask for Cyber Essentials, your patch cadence now decides whether you pass.

What end-of-support deadlines should manufacturers plan for?

The nearest is Windows Server 2016. Microsoft’s extended support ends on 12 January 2027, after which there are no free security updates. If your ERP, SQL, file or SCADA servers run on it, that date matters. Cyber Essentials also requires systems to be supported on the date the certificate is issued, which turns an old server into a renewal problem.

Microsoft has announced paid Extended Security Updates for Windows Server 2016, so there are three broad routes:

OptionWhat it meansBoard question
Upgrade or replaceMove the workload to a supported serverWhen is the maintenance window, and what’s the rollback plan?
Pay for Extended Security UpdatesBuy time, at a cost, while you planAre we eligible, and what’s the exit date?
Isolate and reduce scopeSeparate the old system and limit what can reach it. For Cyber Essentials, unsupported software must sit in a separate sub-set with no internet traffic in or outIs this a short-term measure with an owner and a date?

Whichever route you choose, write it down with a date and a name next to it.

What does a “tested backup” actually mean?

It means you’ve restored from it recently, timed it, and know it works. The NCSC says backups should let you restore data, applications, identity systems and configuration, not just files. They should be protected from deletion or change, immutable where possible, stored separately from your main systems, and tested regularly.

The NCSC published new guidance on disruptive cyber attacks, including how to prepare your technical recovery on 1 October 2026. For a factory, the practical parts are:

  • Restore the whole service, not one file. Can you bring back the ERP server, its database and the accounts people log in with?
  • Know the restart order. Network, identity, database, application, then users. Document it and store it away from the systems it describes.
  • Include the shop floor. If you have OT, test restoring it to a known good state, and make sure IT and OT recovery plans line up.
  • Keep an offline copy. The NCSC’s 10 Steps recommends the 3-2-1 approach and keeping backups for at least a month, because damage can go unnoticed before a single rolling backup is overwritten.

Attackers often target backups, because a business that can restore is under far less pressure to pay. A tested, offline backup gives you a way back.

What should the board ask about patching and backups each quarter?

Six plain questions, each answered with evidence rather than reassurance. What percentage of critical updates went in within 14 days? What’s still end of life? When did we last restore a key system, and how long did it take? Who owns each risk we’ve accepted? Make UK’s advice is simple: test recovery, not just response.

QuestionEvidence to ask for
Are critical updates going in within 14 days?A monthly patch report showing exceptions
What’s out of support or close to it?A dated list with an owner and a plan per item
When did we last restore a critical system?A restore test record with the time it took
How much data could we lose?The agreed recovery point for ERP and production data
What have we decided not to patch, and why?A short risk register entry signed by a director
Who would we call at 2am?Named contacts, stored offline

Governance is where manufacturers have most room to improve. Make UK found 51% have incident response processes, 45% have a senior leader responsible for cyber security, and 39% discuss it regularly at board or risk meetings.

Key takeaways

  • Only 36% of UK manufacturers use patch management (Make UK, 2026).
  • The NCSC says a decision not to update is a senior-level risk decision.
  • Under the April 2026 rules, missing the 14-day window for high-risk or critical updates is an automatic Cyber Essentials fail.
  • Windows Server 2016 extended support ends on 12 January 2027.
  • A tested backup is one you’ve restored recently, timed and documented.

Frequently asked questions

How quickly should security updates be applied?

The NCSC advises updating by default, as soon as possible and ideally automatically. For Cyber Essentials, high-risk and critical updates for operating systems, router and firewall firmware, and applications must be installed within 14 days of release. For assessments opened after 26 April 2026, missing that window is an automatic fail.

How often should we test our backups?

Regularly, and always after a major change. The NCSC recommends testing restores before you need them and prioritising business-critical services. A sensible pattern is a small restore check every month and a full test of a critical system such as ERP at least once a year, timed and written up.

What happens when Windows Server 2016 support ends?

From 12 January 2027 Microsoft stops free security updates for Windows Server 2016. Servers keep running, but new flaws stay unfixed. You can upgrade, pay for Extended Security Updates, or isolate the system while you plan. Unsupported systems can also put Cyber Essentials certification at risk.

Can we patch factory machines the same way as office PCs?

Not always. The NCSC accepts that updating by default may not apply to safety-critical systems and OT. Where kit can’t be updated quickly, agree a maintenance window with engineering and the machine builder, and protect it in the meantime by separating it from the rest of the network.

TekXera looks after servers and backups for UK businesses. If you’d like a second view of your patching and backups before the board asks, our CTO runs a free IT assessment.

Book a free IT assessment

Related articles

Start your journey with Tekxera today

The future of IT at your fingertips