Topic starter
10/07/2026 9:17 pm
TL;DR: Healthcare breach costs reached $7.42 million per incident for the 14th consecutive year, while stolen credentials stayed the top initial access vector and unpatchable medical devices kept widening exposure, according to Elisity’s recap of IBM, Verizon, and HIMSS findings. The governing assumption is no longer that entry can always be prevented, but that identity scope, segmentation, and lifecycle controls must limit how far an attacker can move once inside.
Editorial analysis by NHI Mgmt Group, based on content published by Elisity: “Reducing the Blast Radius: A Cybersecurity Summit Boston Recap”.
By the numbers:
- As covered in the recap, 60 percent of health systems say they cannot adequately protect the unpatchable, agentless medical devices already on their networks.
- The recap says 52 percent report they have no continuous monitoring for lateral movement or segmentation failures.
- The IBM Cost of a Data Breach Report 2025 put the global average breach cost at 4.44 million dollars.
Key questions
Q: What breaks when healthcare networks still rely on flat internal trust?
A: Flat internal trust fails when a stolen credential or compromised device can move laterally without crossing meaningful barriers.
Q: Why do legacy medical devices increase breach impact in hospitals?
A: Legacy devices often cannot support modern patching, strong authentication, or continuous monitoring, so they remain reachable long after vulnerabilities are known.
Q: How do security teams know if identity-based segmentation is actually working?
A: Teams should test whether a compromised or simulated compromised host can reach anything beyond the minimum required set of services.
Practitioner guidance
- Map blast-radius dependencies Identify which clinical systems, vendor pathways, service accounts, and AI agents can reach high-value assets if one identity is compromised.
- Segregate unpatchable medical devices Place legacy devices into dedicated network segments with explicit allow-lists, controlled administration paths, and monitoring that compensates for the lack of direct hardening options.
- Remove implicit vendor reach Force third-party access through controlled privileged gateways and disallow direct remote administration paths that bypass segmentation and accountability.
Bottom line: The article argues that healthcare security now has to be measured by how much an attacker can reach after entry, not only by whether entry is blocked.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
10/07/2026 9:40 pm
Blast-radius control is now the right governing objective for healthcare identity security: Perimeter success no longer tells you whether the environment can survive compromise. In hospitals, the hard problem is limiting what a stolen identity can reach after initial access, especially when legacy systems and vendor paths remain unavoidable. The implication is that identity governance has to be judged by containment, not just authentication rates.
A question worth separating out:
Q: Should organisations treat AI agents and service accounts differently in SaaS governance?
A: They should govern them with the same relationship-aware discipline but not the same assumptions. Service accounts usually have more stable ownership and scope, while AI agents can chain access across workflows and integrations in ways that change during execution. That means both need inventory, lifecycle control, and blast-radius analysis, but agent behaviour deserves closer runtime scrutiny.
👉 Read our full editorial: Reducing blast radius in healthcare identity and AI agent governance