Zscaler Blog
Get the latest Zscaler blog updates in your inbox
Subscribe
The Zero Trust Hospital: A New Approach to Securing Healthcare
The healthcare industry is undergoing a major digital transformation. AI-assisted diagnostics, electronic health records (EHRs), telemedicine, and wearable health devices are revolutionizing patient care, improving efficiency, and enhancing the overall healthcare experience. Just take EHRs, for example—adoption has skyrocketed from 22% in 2009 to 78% in 2021 among U.S. office-based physicians. Meanwhile, telemedicine visits surged by 85.9% between 2019 and 2021, largely driven by the pandemic.
But with innovation comes risk, and in healthcare, cybersecurity risks are particularly high-stakes. The treasure trove of sensitive data held by hospitals—patient records, financial details, research data—is an absolute goldmine for cybercriminals. According to Trustwave, healthcare records can fetch up to $250 per record on the dark web—47 times more valuable than payment card information. That’s right, your credit card? Five bucks. Your full medical history? A small fortune.
The Rising Threat of Cyberattacks in Healthcare
Healthcare has become a full-blown battleground for cybercriminals, and 2024 has been one of the worst years yet. The numbers don’t lie—181 confirmed ransomware attacks hit healthcare providers, exposing a staggering 25.6 million patient records. And if that wasn’t bad enough, February brought us the largest healthcare data breach to date: the Change Healthcare attack. Hackers infiltrated the system, encrypted critical files, and made off with the protected health information of an estimated 100 million individuals. Let that sink in.
But this isn’t just about data theft. It’s about patient safety. A 2024 survey found that 36% of healthcare facilities reported increased medical complications due to ransomware attacks. When hospitals go offline, the fallout is immediate—appointments canceled, emergency services rerouted, and life-saving procedures delayed. In critical care, minutes matter. Cyberattacks don’t just disrupt operations; they endanger lives.
Let’s talk about money. The financial toll of these attacks is brutal. In 2024, the average ransom demand in healthcare hit $5.7 million, with organizations actually paying an average of $900,000 to get their systems back. But the real cost isn’t just the ransom—it’s the recovery. The average expense to bounce back from an attack climbed to $2.57 million, up from $2.2 million in 2023.
The takeaway? Cybersecurity in healthcare isn’t just an IT problem—it’s a patient care problem. Security architects have to strike the right balance: strong enough defenses to keep threats out but seamless enough that clinicians can still do their jobs. Because if security slows down patient care, it won’t be followed—and that’s a risk no one can afford.
Zero Trust: The Path Forward (But Not a Magic Fix)
When we set out to write The Zero Trust Hospital for the Architects, it wasn’t just because zero trust is the industry’s latest buzzword. It was because healthcare desperately needs guidance on how to make it work.
Zero trust in healthcare isn’t impossible, but it’s not as simple as flipping a switch. If you ask a hospital CIO, “Are you zero trust?”, you’ll get wildly different answers. The most common response I hear is:
“It’s really freaking hard to do zero trust in a clinical setting. Our clinicians won’t stand for anything that impacts their workflow. It could affect patient care!”
While I understand that perspective, it’s not entirely true. The real problem? Many just don’t know where to start. Before writing the book, I was at a healthcare event where a CIO described how their hospital responded to a ransomware attack.
Their solution? Turning off the internet. But first, they had to give the stroke unit a one-minute heads-up.
That moment floored me. Why wasn’t there a better plan to contain the blast radius? Why was the nuclear option—shutting everything down—the only available response?
That’s when I knew: hospitals need a practical, step-by-step guide to zero trust.
The Zero Trust Hospital: A Playbook for Healthcare Security
The Zero Trust Hospital: An Architect’s Guide isn’t a magical step-by-step manual that instantly makes your hospital zero trust overnight. Instead, it’s a jump start—a practical approach to moving healthcare organizations toward a more secure future. We cover:
- Least-privileged access, because too many people have too many permissions they don’t need.
- Microsegmentation to keep bad actors from spreading through your network like wildfire.
- Identity verification best practices, because stolen credentials are still the #1 attack vector.
- Sample policies and practical examples, because theory without execution is useless.
- A phased approach to implementation, because nobody goes from zero to fully zero trust overnight.
The challenge with zero trust is figuring out where to start and what’s actually achievable. Can you ever reach true zero trust by NIST standards? Technically, yes. Realistically? Probably not—especially with legacy applications and internet of medical things (IoMT) devices that simply can’t be fully locked down.
Security architects face a unique balancing act—protecting sensitive patient data while ensuring clinicians can still do their jobs effectively. It’s a daunting task, but here’s the thing:
In today’s digital healthcare world, it’s not a question of if you’ll be breached—it’s a question of when.
The best thing we can do is make those breaches as difficult, costly, and limited in scope as possible. That’s the goal of zero trust. Not perfection, but practical, achievable security improvements.
In the next post in our Zero Trust Hospital series, we’ll break down exactly where healthcare organizations should start their zero trust journey—starting with securing the workforce. Stay tuned.
Zero Trust Hospital eBooks
Get your free copies of the Zero Trust Hospital eBooks today by clicking here.
Was this post useful?
Get the latest Zscaler blog updates in your inbox

By submitting the form, you are agreeing to our privacy policy.