St. Luke’s University Health Network deployed Elisity identity-based microsegmentation across 15 hospitals and 85,000 connected devices in 46 days, without new agents, hardware, or VLAN redesign. The team used existing Cisco switches as policy enforcement points, integrated with Armis for medical device discovery, and rolled out site-by-site after a one-time Virtual Edge install. Most health systems take 18 to 24 months with legacy approaches. Learn how Elisity microsegmentation works for healthcare.

Most medical devices, including infusion pumps, imaging systems, and surgical robots, can’t accept endpoint agents because of FDA validation constraints and clinical safety requirements. Elisity solves this with agentless identity-based microsegmentation: it ingests device telemetry from the network and from partners like Armis, builds a real-time identity for each device, then enforces least-privilege policy on the existing access switches. St. Luke’s protected 85,000 medical and IoT devices this way. See the Armis and Elisity integration.

Ransomware in hospitals causes catastrophic damage by spreading laterally between unprotected medical devices and clinical workstations. Elisity contains the blast radius by enforcing identity-based, least-privilege policies on every existing access switch, blocking unauthorized east-west traffic before encryption can spread. At St. Luke’s, this turned 15 hospitals from a single flat network into 85,000 individually contained policy zones. Read how identity-based microsegmentation stops lateral movement.

No. Elisity deploys in observation-only mode first, mapping every device-to-device communication before any policy is enforced. Security teams review and approve flows before turning on enforcement, so legitimate clinical traffic is never blocked unexpectedly. St. Luke’s brought 15 hospitals and 85,000 devices online in 46 days with zero clinical disruption, including imaging, infusion, and surgical robotics. See the Elisity microsegmentation deployment process.

Both the proposed 2026 HIPAA Security Rule update and HHS 405(d) HICP recommend network segmentation as a core safeguard. Elisity satisfies these by isolating ePHI systems, medical devices, and clinical workstations through identity-based policies enforced on existing infrastructure: no new hardware, no flat VLANs. Auditors get policy logs and traffic visibility per device. St. Luke’s used Elisity to align with both frameworks across 15 hospitals. Read the HHS 405(d) HICP segmentation guide.

Traditional microsegmentation projects in healthcare typically take 18 to 36 months. Identity-based microsegmentation deploys in weeks because it uses existing access switches as enforcement points and requires no agents on medical devices. St. Luke’s University Health Network went from contract signature to full enforcement across 15 hospitals and 85,000 devices in 46 days. See how identity-based microsegmentation accelerates Zero Trust.