Topic starter
10/07/2026 9:20 pm
TL;DR: Sixty percent of health systems cannot adequately protect unpatchable, agentless medical devices, while 40% say fear of clinical disruption blocks microsegmentation adoption and 78% rank breach or ransomware prevention as the top buying criterion, according to Elisity and HIMSS Market Insights. The data shows healthcare security teams are not short on intent, but on deployment models that preserve uptime while reducing lateral movement risk.
Editorial analysis by NHI Mgmt Group, based on content published by Elisity: “HIMSS 2026 Microsegmentation Survey on Healthcare”.
By the numbers:
- 60% of health systems cannot adequately protect unpatchable, agentless medical devices.
- 40% cite fear of clinical disruption as the top barrier to microsegmentation adoption.
- 78% rate proven breach and ransomware prevention as the most important decision criterion.
Key questions
Q: What fails when hospitals try to segment medical networks with legacy tools?
A: Legacy segmentation fails when it assumes hospitals can tolerate VLAN rework, ACL changes, and long maintenance windows.
Q: Why does clinical downtime fear increase lateral movement risk?
A: Because fear of disruption pushes teams toward inaction, flat networks remain in place and attackers can move more easily from one device to another.
Q: What are the signs that a microsegmentation programme is being delayed too long?
A: Common warning signs are repeated exceptions, persistent excess privilege, and teams treating segmentation as a future project instead of a current control gap.
Practitioner guidance
- Map unmanaged medical devices first Inventory IoMT, OT, and other agentless assets by location, communication pattern, and clinical criticality before designing segmentation policy.
- Simulate policy before enforcement Test segmentation rules against real traffic and clinical workflows before blocking any east-west paths, especially for devices that support patient care.
- Prioritise lateral movement containment Target the segments and device groups most likely to enable ransomware spread, rather than trying to redesign the whole hospital network at once.
Bottom line: Healthcare microsegmentation is trapped between two valid priorities, protecting clinical systems and avoiding operational disruption.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:43 pm
Microsegmentation in healthcare is now a clinical resilience problem, not just a network architecture choice. The article shows that hospitals are not deciding whether segmentation has value, but whether the deployment model can coexist with patient safety and uptime. That makes the control a governance issue across security, biomedical engineering, and operations. The practitioner takeaway is that segmentation programs must be judged by their ability to reduce lateral movement without disrupting care.
A few things that frame the scale:
- Only 36% of health IT leaders say their organisation applies a privileged access strategy consistently across the enterprise, according to Ponemon Institute research.
A question worth separating out:
Q: How should healthcare security teams balance patient safety and segmentation controls?
A: They should use a model that protects east-west traffic without changing clinical workflows, then phase enforcement through simulation and cross-functional approval. Patient safety and security are not opposing goals, but the control must be designed so it does not depend on shutting systems down to work.
👉 Read our full editorial: Healthcare microsegmentation faces an implementation paradox