February 21, 2025: This is the fourth episode in the Zero Trust Hospital Series. Tamer Baker, Healthcare CTO for Zscaler, dives into the myths surrounding zero trust implementation in healthcare settings. As healthcare systems grapple with digital transformation, what really stands between organizations and successful zero trust adoption? Through their discussion of real-world examples and strategic partnerships, they challenge conventional wisdom about vendor relationships and implementation timelines.
Want to get your copy of the new book "Zero Trust Hospital: The CXO Vision" by Zscaler?
Don't miss our webinar after all six Zero Trust Hospital Series episodes!
Key Points:
Donate: Alex’s Lemonade Stand: Foundation for Childhood Cancer
This transcription is provided by artificial intelligence. We believe in technology but understand that even the smartest robots can sometimes get speech recognition wrong.
[:
Welcome to This Week Health. Today, we are continuing a six part series on Zero Trust Hospital, the CXO Vision.
It's a new book by Zscaler. I have one of the authors, Tamer Baker. He's the healthcare CTO for Zscaler. He's with me today. I'm Drex DeFord, president of Cyber and Risk at This Week Health and the 229 Project. Welcome to the show, Tamer.
Thank you, Drex. Happy to be here. Excited to be here with you as usual.
This is a great time.
hang out with each other. So [:Thank you.
I'm happy to be here.
We are going to cover in this episode some of the common misconceptions about Zero Trust. We're going to do some Zero Trust myth busting. What do you think?
I love it. Yeah, it's one of my favorite topics in the book.
Yeah, let's just start , from the big perspective.
What's one of the biggest misconceptions about Zero Trust that healthcare leaders face? And how do you address them?
would say one of the biggest myths. There's a number of them that we cover in the book, of course. But one of the big things that immediately am drawn to is almost like you bring up the word zero trust, you can get the eye roll.
ls down to its It's actually [:There's been so much market texture out there and so much, FUD being put out about Zero Trust because of that huge explosion of that buzzword a few years ago and now we have to bust through all that FUD. There's other myths of course that are pretty major ones, like it's super disruptive in a health care environment.
So disrupts patient care. And the expense of it too is another piece of it that people think that zero trust is there are other myths in the book, but we don't want to spoil the whole book, but those I think would be pretty big, important myths to break, through.
So if you think about just starting with the beginning of that this is a long project.
ically stomping the crap out [:That's right. Hopefully I can say that. But zero trust is really built to still allow you to eat that elephant one bite at a time, even when it feels like on some days the elephant standing on top of you.
That's right. And not only standing on top of you, but dragging you with it as a stampeding, right?
That's what it is. absolutely can be done in that way. And part of what we talk about when we bust these myths is it's not disruptive. You can actually implement this in a good user experience fashion where your health care clinicians, for example, don't even know what's going on in the sense that everything actually gets better for them.
Examples, we have customers that I can talk about where we've got 50, 000 users at a health system that were able to deploy this in three weeks using an intern, right? So an intern obviously very quickly got a job as an engineer after that, but if you can deploy such a large health system in that short amount of time, it makes it viable, right?
t have to disrupt how you do [:And when you think about it. You start being able to phase out all these other pieces products and platforms that you may have already invested in as those things are, coming up for renewal. So it makes it easy to just turn those things on. And once you've deployed, let's say the agent as an example.
All you're doing is turning switches on, right? Say, yep, let's turn this feature on now and then start configuring it. We'll turn this feature on. We see how everybody's talking to everybody else. We see what applications are being accessed and then start narrowing it down from there. So you just flipping on switches, the quote unquote deployment part of it becomes drastically reduced because it's already deployed.
for zero trust. True, false. [:Yeah, one is a huge red flag. If you ever go to sell or have a meeting with somebody and they say, if you buy me, we'll get you zero trust, that should raise some significant red flags in your head.
There is no one single vendor solution for this. And if somebody's trying to tell you they can do it all, I would be very leery about that you don't want the fox gaurding, the hen house as an example, especially when that guarding the henhouse part is not very good at all the different pieces of Zero Trust.
It is a multi vendored approach. You're going to have to use multiple vendors. It is a way to do this where you narrow down from many different vendors in your ecosystem to just a handful of strategic vendors. And the beauty of this ecosystem of Zero Trust Is that handful of strategic vendors are all interconnected, right?
They're all partnered. They all work well together. They all work well for you as well. They're, everybody works as this ecosystem to make it happen in a really smooth and seamless way.
Yeah, I came from that [:Because of the specialty, the special things that they bring to that party is pretty incredible. Can you talk about that? Can you give any examples of that? The way that the partners in that whole Zero Trust ecosystem work together to make Zero Trust better?
Yeah, I'll give a couple of quick examples and we're actually about to launch a webinar too
with an ecosystem of partners talking specifically about this. A great example would be one that you're very familiar with, which is CrowdStrike. So when we are making these decisions, if these users are allowed to access something or not, we take into account, does CrowdStrike think that they're safe enough?
record. Maybe their score is [:We also do that intelligence sharing, the threat intel, right? Because CrowdStrike gathers a lot of threat intelligence and we gather a lot of threat intelligence. We actually share them by directionally. So they have when we discovered something brand new, CrowdStrike protects all their users with it to in both directions.
The other great pieces. I'll talk about the Improvata integration. We're Improvata's only certified cyber security partner right now. And it's a great use case because if you think about zero trust and security on a shared workstation today. Your users are tapping in and out of that shared workstation.
a nurse, they get a security [:So there's different personalized security policies that come into play as they tap in and out with our Improvata integration. So these are two very short examples of how we work well together to make sure the ecosystem works for you. And it's supercharged in both directions now to be able to empower your teams to do their jobs easier and your users are happier because it's all happening behind the scenes.
We talked about this in a previous episode, this sort of being able to scratch the itch of both these issues, making it easier for end users and helping them feel more comfortable that they are only allowed to do the right things and that they can't do the wrong thing from a security perspective and at the same time make operations better.
imilar examples for business [:We talked about a squeaky wheel before of remote radiologists as an example Institutions nowadays health systems have researchers bring in money, right?
They have to have the access that they need That you're not allowed to manage their systems. it's wild west when it comes to the research side of your house, right? Oftentimes you can't control a lot of it and you can't control other parts.
And sometimes it's the other way around. This is where again, zero trust helps. And this is part of the myth busting, right? Makes it seamless and easier and more cost effective. All these air myths that people think it's going to take a long time. You give researchers access to what they need, you give them, you host a web portal you give them a cloud browser where they don't even need to install an agent or browser or anything like that, and they have access to everything that they need, but they're coming in.
ve to mess with them, but as [:So that's another fantastic use case that we can talk through.
researchers are challenging. Health care in general is challenging. It's why the zero trust model is so appealing to me in a lot of ways.
Hey, thanks for being with me today, Tamer. I really appreciate it.
Thank you. This was a fun conversation as usual.
Thanks for tuning in to episode four of our Zero Trust series. You want to dive deeper? Don't miss your chance to get a signed copy of the book at HIMSS along with the other book in this series, which is called The Architect's Approach. That book is really more targeted at your team.
bunch more on this topic to [:Visit this week health. com slash zero trust and get your name in there again. Thanks Tamer. Glad you're here
Thank you tracks. Happy to be here