← Back to InsightsSecurity

What to Do With Devices You Can't Patch: Containing IoT and Legacy Equipment

· 3 min read

A CybertronIT technician pushing security updates from her monitoring station

When a device can’t be patched, contain it: put it on its own network segment, let it talk only to the systems it needs and watch its traffic. That matters more each year, because AI is shortening the time between a software flaw existing and an attacker using it.

Why waiting to patch stopped being safe

For decades, finding a serious unknown vulnerability took elite people, months of manual code review and expensive tooling. That friction gave defenders a grace period. AI is erasing it. AI doesn’t get bored or frustrated, and it works through tedious steps in seconds.

The old approach was to patch on a comfortable schedule. When the time to weaponize a new bug keeps shrinking, that schedule is a long stretch of exposure. If your approach to updates is “when we get to it,” you’re choosing to stay exposed. Our post on why once-a-month patching no longer keeps you safe covers the timing.

The unpatchable device problem

Patching assumes you can patch. Plenty of networks hold equipment that can’t be: sensors, cameras, machine controllers and medical devices that run for years on firmware nobody updates. A bug that has sat in one of those for years should be treated as something an attacker will find tomorrow. Our post on the network risk in smart devices explains how they become a way in.

How to contain a device you can’t patch

  1. Inventory the unpatchables. You can’t protect what you can’t see. Find every legacy controller, medical device and sensor on your network and write it down.
  2. Assume compromise. If a device has gone years without updates, build your defenses as if it’s already breached.
  3. Segment the network. These devices can’t run security software, so enforce the rules at the network. A device should reach the handful of systems it needs and nothing else.
  4. Keep it off the open internet. If it doesn’t need outside access, block it.
  5. Change default passwords and turn off features you don’t use.
  6. Watch the traffic. A sensor that starts talking to an unfamiliar address is a warning.
  7. Put a replacement date on it. Containment buys time. It doesn’t make the device safe.

The same thinking applies to old software, which our post on defending legacy software you can’t replace yet covers.

Patch what you can, quickly

Everything that can take updates should get them fast: computers, servers, firewalls and business applications. Patch management is part of every engagement in Cybersecurity Services, and for production floors our manufacturing IT page covers how we work around equipment that has to keep running.

If you have equipment you can’t update, book a 30-minute call. We’ll ask what’s on your network and how it’s separated today, and tell you which devices we’d fence off first.

Want this handled for your business? Book a 30-minute call and we'll give you a straight read on where you stand.

Book a call

FAQs

What is an unpatchable device?

Equipment that can't receive security updates: a sensor, camera, machine controller or medical device whose manufacturer stopped supporting it, or that can't be taken offline to update.

How do you secure a device that can't be patched?

Contain it. Put it on its own network segment, allow it to talk only to the systems it needs, keep it off the open internet and watch its traffic for anything unusual.

What is network segmentation?

Dividing a network into separate zones with rules about what can cross between them. If one device is compromised, the attacker can't reach the rest of the network from it.

How is AI changing software security?

Finding a serious flaw used to take skilled people and months of manual review. AI tools speed that work up, which shortens the time between a flaw existing and someone using it.

How fast should security patches be installed?

Critical ones within days, once they've been tested, instead of waiting for a monthly cycle. The longer a known hole stays open, the more likely someone uses it.

Talk it through with us

Book a 30-minute exploratory call. We'll tell you where your environment stands and what we'd fix first. If we're not the right fit, we'll say so.

Book a call

Practical IT tips, by email

Short, practical IT and security tips for business owners, written by the team that runs our clients' IT.

Unsubscribe anytime.