Agentless IoMT Protection
Medical device ransomware protection for systems that can't defend themselves
Connected medical devices are among the most exposed systems in any hospital and the hardest to protect. Immune secures them where they live, on the network, so infusion pumps, imaging controllers, and legacy clinical systems are covered even though they can't run a security agent.
Most security tools need an agent on the device. Medical devices usually can't run one. Immune closes that blind spot by protecting them at the network boundary and quarantining threats without ever shutting a device down.
Why medical devices are the soft underbelly of hospital security
Walk through any modern hospital and you are surrounded by computers that do not look like computers. Infusion pumps meter medication. Imaging systems capture and store scans. Patient monitors stream vital signs. Ventilators, dialysis machines, and dozens of other devices quietly run software and connect to the network. Collectively they are the Internet of Medical Things, and a single large hospital may operate ten to fifteen thousand of them. They are essential to care, and they are a security nightmare.
The problem is structural. These devices are built to be medical instruments first and network citizens second. Many run old or proprietary operating systems that were never designed to host security software. Research across millions of medical devices has found they carry an average of more than six known vulnerabilities each, that the majority of hospitals operate at least one device with a vulnerability attackers are actively exploiting, and that a large share of devices in active use are end-of-life. You cannot patch your way out of this, and you cannot install an agent on a device that will not accept one.
Attackers understand all of this. As endpoint protection has improved on laptops and servers, adversaries have shifted toward the systems that endpoint tools cannot see. Ransomware aimed at hospital connected devices has climbed sharply, because a compromised imaging system or a foothold on an unmonitored device gives an attacker a quiet place to hide and a bridge into the rest of the network.
See it in action
Every connected medical device is discovered on the network, then classified, risk-scored, and protected at the boundary without an agent.

IoMT security by the numbers
The medical-device risk, in figures
These figures come from independent research and government sources, not from us. They explain why medical device security has become one of the defining problems in healthcare.
The device catalogue
Every class of connected medical device, and why it matters
"Medical device" covers an enormous range of equipment, and each class carries its own risk. Here is the full landscape of the Internet of Medical Things, what each device does, why it is hard to secure, and what an attack on it means for patients.
Infusion & syringe pumps
What it is: Deliver medication, fluids, and chemotherapy at precise rates to a patient's bloodstream.
Why it is at risk: Among the most numerous connected devices in a hospital, often running old firmware with documented vulnerabilities. They cannot host an agent and must never be shut down mid-therapy, so they are a favorite entry and hiding point for attackers.
Imaging systems & PACS (MRI, CT, X-ray, ultrasound)
What it is: Capture diagnostic images and store them in Picture Archiving and Communication Systems that clinicians rely on for treatment decisions.
Why it is at risk: Claroty's research identifies imaging as the single highest-risk device category. A compromised or encrypted imaging system or PACS archive can halt diagnosis, force patient re-routing, and expose huge volumes of sensitive images.
Patient monitors & telemetry
What it is: Continuously track vital signs such as heart rate, blood pressure, and oxygen, often streaming to central nurse stations.
Why it is at risk: Availability is a direct patient-safety matter. Monitors run embedded operating systems that rarely accept security software, and a flood or disruption on the monitoring network can blind clinical staff.
Ventilators & life-support systems
What it is: Sustain breathing and vital functions for critically ill patients, increasingly networked for remote monitoring and configuration.
Why it is at risk: The highest-consequence devices of all. They cannot be taken offline to patch or contain, so any protection has to work without touching the device, at the network layer.
Dialysis machines
What it is: Perform renal-replacement therapy, networked for scheduling, monitoring, and record-keeping.
Why it is at risk: Long service lives mean many run unsupported software. Disruption delays life-sustaining treatment for vulnerable patients.
Laboratory & diagnostic analyzers
What it is: Process blood, tissue, and other samples and feed results into the electronic health record.
Why it is at risk: A compromise can corrupt or delay results, undermining trust in diagnostics. These systems often sit on flat networks with broad access to records.
Surgical robots & operating-theatre systems
What it is: Assist or perform procedures and run the integrated technology of a modern operating room.
Why it is at risk: Downtime cancels surgeries. Theatre integration systems connect many devices, so a single weak link can expose the whole room.
Implantable & wearable devices
What it is: Pacemakers, insulin pumps, and connected wearables that communicate wirelessly with clinical systems.
Why it is at risk: Research has repeatedly shown pacemakers and insulin pumps can be manipulated wirelessly. Rare in practice, but the potential for direct patient harm makes them a serious concern.
Legacy & end-of-life systems
What it is: Clinical systems kept in service for years past vendor support because replacing them is costly or disruptive.
Why it is at risk: Around 60% of medical devices are end-of-life with no patches available. They will never be fixed, so the only viable protection is at the network boundary around them.
Building & facility systems on the clinical network
What it is: HVAC, physical access, cameras, and other operational technology that shares the hospital network.
Why it is at risk: Often overlooked, frequently unmonitored, and a documented ransomware entry point. In one case an attacker launched encryption from an unsecured networked camera.
Features
What medical-device protection includes
A complete set of capabilities for securing the connected devices conventional tools can't reach.
Agentless coverage
Protects devices at the network boundary, with no software required on the device itself.
Per-device behavioral baseline
Learns the normal traffic pattern of each device so deviations are obvious.
Automatic device discovery
Finds and classifies connected devices on the network, including unmanaged ones.
Network quarantine, not shutdown
Isolates a compromised device's connectivity while keeping it powered and clinically functional.
IoMT-aware threat detection
Recognizes the abnormal behavior that signals a device is being used in an attack.
Legacy & end-of-life support
Protects unpatchable systems that will never receive another security update.
How it works
How Immune protects an agentless device
Discover and classify
Immune identifies every connected device on the network and classifies what it is, whether a pump, imaging system, monitor, or legacy system.
Baseline normal behavior
It learns each device's characteristic communication: which systems it talks to, on which protocols, and in what volume and timing.
Watch at the boundary
Every device's traffic is monitored continuously at the network boundary, where an attack on an agentless system becomes visible.
Detect the deviation
When a device reaches for systems it never touches, beacons to an unfamiliar destination, or moves toward the health record, Immune flags it as a high-priority threat.
Quarantine safely
On a confirmed threat, Immune isolates the device at the network layer, cutting the attacker off while leaving the device powered and safe for the patient.
Advantages
The advantages of protecting devices on the network
Closes the primary entry point
The agentless fleet is where many hospital attacks begin; covering it removes that opening.
Covers a huge share of the attack surface
Thousands of previously-invisible devices become monitored, not a rounding error.
Safe by design
Quarantine at the network layer never powers down a device a patient depends on.
No performance impact on devices
Protection happens off the device, so sensitive medical equipment is untouched.
Works with what you have
Complements endpoint tools and backups by covering the systems they structurally cannot.
A defensible differentiator
Agent-based competitors cannot match network-boundary protection for these devices.
Use cases
Where agentless protection matters most
Infusion pumps & bedside devices
Medication-delivery devices that cannot host software and must never be shut down.
Imaging & PACS archives
Diagnostic imaging systems and the archives that store scans — frequent ransomware targets.
Patient monitors & telemetry
Continuous vital-sign systems whose availability is a patient-safety matter.
Legacy & end-of-life systems
Unpatchable clinical systems that remain in service long past vendor support.
IoMT exposure management
From a wall of vulnerabilities to the few that actually matter
If 99% of hospitals have devices with known exploited vulnerabilities and the average device carries more than six flaws, a raw vulnerability list is useless. You cannot patch most of these devices, and you cannot act on tens of thousands of findings. IoMT exposure management is the discipline of cutting that noise down to the handful of devices that are genuinely dangerous: the ones that carry a known exploited vulnerability, are reachable by an attacker, and are tied to active ransomware campaigns. Claroty's 2025 research found that 89% of healthcare organizations have devices in that top 1% of risk, and those are the devices worth your attention.
Exposure management answers three questions in order. What connected devices do I actually have, including the ones nobody put on a list? Which of them are both vulnerable and exposed, rather than merely vulnerable? And what do I do about the ones I cannot patch? Most medical device security tools answer the first two well. The gap, and the reason exposure visibility alone has not stopped the attacks, is the third. A device you have identified as high-risk but cannot patch is still high-risk until something actively protects it.
That is where we differ from a pure exposure-management or asset-inventory product. We discover and risk-score every device like a good exposure tool does, but we also sit in the network path and defend the devices you cannot fix, baselining their behavior and quarantining them the moment they are used in an attack. Exposure management tells you where the risk is. We also take it off the board.
Buyer's guide
How to evaluate IoMT and medical device security companies
The medical device security market has grown crowded, and the products are not interchangeable. Most fall into a few categories, and it helps to know which problem each one actually solves before you compare them. Here is an honest map of the landscape and the questions that separate a tool that reports risk from one that reduces it.
The categories of medical device security tools
Asset discovery & inventory
Find and classify connected devices so you finally know what is on the network. Essential groundwork, but inventory on its own does not detect or stop an attack.
Exposure & vulnerability management
Layer risk scoring, known-exploited-vulnerability data, and prioritization on top of discovery. Strong at telling you where the danger is, but most stop at an alert and leave the response to you.
Microsegmentation & network control
Reduce the blast radius by restricting what devices can talk to. Valuable and complementary, though static segmentation is hard to maintain and does not catch an attack already inside an allowed path.
Agentless detection & response
Watch device behavior at the network layer and actively contain a threat, without software on the device. This is the category that closes the gap between knowing about risk and stopping it. It is where we focus.
Eight questions to ask any vendor
- Does it protect devices that cannot run an agent, or only the ones that can?
- Does it only report risk, or does it also actively contain a threat in progress?
- Is containment safe for patient care, meaning network quarantine rather than powering a device down?
- How accurately does it discover and classify devices, including unmanaged and legacy ones?
- Does it detect an attack by behavior, so it catches a device being misused even without a known signature?
- Does it focus on the small subset of devices that are vulnerable and exposed, not just a long raw list?
- Does it complement your EDR, backups, and existing segmentation rather than duplicating them?
- Can it run on-premises so sensitive device and patient data never leaves your environment?
Where we fit: many excellent companies do discovery and exposure management well, and we work alongside them. Our focus is the agentless detection-and-response layer that actually stops an attack on a device you cannot patch, and keeps it safely running while doing so.
Related reading: How to choose a medical device security company: a buyer's checklist for hospitals, a vendor-neutral walkthrough of the six criteria that separate a risk dashboard from real protection.
Why this is decisive
The blind spot other tools leave open
The leading endpoint and detection products are genuinely good, as long as you are talking about devices that can run their agent. Ask them to protect an infusion pump or a decade-old imaging controller, and they cannot, because there is nowhere to install the software. The industry openly acknowledges this: attackers go where agents cannot, and in a hospital that means the medical devices. Backup-centric tools have the same gap; they can help you recover data, but they do nothing to stop a device from being used as an attack path in the first place. Immune was designed from the start to cover exactly this territory. Protecting the systems that cannot protect themselves is a founding reason the platform exists.
Common questions
Medical device and IoMT security, answered
+What is IoMT security?
IoMT (Internet of Medical Things) security is the practice of protecting connected medical devices, such as infusion pumps, imaging systems, and patient monitors, from unauthorized access, manipulation, and disruption, while keeping them safely available for patient care. Because many of these devices cannot run security software, IoMT security is usually enforced at the network layer rather than on the device itself.
+What is IoMT exposure management?
IoMT exposure management is the continuous process of discovering every connected medical device, understanding which ones carry known exploited vulnerabilities or unsafe internet connections, prioritizing them by real risk, and reducing that exposure. Claroty's 2025 research found that 99% of healthcare organizations have devices affected by known exploited vulnerabilities, so exposure management is about focusing on the small subset of devices that are both vulnerable and reachable by an attacker. We pair exposure visibility with active protection, so a high-risk device is not just flagged but defended.
+What should I look for in IoMT security companies?
Evaluate IoMT and medical device security companies on five things: agentless coverage (can they protect devices that cannot run software), discovery and classification accuracy, whether they only report risk or also actively contain a threat, whether containment is safe for patient care (network quarantine rather than shutdown), and how they fit alongside your EDR and backups. Many vendors do visibility and exposure management well but stop at an alert. We focus on also stopping the attack and keeping the device safely running.
+How do you protect medical devices that can't run a security agent?
We protect agentless devices at the network boundary rather than on the device itself. We baseline each device's normal behavior, watch its traffic continuously, and on a confirmed threat we quarantine the device at the network layer so the attacker is cut off while the device stays powered and safe.
+Why can't EDR or antivirus protect medical devices?
Endpoint detection and antivirus require installing an agent on the device. Most medical devices run closed or unsupported operating systems that cannot host one, and a large share are end-of-life with no patches. Research has found that while around half of IoMT devices run Windows, only about 10% have active anti-malware protection. That leaves most devices invisible to endpoint tools, a blind spot attackers deliberately target.
+Does quarantining a device put patients at risk?
No. We quarantine at the network layer, which isolates the device's connectivity without powering it off or interrupting its clinical function. Any action that could affect care is gated behind human approval, so a clinician remains in control of the device itself.
+What kinds of devices can Immune protect?
Infusion pumps and bedside devices, imaging systems and PACS archives, patient monitors and telemetry, ventilators and life-support systems, dialysis machines, laboratory and diagnostic equipment, surgical robots and theatre systems, implantable and wearable devices, building and facility systems on the clinical network, and the legacy and end-of-life systems that remain in service long past vendor support.
+How does Immune know a device is behaving abnormally?
We learn a behavioral baseline for each device: the systems it talks to, the protocols it uses, and its normal volume and timing. Because medical-device behavior is highly predictable, deviations such as new destinations, beaconing, or attempts to reach the health record stand out clearly and quickly.
References
Sources and further reading
The statistics and incidents on this page are drawn from independent research and government sources. The primary references are listed below.
- 1.Claroty Team82: State of CPS Security, Healthcare Exposures 2025 (2.25M+ IoMT devices; 99% KEV-affected; 89% top-1% risk)
- 2.Claroty Team82: 63% of CISA-tracked KEVs found on healthcare networks
- 3.Ordr: Medical Device Breach Statistics 2026 (60% end-of-life; imaging highest risk; FBI 53%)
- 4.U.S. House E&C hearing: Aging Technology, Emerging Threats, Legacy Medical Devices (April 2025)
- 5.Help Net Security: CISOs, are your medical devices secure?
- 6.BleepingComputer: Ransomware gang encrypted a network from a webcam to bypass EDR
Figures were current as of publication and are presented for context. Content was rephrased for compliance with source licensing.
Explore the platform
Related capabilities
Cover the devices your current tools can't see
Book a demo and we'll show you how Immune protects agentless medical devices at the network boundary, and quarantines threats without ever disrupting patient care.
