CyberStark
CyberStark
Get a Quote

The Machines Running Your Building Are Connected to the Internet. That Is Now a Cyber Security Problem for UK Small Businesses

5 October 2026 · 6 min read

Close-up of an industrial control panel with cables and indicator lights in a small facility

Photo by Ibrahim Boran on Unsplash

If your business has a boiler room, a factory floor, a car park barrier, a CCTV network, or even a smart thermostat wired into your building management setup, you have operational technology. And right now, critical vulnerabilities are being disclosed in the industrial control systems that run equipment exactly like that.

This week, security researchers confirmed a critical flaw in a widely used range of programmable logic controllers, the small computers embedded inside industrial equipment that tell it what to do. These devices sit inside manufacturing lines, access control systems, building automation setups, and utilities across the UK. The severity was high enough that organisations were specifically told to review and update their incident response plans without delay.

If your instinct is that this sounds like a problem for large manufacturers rather than a business your size, you are in good company. But that instinct is worth questioning before you move on.

Do You Actually Have Operational Technology in Your Business?

Operational technology, or OT, is any hardware or software that monitors or controls physical equipment. Traditional IT processes data. OT controls the physical world. For a small business, it might look like any of these:

  • A building management system controlling heating, ventilation, and air conditioning
  • Networked electronic door locks or an access control panel
  • A CCTV or surveillance system with a networked recorder
  • Smart meters or energy monitoring devices
  • Production or assembly equipment with programmable controllers

These devices were originally designed to be isolated, running on closed networks with no internet connection. Over the past decade that changed. Equipment is now routinely connected for remote monitoring, software updates, and management convenience. The result is that vulnerabilities in these systems are reachable by attackers who are nowhere near your premises.

Why OT Vulnerabilities Are a Different Kind of Problem

When a flaw appears in typical business software, the fix is usually an update. You patch it and the risk closes. With industrial control systems it is rarely that straightforward.

Many OT devices run firmware that cannot be updated without shutting down the equipment they control. Some run on older software where vendor support has ended entirely. Others sit in locations where applying a fix requires specialist engineers and planned downtime. For a small manufacturer or a business with an older building management system, that creates a window of exposure that can stretch for months or years after a vulnerability becomes public knowledge.

The consequences of an attack on OT go beyond a data breach. If a system controlling physical equipment is compromised, the damage is not just to your data. It can be to your operations, your premises, and in the worst cases to the safety of people on site. That changes the risk calculation significantly.

What Attackers Actually Do With These Weaknesses

The groups targeting OT systems are not all sophisticated state-level actors. Ransomware operators have increasingly turned their attention to operational systems because the pressure to pay is far higher when a production line is standing still or a building cannot function. A business that can absorb days of IT disruption may not be able to absorb hours of an operational shutdown.

Lateral movement is the other real concern. An attacker who gains a foothold in an OT device on your network does not have to stay there. If your operational systems and your business IT share the same network, access to one can become access to the other. This is exactly why network segmentation, keeping OT and IT traffic separated, sits at the top of almost every piece of OT security guidance published anywhere in the world.

Practical Steps for a Small Business

You do not need to be running a power station to take this seriously. The practical steps for a small business are not dramatically different from good IT hygiene, with a few OT-specific additions.

Know what you have connected. Start with a full inventory of every networked device in your business, not just laptops and phones. That includes CCTV recorders, smart devices, access control panels, and any equipment with a network port. If you do not know what is connected, you cannot protect it. Vulnerability scanning can surface devices and known weaknesses across your environment without guesswork.

Segment your network. Where possible, OT and IT systems should sit on separate network segments. Your building management system should not be on the same network as your accounts team. A conversation with your IT provider about basic network segmentation is a worthwhile investment, not a luxury.

Stay on top of patching. For every device that can be updated, make sure it is. Automated patch management removes the risk of updates being quietly missed across your standard endpoints, and forms part of any solid baseline security setup. For OT devices specifically, check manufacturer guidance on firmware updates and set a regular reminder to review it.

Have a response plan. The direct advice from this week's disclosure was to review incident response plans. That guidance is not only for enterprise security teams. Even a brief document covering who gets called, what gets isolated, and who makes the call in the event of a suspected incident is better than starting from scratch in a moment of pressure. As we have covered previously, attackers do not wait for you to be ready.

Reduce your internet-facing exposure. Any OT device that does not need direct internet access should not have it. Remote access, where genuinely needed, should go through a properly secured and monitored route rather than being left open. Our earlier piece on prioritising vulnerabilities when resources are limited offers a practical framework for deciding where to start.

One More Thing Worth Checking

Default credentials are still one of the most common ways attackers get into connected devices. Programmable controllers, CCTV recorders, and building management systems frequently ship with usernames and passwords that are publicly documented and never changed. If any device in your business is still running default login details, that is the first thing to fix, before anything else on this list.

The Takeaway

OT security is no longer a niche concern for large industrial operators. Any small business with connected physical equipment has some level of exposure to the same class of vulnerabilities making headlines this week. The first steps are not complicated: know what you have connected, keep it updated where you can, separate your operational and business networks, change default credentials, and have a response plan ready before you need one.

If you are not sure where your business currently stands, a vulnerability scan is the most practical starting point. It surfaces the gaps without guesswork and gives you something concrete to act on. Get in touch if you want to talk through what makes sense for your setup.

FAQ

Common questions

Possibly yes. Operational technology is not limited to factories. If your premises has networked access control, a building management system, a CCTV recorder, smart meters, or any internet-connected equipment that controls something physical, you have OT in your business. The vulnerabilities being disclosed affect these types of devices, not only large industrial sites.

The most common routes are unpatched software flaws, default credentials that were never changed, and devices that are directly accessible from the internet with no additional security in front of them. Once access is gained, attackers can disrupt operations, move across to business IT systems, or hold the device to ransom.

Network segmentation means keeping different types of devices on separate parts of your network so that a compromise of one cannot automatically spread to others. If your CCTV system, your building controls, and your finance team's laptops all sit on the same network, a breach of any one of them creates a path to the others. Segmentation removes that path. It is recommended for any business with a mix of operational and business IT.

If patching is not immediately possible, focus on reducing exposure in other ways: ensure the device is not directly accessible from the internet, change any default credentials, and restrict which other systems on your network can communicate with it. Document the unpatched device as a known risk and set a date to review whether patching becomes feasible.

At a minimum it should cover: who in the business is responsible for making decisions during an incident, who your IT provider or security contact is and how to reach them out of hours, which systems should be isolated first if a breach is suspected, and how you will communicate with staff and customers. It does not need to be long, but it does need to exist before something goes wrong, not written in the middle of it.

Get certified in as little as 5 days

Tell us a little about your organisation and we'll send an itemised quote, no obligation, no sales call required to get pricing.

We use essential cookies to make this site work (e.g. keeping your quote calculator session active), and, only if you accept, Google Analytics and the Meta (Facebook) Pixel for analytics and advertising measurement. See our Cookie Policy for details.