WEBVTT - Smart Talks with IBM: How AI Can Accelerate Cybersecurity 0:00:00.120 --> 0:00:02.880 Hey everyone, it's Robert and Joe here. Today we've got 0:00:02.880 --> 0:00:05.120 something a little different to share with you. It's a 0:00:05.160 --> 0:00:08.760 new season of the Smart Talks with IBM podcast series. 0:00:09.240 --> 0:00:12.040 This season, on smart Talks, Malcolm Gladwell and team are 0:00:12.080 --> 0:00:15.280 diving into the transformative world of artificial intelligence with a 0:00:15.320 --> 0:00:18.640 fresh perspective on the concept of open What does open 0:00:18.720 --> 0:00:21.919 really mean in the context of AI. It can mean 0:00:22.040 --> 0:00:25.639 open source code or open data, but it also encompasses 0:00:25.720 --> 0:00:30.800 fostering an ecosystem of ideas, ensuring diverse perspectives are heard, 0:00:31.160 --> 0:00:33.559 and enabling new levels of transparency. 0:00:33.880 --> 0:00:37.120 Join hosts from your favorite pushkin podcasts as they explore 0:00:37.120 --> 0:00:40.960 how openness in AI is reshaping industries, driving innovation, and 0:00:41.000 --> 0:00:44.880 redefining what's possible. You'll hear from industry experts and leaders 0:00:44.880 --> 0:00:48.360 about the implication and possibilities of open AI, and of course, 0:00:48.720 --> 0:00:50.920 Malcolm Gladwell will be there to guide you through the 0:00:50.960 --> 0:00:52.720 season with his unique insights. 0:00:53.000 --> 0:00:55.560 Look out for new episodes of Smart Talks every other 0:00:55.640 --> 0:00:59.200 week on the iHeartRadio app, Apple Podcasts, or wherever you 0:00:59.240 --> 0:01:02.520 get your podcast and learn more at IBM dot com 0:01:02.560 --> 0:01:04.280 slash smart Talks. 0:01:07.120 --> 0:01:10.479 Hello, Hello, Welcome to smart Talks with IBM, a podcast 0:01:10.480 --> 0:01:16.920 from Pushkin Industries, iHeartRadio and IBM. I'm Malcolm Glappwell. This season, 0:01:17.120 --> 0:01:20.039 we're diving back into the world of artificial intelligence, but 0:01:20.120 --> 0:01:26.560 with a focus on the powerful concept of open its possibilities, implications, 0:01:26.840 --> 0:01:30.320 and misconceptions. We'll look at openness from a variety of 0:01:30.400 --> 0:01:34.559 angles and explore how the concept is already reshaping industries, 0:01:35.000 --> 0:01:38.759 ways of doing business and our very notion of what's possible. 0:01:39.880 --> 0:01:43.000 On today's episode, I'm joined by Jason Kelly, the global 0:01:43.040 --> 0:01:47.240 Managing Partner for IBM Strategic Partners and Ecosystems, and by 0:01:47.360 --> 0:01:51.720 Christy Fredericks, the Senior Vice President and Chief Partnership Officer 0:01:52.040 --> 0:01:56.560 at Palo Alto Networks. We discussed how their partnership in 0:01:56.600 --> 0:02:01.760 the cybersecurity space helps strengthen enterprises by focusing on seamless 0:02:01.880 --> 0:02:07.440 cybersecurity solutions tailored to meet the evolving threat landscape. By 0:02:07.520 --> 0:02:12.560 leveraging AI and automation, this collaboration aims to modernize security programs, 0:02:12.960 --> 0:02:17.959 improve response times, and produce risks. Jason and Christie both 0:02:18.000 --> 0:02:22.280 bring a tremendous amount of experience and expertise to the subject. 0:02:23.400 --> 0:02:38.040 I think you're really going to enjoy this one. Jason Christy, 0:02:38.160 --> 0:02:41.240 Welcome to Smart Talks with IBM. Thank you for joining me. 0:02:41.520 --> 0:02:42.919 Thank you, it's great to be here. 0:02:43.240 --> 0:02:46.720 We are here to discuss cybersecurity and the partnership between 0:02:46.760 --> 0:02:50.000 IBM and Polo Alter Networks. But before we get there, 0:02:50.240 --> 0:02:51.919 I wanted you guys to tell me a little bit 0:02:52.480 --> 0:02:57.200 about yourself. Jason's start with you. I see on your 0:02:57.840 --> 0:03:01.760 resume west Point, which makes we think there's some interesting 0:03:01.800 --> 0:03:04.799 things going on there. How did you get to west Point? 0:03:05.400 --> 0:03:07.880 West Point? West Point was the decision. First, it was 0:03:07.919 --> 0:03:11.000 it was affordable back in the day. But I had 0:03:11.040 --> 0:03:12.880 a sense of service. My father was a World War 0:03:12.919 --> 0:03:15.920 Two vet, so I grew up on the weekends watching 0:03:16.000 --> 0:03:19.920 World War two video. You know he's army as well. Yeah, 0:03:20.000 --> 0:03:24.520 and so I thought, oh, that'd be exciting, and I 0:03:24.520 --> 0:03:27.800 thought I do some type of service. Went there and 0:03:27.840 --> 0:03:30.560 now I have the biggest family, extended family I could 0:03:30.560 --> 0:03:33.920 ever have. So it was very exciting. Played football lucked out, 0:03:34.760 --> 0:03:40.240 meaning I wasn't recruited. I walked on and that kept 0:03:40.280 --> 0:03:42.160 me there because it gave me something and out left 0:03:42.240 --> 0:03:45.440 with all the other pressures that a defensive back I was. 0:03:45.480 --> 0:03:47.560 I was great at knocking the ball down, not the 0:03:47.560 --> 0:03:48.360 best at catching it. 0:03:48.480 --> 0:03:51.720 Yeah, and then you were a ranger. 0:03:52.640 --> 0:03:55.040 I was. I was privileged to be a US Army 0:03:55.040 --> 0:03:58.240 airborne ranger station, but did most of my time in 0:03:58.280 --> 0:04:01.320 northern Italy. Were part of the It's eighty second. 0:04:01.200 --> 0:04:02.240 Air barnship post. 0:04:02.320 --> 0:04:05.080 Oh yeah, that's what people say, seriously, like, you know, 0:04:05.160 --> 0:04:07.840 you were you were nor You're drinking wine and having 0:04:07.880 --> 0:04:10.880 bred you know. But it was a part of a 0:04:11.080 --> 0:04:14.680 NATO force there at the time. Yeah, so exciting. 0:04:14.880 --> 0:04:18.560 How did you get from there to IBM? 0:04:19.040 --> 0:04:21.560 A long path. As I came out of the military, 0:04:21.800 --> 0:04:29.440 I started manufacturing retail housing and did a quick stint, 0:04:29.480 --> 0:04:33.520 took a leave of absence from industry, and did a 0:04:33.720 --> 0:04:36.839 stint of yet again public service in the state of 0:04:36.880 --> 0:04:41.479 Tennessee with economic development, and got a whiff of how 0:04:41.520 --> 0:04:45.000 fun it could be to do things around data and media. 0:04:45.320 --> 0:04:48.280 Started a small media firm what we would now call 0:04:48.279 --> 0:04:52.640 a digital firm, sold it and said I wanted to 0:04:52.640 --> 0:04:55.039 go do it again somewhere, but I wanted to go 0:04:55.080 --> 0:04:57.719 to a big company. And the family at IBM brought 0:04:57.760 --> 0:04:59.880 me in and yet to let me go. 0:05:00.120 --> 0:05:01.280 That was how many years ago? 0:05:03.120 --> 0:05:03.799 Two decades? 0:05:03.960 --> 0:05:04.360 Oh wow? 0:05:04.760 --> 0:05:07.200 Yeah, so, I know I look amazingly young on but yes, 0:05:10.240 --> 0:05:13.719 IBM was my fifth career and and and I've enjoyed 0:05:13.720 --> 0:05:15.440 a since. And that's what I what I do. They 0:05:15.680 --> 0:05:18.560 build teams, grow new parts of the company and get 0:05:18.600 --> 0:05:21.200 to work with some of the most brilliant people on 0:05:21.200 --> 0:05:23.640 the face of the planet, as well as partners like 0:05:23.920 --> 0:05:26.080 like Christy that just keep it exciting. 0:05:26.440 --> 0:05:29.000 Christy, you're I was delighted to learn that you are Canadian. 0:05:29.080 --> 0:05:34.800 Yes here, Yeah, but you so you were a consultant 0:05:34.839 --> 0:05:36.240 for a long time at Bane. 0:05:36.560 --> 0:05:39.800 Yes. Yeah. I joined Bain Consulting intending to spend a 0:05:39.839 --> 0:05:41.920 couple of years there learn the ropes and then go 0:05:41.960 --> 0:05:45.479 get my first real job. But the value personally to 0:05:45.520 --> 0:05:47.560 my growth and development, and then that we were able 0:05:47.560 --> 0:05:50.119 to bring our clients. I ended up there for sixteen years, 0:05:50.680 --> 0:05:54.239 and then post Bain went on to another my first 0:05:54.240 --> 0:05:57.039 product company, a new relic, and then it's come full 0:05:57.040 --> 0:06:00.440 circle at Polluta Networks. But at Bain it was all 0:06:00.480 --> 0:06:03.920 about bringing expertise across different industries to help our clients 0:06:04.160 --> 0:06:07.719 improve whatever they needed to improve and bringing that expertise 0:06:07.800 --> 0:06:10.200 to bear. And then you have the product lens and 0:06:10.200 --> 0:06:11.960 you think Okay, we're going to build the absolute best 0:06:12.000 --> 0:06:14.560 product to help our customers do what they need to 0:06:14.600 --> 0:06:17.360 get done. And then I joined pal Alto about six 0:06:17.400 --> 0:06:21.480 seven months ago in a partnerships role and I'm delighted 0:06:21.520 --> 0:06:23.840 to be able to work with amazing consulting companies like 0:06:23.880 --> 0:06:25.800 IBM where we bring both to bear. 0:06:26.320 --> 0:06:29.480 How long have IBM and Polo Alto Network's been partners? 0:06:30.080 --> 0:06:33.000 So we've been We've been working together for quite quite 0:06:33.040 --> 0:06:36.520 a long time. But we made it official, meaning we 0:06:36.839 --> 0:06:39.000 got married as strategic partners last year. 0:06:39.160 --> 0:06:41.159 Oh I see. So what is it that each of 0:06:41.240 --> 0:06:44.320 you bring to the table? What's each side special? 0:06:44.480 --> 0:06:47.359 So it's great that you asked that because about a 0:06:47.400 --> 0:06:51.320 decade ago, are now CEO Arvin Christ says, you know, 0:06:51.320 --> 0:06:53.920 it wouldn't be great if we just had this one 0:06:53.960 --> 0:06:56.479 focus with this what does IBM do? And you have 0:06:56.560 --> 0:06:58.880 this whole list, and he says, let's make it simple. 0:06:59.440 --> 0:07:04.200 We are a multi cloud, hybrid cloud AI company. And 0:07:04.240 --> 0:07:06.599 so when you say that, it sounds very simple, but 0:07:06.640 --> 0:07:10.600 then people, what the hell is that? What your hybrid cloud? Well, 0:07:11.280 --> 0:07:13.720 both of those two things have a lot of data involved, 0:07:13.960 --> 0:07:16.520 and a lot of those mean that that data is 0:07:16.520 --> 0:07:20.480 going to sit in multiple places and distributed environments. Well, 0:07:20.480 --> 0:07:23.840 if you're able to tie those things together with multiple partners, 0:07:24.200 --> 0:07:28.280 you also have to make sure that it's secure because 0:07:28.720 --> 0:07:31.880 in the direction that we're going, where data is now 0:07:32.160 --> 0:07:34.640 being consumed in many different places and it is the 0:07:34.640 --> 0:07:39.120 fuel behind AI as we know, then you say, ah, well, 0:07:39.640 --> 0:07:42.120 who does that well and who does it in a 0:07:42.120 --> 0:07:44.960 way that's getting rid of seams, the seams that could 0:07:44.960 --> 0:07:49.000 be across multiple products, multiple product SATs even And that's 0:07:49.000 --> 0:07:49.960 where Powell comes in. 0:07:50.840 --> 0:07:54.560 I think the conventional wisdom and cybersecurity was always you 0:07:54.640 --> 0:07:58.040 need all the new tools, right, you need it every threat. 0:07:58.040 --> 0:07:59.760 It's like, whack them all. Every threat that pops up, 0:07:59.800 --> 0:08:03.360 you get the tool that's purpose built for that specific thing. Well, 0:08:03.360 --> 0:08:06.320 fast forward to the RSA conference this year. There were 0:08:06.600 --> 0:08:09.760 four thousand vendors on the floor. You look at an 0:08:09.760 --> 0:08:13.800 average company, there's hundreds of cybersecurity tools. It introduces a 0:08:13.880 --> 0:08:17.760 level of complexity that is really hard to manage you 0:08:18.000 --> 0:08:23.240 as a user, query and application, right, that query can 0:08:23.280 --> 0:08:26.880 go through a bunch of different pings from one cloud 0:08:26.880 --> 0:08:29.160 to the next, It goes into and out of assaas application, 0:08:29.240 --> 0:08:31.679 it maybe running along a network. You may be accessing 0:08:31.720 --> 0:08:34.560 it from your phone, which is an unmanaged device. It's 0:08:34.559 --> 0:08:36.679 got to go in and out. And if you say, okay, 0:08:36.880 --> 0:08:39.640 I've got to secure that phone, I've got to secure 0:08:39.679 --> 0:08:41.560 the network. I've got it, then all of a sudden, 0:08:41.600 --> 0:08:45.240 you've got sort of firewalls, software and hardwelfowles popping up everywhere. 0:08:45.480 --> 0:08:48.400 You've got cloud security, and it's you've probably heard of 0:08:48.400 --> 0:08:50.400 this concept of zero trust, which is every time you 0:08:50.400 --> 0:08:51.920 have to check and say are you allowed in here? 0:08:51.960 --> 0:08:54.120 Are you allowed in here? The number of places that 0:08:54.160 --> 0:08:56.840 can fall down it just becomes overwhelming. So you end 0:08:56.960 --> 0:09:02.360 up with either alerts firing every two seconds that you 0:09:02.360 --> 0:09:04.120 have to then go investigate in most of which are 0:09:04.559 --> 0:09:08.679 false positives or you miss something right. And so that 0:09:08.760 --> 0:09:11.000 was the conventionalism was we've got to buy all these tools, 0:09:11.040 --> 0:09:13.960 and now you've got overwhelmed CIOs and CSOs with hundreds 0:09:13.960 --> 0:09:17.439 of tools, and Palo Alto strategy has been, look, we're 0:09:17.480 --> 0:09:20.280 going to create a platform where everything can be stitched together, 0:09:20.400 --> 0:09:24.240 everything can speak the same language, and we can sort 0:09:24.240 --> 0:09:28.560 of manage throughout the architecture and watch this call as 0:09:28.640 --> 0:09:32.760 as it's passing through all these different checkpoints, and we 0:09:32.760 --> 0:09:34.280 can do it in a way that you still have 0:09:34.320 --> 0:09:36.280 the confidence that it's best to breed right, so you're 0:09:36.280 --> 0:09:39.160 not making any trade offs. But it's not so simple 0:09:39.559 --> 0:09:43.040 just to get from the spaghetti to the seamless architecture. 0:09:43.080 --> 0:09:46.600 You need, oftentimes to re engineer your business processes. You 0:09:46.679 --> 0:09:49.839 have to re architect your digital environment. And so that's 0:09:49.880 --> 0:09:52.720 where we partner with a company like IBM to bring 0:09:52.760 --> 0:09:54.920 that expertise and say we're going to help you not 0:09:55.040 --> 0:09:57.920 just deploy the best cybersecurity architecture, but really get your 0:09:58.040 --> 0:10:00.760 environment ready to have this ar as. 0:10:00.600 --> 0:10:04.160 Well as all of those players that cross that spaghetti. 0:10:04.840 --> 0:10:07.560 Because when you start thinking about all the other partners 0:10:07.559 --> 0:10:09.480 that you work with, if you're you think of an 0:10:09.520 --> 0:10:12.480 industry perspective, you're gonna have an e ERP. It could 0:10:12.520 --> 0:10:15.200 be an Oracle, it could be an SAP. You're not 0:10:15.240 --> 0:10:16.840 going to have one cloud, as I mentioned, it's gonna 0:10:16.840 --> 0:10:20.960 be possibly multiple clouds. You'll have some aws maybe Microsoft 0:10:21.040 --> 0:10:23.360 Azure and then even even some Google in there, and 0:10:23.360 --> 0:10:26.440 then your own that you've built in your private over there, uh, 0:10:27.360 --> 0:10:31.360 some an IBM cloud. You'll have those multiple clouds, and 0:10:31.400 --> 0:10:34.520 then you also will have you know, fit for purpose Oh, well, 0:10:34.559 --> 0:10:37.120 I need a I need a salesforce in there for 0:10:37.520 --> 0:10:40.000 my customer focusing. I need I'm doing some graphics, so 0:10:40.040 --> 0:10:42.280 I have Adobe. So I just as I can name 0:10:42.400 --> 0:10:47.480 name name, all of those then have to be re engineered. Seriously. 0:10:48.080 --> 0:10:49.840 I mean, come on, Malcolm, You're gonna sit there. You 0:10:49.880 --> 0:10:52.920 think how long that would take. So if you haven't 0:10:52.960 --> 0:10:56.240 done that before, you're gonna have to go to each 0:10:56.280 --> 0:10:58.600 one of those individually, or you can work with a 0:10:58.640 --> 0:11:01.280 company that can tie those things together, because we are 0:11:01.320 --> 0:11:05.040 also strategic partners with them. So that's where you start 0:11:05.040 --> 0:11:09.280 to say, Okay, I see how this comes together. You 0:11:09.480 --> 0:11:12.800 have to make sure that your ecosystem is going to 0:11:12.800 --> 0:11:15.640 be stronger than your competitor's ecosystem, and you have to 0:11:15.679 --> 0:11:18.280 be secure in what you're doing because as you add 0:11:18.320 --> 0:11:21.800 more players or products, you create seams, and you want 0:11:21.840 --> 0:11:25.160 to make sure there's fewer seams and that there's zero 0:11:25.240 --> 0:11:29.880 trust across that capability you're building. And that's why the 0:11:29.920 --> 0:11:31.880 compliment between the two companies. 0:11:31.559 --> 0:11:33.600 Well, take a step back from a moment before we 0:11:33.720 --> 0:11:36.440 sort of launch, once get into the specifics of what 0:11:36.559 --> 0:11:40.400 you guys are doing. I'm curious at this moment in 0:11:40.520 --> 0:11:46.880 twenty twenty four. How nervous should we be about cybersecurity? 0:11:47.040 --> 0:11:51.240 So compared it to five years ago or ten years ago, 0:11:51.760 --> 0:11:53.760 are we are you less nervous than you were five 0:11:53.840 --> 0:11:56.480 years ago or more nervous or all of changes going 0:11:56.520 --> 0:12:00.920 on right now increasing vulnerability or decreasing it? 0:12:01.360 --> 0:12:04.840 I would say Christie, also, I think we share the 0:12:04.880 --> 0:12:09.000 point of view is that it's not necessarily being more nervous. 0:12:09.040 --> 0:12:13.559 I think you should be more prepared because the amounts 0:12:14.040 --> 0:12:18.400 of threat is increasing based on our dependence upon data. 0:12:19.480 --> 0:12:23.680 And that's that's where I think the attention should be placed. 0:12:23.800 --> 0:12:27.240 Is that more and more, especially with the importance of AI, 0:12:28.360 --> 0:12:31.080 that you say, okay, then what's under all that? And 0:12:31.120 --> 0:12:35.840 it's the data? As I said, So knowing that you 0:12:35.880 --> 0:12:37.480 should be more concerned. 0:12:38.400 --> 0:12:42.400 Does the advent of AI and its rapid evolution help 0:12:42.520 --> 0:12:44.320 defense more or offense more? 0:12:44.840 --> 0:12:47.760 I think it's I think it's like any mega trend 0:12:47.760 --> 0:12:51.760 that we've witnessed both. Right, So you think about AI, 0:12:51.920 --> 0:12:55.800 it's it's ninety nine percent great, right in terms of 0:12:55.840 --> 0:12:58.840 what it's going to unlock for productivity, for humanity, But 0:12:59.000 --> 0:13:01.080 it also makes it a whole lot easier to build 0:13:01.160 --> 0:13:04.160 ransomware it's a whole lot easier to test different ways 0:13:04.640 --> 0:13:07.240 into a system, right. But I think that's true if 0:13:07.280 --> 0:13:09.080 you think about like the rise of the Internet, right, 0:13:09.080 --> 0:13:11.800 all of a sudden, everyone was putting their data online 0:13:12.559 --> 0:13:14.800 and you had to think of new ways to stay 0:13:14.840 --> 0:13:16.640 ahead and keep that secure. And I don't think AI 0:13:16.720 --> 0:13:20.240 is any different. You've got companies like Palta, partnerships like 0:13:20.240 --> 0:13:25.600 Powell and IBM that are constantly scanning the landscape for 0:13:25.640 --> 0:13:28.000 not only the current threats, but what's next, what's coming 0:13:28.040 --> 0:13:30.640 around the corner, what's after AI? And so I think 0:13:30.880 --> 0:13:33.200 taking it seriously and being prepared is probably the right 0:13:33.280 --> 0:13:35.800 way of looking at it as opposed to because if 0:13:35.800 --> 0:13:38.280 you think about it too hard, you'll just want to 0:13:38.320 --> 0:13:42.520 crawl into a corner and stuff everything under the mattress. 0:13:42.880 --> 0:13:50.080 I am the CEO of a regional hospital chain, big 0:13:50.280 --> 0:13:55.319 distribute healthcare system, so a ton of data. The consequences 0:13:55.320 --> 0:13:58.079 of being hacked and help for ransom. 0:13:57.720 --> 0:13:59.240 Are life and death. 0:13:59.400 --> 0:14:03.000 Life and death, right, little when you come So you 0:14:03.440 --> 0:14:05.360 come down, you sit down with me, and you chat 0:14:05.400 --> 0:14:08.880 with me, walk me through the kinds of things you 0:14:08.880 --> 0:14:11.480 would tell me about what I need to get safer. 0:14:11.800 --> 0:14:15.000 For example, let's start with one. Is it likely that 0:14:15.040 --> 0:14:16.920 I'm spending too little or am I spending money in 0:14:16.960 --> 0:14:17.640 the wrong place? 0:14:18.520 --> 0:14:22.600 Great question, It depends how you've broken it out. If 0:14:22.640 --> 0:14:25.760 you are distributing all of your dollars across a whole 0:14:25.760 --> 0:14:28.360 bunch of different tools, it's likely you're just spending the 0:14:28.360 --> 0:14:30.640 wrong money. And in fact, you know, putting it all 0:14:30.640 --> 0:14:33.440 in one place is a way of potentially saving money 0:14:33.760 --> 0:14:37.640 but keeping your security actually higher. And I'd love to 0:14:37.640 --> 0:14:39.480 hear Jason, how you would approach it. How we would 0:14:39.480 --> 0:14:41.680 approach it, of course, is by saying, you know, what, 0:14:41.680 --> 0:14:44.800 what does your environment look like? You know, do you 0:14:44.840 --> 0:14:49.320 have the connected medical devices into your EMR? Are your 0:14:49.440 --> 0:14:52.960 respirators and ventilators all online? Right? And so we would 0:14:52.960 --> 0:14:55.800 talk about, okay, here's how you get coverage, and how 0:14:55.840 --> 0:14:58.360 the coverage of both the firewalls as well as the 0:14:58.440 --> 0:15:01.720 detectors all feed back into your security operations center and 0:15:01.760 --> 0:15:04.480 you can manage it and do your learning with AI 0:15:05.520 --> 0:15:06.560 and keep yourself secure. 0:15:06.560 --> 0:15:08.680 And so yeah, and I would say Christy and I 0:15:08.720 --> 0:15:11.080 would go to the same point because if you get 0:15:11.160 --> 0:15:14.480 under what she was just asking, it is your data 0:15:15.080 --> 0:15:19.360 on prem and when it's on prem how active is 0:15:19.400 --> 0:15:23.600 it across the enterprise? And so that begins the basis 0:15:23.600 --> 0:15:25.640 for the start. And then often you're going to say, well, 0:15:25.680 --> 0:15:28.840 we actually take in data from outside and then we 0:15:28.880 --> 0:15:32.400 also have the circumstances. There's a lot of PII and 0:15:32.440 --> 0:15:37.680 so that personal is the personal information, right, Yeah, And 0:15:37.760 --> 0:15:41.000 so now you're saying, okay, now how are we securing 0:15:41.080 --> 0:15:43.920 that and where are we securing it? And so you 0:15:43.960 --> 0:15:47.800 have to start really thinking about the different areas within 0:15:48.120 --> 0:15:52.200 that hospital chain. Are you sharing that amongst your hospitals? 0:15:52.760 --> 0:15:55.880 And now you start to think of if I'm saying 0:15:55.960 --> 0:15:57.400 no to a lot of that, it's like, well, then 0:15:57.440 --> 0:16:00.120 are you as efficient as you want to be? So 0:16:00.160 --> 0:16:03.640 there is that trade off of you know, am I 0:16:03.680 --> 0:16:07.240 so tightly walled that I'm not productive? And so that's 0:16:07.280 --> 0:16:10.400 where we would start to say what's the outcome that 0:16:10.400 --> 0:16:12.560 you're trying to get to? All Right, maybe you're good, 0:16:12.600 --> 0:16:14.960 Maybe you're you're good with your five locations and you 0:16:14.960 --> 0:16:17.480 don't need to go any further, but maybe you want 0:16:17.520 --> 0:16:19.520 to expand to fifty and by the way, you're going 0:16:19.600 --> 0:16:21.680 to go crossporder, you're going to be in Toronto and 0:16:21.800 --> 0:16:25.080 in New York. Okay, Well, then how do you do that? 0:16:25.960 --> 0:16:28.640 And so I think that it's very easy to start 0:16:28.720 --> 0:16:34.160 jumping into any of the typical situations. But the first 0:16:34.280 --> 0:16:38.560 question that you have to ask you, as the hospital CEOs, 0:16:39.040 --> 0:16:42.360 what's your objective? Are? What are you trying to do? 0:16:42.400 --> 0:16:45.960 Because too often what we see is that there's some bright, new, 0:16:45.960 --> 0:16:49.840 shiny thing that everybody wants to put in play. You know, 0:16:49.880 --> 0:16:53.280 it's a sandwich looking for lunch and you go, but 0:16:53.360 --> 0:16:54.960 what is it that you want to do as this? 0:16:55.560 --> 0:16:58.120 Are you doing research? Are your research hospital? Are you 0:16:58.200 --> 0:17:01.400 more consumer wriented? So those are the questions you start 0:17:01.440 --> 0:17:03.880 to ask because they start to then tell a story 0:17:04.400 --> 0:17:07.640 in line with what Christy questions. And I think that 0:17:07.640 --> 0:17:11.080 that's where the again the compliment is that instead of 0:17:11.160 --> 0:17:14.000 just saying, oh, well, that's thanks for telling me all this, Malcolm, 0:17:14.040 --> 0:17:18.680 here's your ten page strategy. Now go find somebody. We 0:17:18.760 --> 0:17:22.080 have the benefit in IBM, and it's probably why I'm 0:17:22.080 --> 0:17:24.440 still there is you know, we're very unique. We're the 0:17:24.480 --> 0:17:28.640 only company on the planet that has a consulting business 0:17:28.920 --> 0:17:32.920 at scale inside of a technology company, and so we have, 0:17:33.760 --> 0:17:36.000 you know, the left brain, right brain, We're able to 0:17:36.040 --> 0:17:38.240 do that. And then we're able to say, okay, now 0:17:38.240 --> 0:17:42.640 which partners are going to be most valuable for our clients. 0:17:43.080 --> 0:17:44.680 What's going to work for you? Isn't going to work 0:17:44.720 --> 0:17:47.040 for the manufacturer down the road, isn't going to work 0:17:47.040 --> 0:17:51.879 for the consumer or CpG company across the river. Those 0:17:51.920 --> 0:17:55.720 things are very specific. The threats and the scenes that 0:17:55.760 --> 0:17:59.040 I was talking about are very specific. So that's where 0:17:59.080 --> 0:18:02.359 it becomes very value to make sure that I'm not 0:18:02.440 --> 0:18:05.480 just giving you some strategy that's generic. 0:18:05.560 --> 0:18:10.280 But everything. As a healthcare CEO, everything I have done, 0:18:10.800 --> 0:18:14.120 almost everything I've done over the last ten years, has 0:18:14.240 --> 0:18:16.800 it had the effect of increasing my vulnerability. I want 0:18:16.840 --> 0:18:19.600 to digitize data within the hospital used to be on 0:18:19.640 --> 0:18:23.200 pieces of paper. I want doctors to go home and 0:18:23.320 --> 0:18:25.280 to be able to seamlessly hook into stuff at work 0:18:25.320 --> 0:18:27.840 because they got to do all their paperwork. I want 0:18:27.840 --> 0:18:30.520 to make sure the diabetes people are speaking to the 0:18:30.640 --> 0:18:34.240 organ transplant people. And so I'm isn't that everything I 0:18:34.280 --> 0:18:36.920 have done to kind of keep up with the revolution 0:18:37.040 --> 0:18:39.760 in healthcare? Isn't that also making me more and more 0:18:39.840 --> 0:18:41.639 vulnerable to a bad actor. 0:18:41.760 --> 0:18:44.120 It's such a great question because think about the quality 0:18:44.119 --> 0:18:47.560 of healthcare delivery, right, So now doctors aren't filling out forms, 0:18:47.560 --> 0:18:50.320 they're spending time with patients, and so the quality of 0:18:50.320 --> 0:18:52.920 care is improving and the vulnerability is improving, right, And 0:18:52.960 --> 0:18:56.840 so I think that's where having a strong cybersecurity strategy 0:18:57.480 --> 0:18:59.920 actually enables all of that. One of our products is 0:19:00.119 --> 0:19:03.240 our sas product, and we tested it with some business applications, 0:19:03.280 --> 0:19:05.840 and oftentimes the wrap is, oh, security is going to 0:19:05.840 --> 0:19:07.880 slow you down, right, Like you have to add a firewall, 0:19:07.920 --> 0:19:11.720 you have to checkpoints. Our product actually increases the velocity 0:19:11.880 --> 0:19:14.359 of your ability to use that application because of the 0:19:14.359 --> 0:19:18.280 way that it is queried through our system as opposed 0:19:18.320 --> 0:19:20.880 to just through the regular network. So it doesn't slow 0:19:20.880 --> 0:19:23.119 it down and in fact, it makes it run more efficiently. 0:19:23.840 --> 0:19:29.080 That's just one minor example. But back to the healthcare question. I, 0:19:29.119 --> 0:19:31.480 as a patient want my doctors accessing all the technology 0:19:31.520 --> 0:19:33.560 and talking to each other and connecting the dots behind 0:19:33.600 --> 0:19:36.159 the scenes. I also want my data to stay private, 0:19:36.720 --> 0:19:41.880 and so having both a consulting partner who understands how 0:19:41.920 --> 0:19:44.320 to ask questions of the environment and of the applications 0:19:44.320 --> 0:19:47.200 you're using, and who understands the industry inside and out, 0:19:47.640 --> 0:19:50.439 and a technology partner that builds and stays ahead of 0:19:50.480 --> 0:19:53.080 all of the different threats, come together and advise you. 0:19:53.160 --> 0:19:57.119 I think is super important. When you bring in a 0:19:57.160 --> 0:20:01.160 partner like IBM, with a platform like pal Aalta that covers, 0:20:01.560 --> 0:20:05.320 you know, all the different parts of your environment, you're 0:20:05.359 --> 0:20:08.879 able to say, look, where where are the vulnerabilities in 0:20:08.920 --> 0:20:11.960 the system, Where are the different endpoints that we need 0:20:12.000 --> 0:20:13.920 to have covered, and then just make sure you get 0:20:13.920 --> 0:20:17.520 that breadth of coverage, and then you're better able to so, yes, 0:20:17.560 --> 0:20:19.639 you've increased the risk, but then you've mitigated it. 0:20:20.400 --> 0:20:24.720 So to give so before I retire my healthcare analogy, 0:20:25.119 --> 0:20:28.399 because I was thinking about just trying to understand the 0:20:28.440 --> 0:20:33.239 importance of this idea of having a single platform. So 0:20:33.560 --> 0:20:36.840 if this muddle healthcare network is typical, I've acquired a 0:20:36.880 --> 0:20:39.320 whole series of over the last ten years. I bought 0:20:39.359 --> 0:20:42.160 a hospital over here, some I've got some physicians things 0:20:42.160 --> 0:20:45.320 that I snapped up over here. I bought a diagnostics company, 0:20:45.760 --> 0:20:49.159 and so I have all of these legacy systems and 0:20:49.200 --> 0:20:51.359 I had, like you said, maybe I got some stuff 0:20:51.359 --> 0:20:53.560 from the cloud with one company, some stuff with the cloud. 0:20:53.760 --> 0:20:56.480 And what you're saying is the first step is to 0:20:56.560 --> 0:21:00.520 kind of rationalize that put it on a single so 0:21:00.560 --> 0:21:04.040 you understand where your points of weakness are as opposed 0:21:04.040 --> 0:21:05.640 to being blind to your points of weakness. 0:21:07.400 --> 0:21:12.359 There's yes, although anyone who's done any kind of M 0:21:12.400 --> 0:21:15.000 and A knows that that's a long journey, right. So 0:21:15.080 --> 0:21:18.679 I think the first step is just understanding where everything is. 0:21:19.320 --> 0:21:20.560 And then you get on a path and you say, 0:21:20.560 --> 0:21:23.399 where's the biggest risk. Let's let's neutralize or mitigate that 0:21:23.480 --> 0:21:27.040 risk one at a time. The thing about open end secure, 0:21:27.760 --> 0:21:30.320 you know Palo Alto. We keep touting the benefits of 0:21:30.359 --> 0:21:33.040 the platform. Everything on Palo Alto, your risk is going 0:21:33.080 --> 0:21:35.040 to be mitigated and you're going to have the full visibility. 0:21:35.720 --> 0:21:39.119 But you can't get there overnight. And so we've got 0:21:39.320 --> 0:21:42.639 you know, thousands of integrations with other technology companies, including 0:21:42.640 --> 0:21:45.280 our partners, to make sure that we can capture and 0:21:45.480 --> 0:21:49.679 have visibility into those those endpoints in those systems as well. 0:21:49.880 --> 0:21:51.959 And so I think step one is just figure out 0:21:51.960 --> 0:21:54.280 where everything is. Just get the scan, so poltize a 0:21:54.280 --> 0:21:56.199 couple of products where you can kind of deploy and 0:21:56.240 --> 0:21:59.400 get a view of your attack surface. I love the analogy. 0:21:59.520 --> 0:22:02.159