Skip to main content
Segmentation & Zero Trust

Can’t patch it? Group it. Segmentation made easy for mission-critical devices

Device segmentation protects infusion pumps, imaging systems and PLCs regardless of patch status. Cut what each device can reach, and a new vulnerability has far less room to move.

November 20, 2026
4 min read

Vulnerabilities are being found faster than ever, and device segmentation is how you protect the devices that can’t keep up. The devices that matter most, like infusion pumps, imaging systems and PLCs, routinely lag on patching. Manufacturer schedules, validation and uptime requirements set the pace, not your team. So protect them regardless of patch status. Group each class of device, limit what it can reach, and a new vulnerability has far less room to move. 

How do you protect mission-critical devices regardless of patch status? 

Cut what each device can reach. A vulnerability is a weakness. Reachability makes it a weapon. Start with three steps. 

  1. Identify your mission-critical devices. Begin with the set that can’t stop: infusion pumps, imaging systems, PLCs, building controls. ORDR finds every connected device, including the ones that can’t run an agent. Full visibility takes 24 to 48 hours. 
  2. Group them by type and function. Policy follows the device, not its IP address. Every infusion pump follows the same rules. Every imaging system follows its own. It stays simple, so it holds up as devices move and change. 
  3. Enforce least-privilege policy on the infrastructure you already own. ORDR builds policy from observed traffic, simulates it against real flows, and pushes it to the switches, firewalls and NAC you already have. Every action is human-approved, and rollback takes under a minute (Emplify Health, ISE policy). 

What happens when a new vulnerability shows up? 

It lands on a device that can only talk to the few systems it needs. A flaw in that device is much harder to use. 

ORDR also confirms which vulnerabilities apply to a device’s actual model and patch level, and weighs exploitability (including EPSS and CISA KEV status) along with what the device does. So your team knows where to look first. When a new CVE or recall changes a device’s risk, its policy can tighten. It relaxes again once the device is fixed. 

Think of it as a shield. It reduces the risk while you wait. It doesn’t eliminate the flaw, and it doesn’t replace the patch. 

Why can’t these devices just be patched faster? 

Patching a laptop is routine. Patching a medical or OT device often isn’t. The manufacturer has to release the fix. Your team has to validate it. Then you need a maintenance window on equipment that has to keep running. Each step takes time, and none of them are yours to speed up. 

Discovery is speeding up. As of November 2, 2026, Anthropic had disclosed 5,087 vulnerabilities to open-source maintainers, and to its knowledge 629 had been patched (Anthropic, coordinated vulnerability disclosure dashboard, 2026 (opens in a new tab)). That’s industry context, not an ORDR result. 

Attackers move fast too. The average eCrime breakout time, from first access to lateral movement, was 29 minutes in 2025 (CrowdStrike 2026 Global Threat Report (opens in a new tab)). You can’t patch an infusion pump in 29 minutes. You can make sure an attacker can’t reach it. 

Does it work on devices that can’t be taken offline? 

Yes. ORDR enforces on the switches, firewalls and NAC you already own, so there’s no new enforcement hardware. Sensors read network data out of band, and nothing sits in line. 

Emplify Health (opens in a new tab) segmented unpatchable Windows 7 imaging workstations and kept them in service. They’re no longer reachable from outside or from most of the inside. A large children’s hospital operationalized Zero Trust across roughly 25,000 connected devices and contained a ransomware incident in under five minutes (ORDR, 2026 (opens in a new tab)). 

Where should you start with device segmentation? 

Start with the devices that can’t stop. Ask one question: if this device were compromised today, how far could an attacker reach? 

ORDR’s Mission-Critical Device Assessment, at no cost to you, shows what your mission-critical devices can reach today and where to start. ORDR gets you to first enforced policy in days, not years. Book your assessment. (opens in a new tab)

Frequently asked questions 

Can segmentation replace patching? No. Segmentation limits exposure while a patch is unavailable or can’t yet be safely deployed. Patch when the fix is ready. 

Which devices should we protect first? The ones that keep operations running and can’t be patched quickly, such as imaging systems, infusion pumps, and PLCs. 

Do we need new enforcement hardware? No. ORDR enforces on the switches, firewalls and NAC you already own. 

We protect your mission-critical devices. 

Sources 

  1. Anthropic's coordinated vulnerability disclosure dashboard (opens in a new tab), Anthropic, November 2, 2026 
  2. CrowdStrike 2026 Global Threat Report: The Evasive Adversary Wields AI (opens in a new tab), CrowdStrike, February 24, 2026 
  3. From Blind Spots to Control: How Emplify Health Used Device Visibility to Drive Network Segmentation (opens in a new tab), ORDR, June 13, 2025 
  4. ORDR and Cisco Deliver Agentic Zero Trust Segmentation at Enterprise Scale (opens in a new tab), ORDR, May 28, 2026 

Found this useful? Share it.