WEBVTT - How AI Can Accelerate Cybersecurity 0:00:03.960 --> 0:00:07.320 Hello, Hello, Welcome to Smart Talks with IBM, a podcast 0:00:07.360 --> 0:00:12.560 from Pushkin Industries, iHeart Radio and IBM. I'm Malcolm Glapwell. 0:00:13.240 --> 0:00:16.480 This season, we're diving back into the world of artificial intelligence, 0:00:16.800 --> 0:00:20.320 but with a focus on the powerful concept of open 0:00:21.040 --> 0:00:26.599 its possibilities, implications, and misconceptions. We'll look at openness from 0:00:26.600 --> 0:00:29.720 a variety of angles and explore how the concept is 0:00:29.760 --> 0:00:33.800 already reshaping industries, ways of doing business and our very 0:00:33.880 --> 0:00:38.400 notion of what's possible. On today's episode, I'm joined by 0:00:38.479 --> 0:00:42.440 Jason Kelly, the global Managing Partner for IBM Strategic Partners 0:00:42.479 --> 0:00:46.599 and Ecosystems, and by Christy Fredericks, the Senior Vice president 0:00:46.880 --> 0:00:52.000 and Chief Partnership Officer at Palo Alto Networks. We discussed 0:00:52.000 --> 0:00:56.920 how their partnership in the cybersecurity space helps strengthen enterprises 0:00:57.120 --> 0:01:01.440 by focusing on seamless cybersecurity solutions tailored to meet the 0:01:01.480 --> 0:01:07.280 evolving threat landscape. By leveraging AI and automation, this collaboration 0:01:07.400 --> 0:01:12.560 aims to modernize security programs, improve response times, and produce risks. 0:01:13.840 --> 0:01:17.280 Jason and Christie both bring a tremendous amount of experience 0:01:17.600 --> 0:01:21.039 and expertise to the subject I think you're really going 0:01:21.120 --> 0:01:36.160 to enjoy this one. Jason Christy, Welcome to Smart Talks 0:01:36.160 --> 0:01:38.080 with IBM. Thank you for joining me. 0:01:38.360 --> 0:01:38.760 Thank you. 0:01:38.920 --> 0:01:39.760 It's great to be here. 0:01:40.120 --> 0:01:43.560 We are here to discuss cybersecurity and the partnership between 0:01:43.600 --> 0:01:46.840 IBM and Palo Alto Networks. But before we get there, 0:01:47.080 --> 0:01:48.760 I wanted you guys to tell me a little bit 0:01:49.360 --> 0:01:54.040 about yourself. Jason, start with you. I see on your 0:01:54.720 --> 0:01:58.640 resume west Point, which makes we think there's some interesting 0:01:58.680 --> 0:02:01.680 things going on. How did you get to west Point? 0:02:02.240 --> 0:02:04.720 West Point? West Point was the decision. First, it was 0:02:04.760 --> 0:02:07.880 it was affordable back in the day. But I had 0:02:07.880 --> 0:02:09.720 a sense of service. My father was a World War 0:02:09.760 --> 0:02:12.760 Two vet, so I grew up on the weekends watching 0:02:12.840 --> 0:02:16.800 World War two video. You know he's army as well. Yeah, 0:02:16.840 --> 0:02:21.360 and so I thought, oh that'd be exciting, and I 0:02:21.360 --> 0:02:24.640 thought I do some type of service. Went there and 0:02:24.680 --> 0:02:27.400 now I have the biggest family, extended family I could 0:02:27.440 --> 0:02:30.760 ever have. So it was very exciting. Played football lucked out, 0:02:31.600 --> 0:02:37.120 meaning I wasn't recruited. I walked on and that kept 0:02:37.120 --> 0:02:39.040 me there because it gave me something and out left 0:02:39.080 --> 0:02:42.400 with all the other pressures defensive back, I was I 0:02:42.560 --> 0:02:44.600 was great at knocking the ball down, not the best 0:02:44.639 --> 0:02:45.240 at catching it. 0:02:45.320 --> 0:02:48.600 Yeah, and then you were a ranger. 0:02:49.480 --> 0:02:51.880 I was. I was privileged to be a US Army 0:02:51.919 --> 0:02:55.079 airborne ranger station, but did most of my time in 0:02:55.120 --> 0:02:59.080 northern Italy. We're part of the it's eighty second airbarnship post. 0:02:59.160 --> 0:03:02.400 Oh yeah, people say seriously, like, you know, you were, 0:03:02.400 --> 0:03:05.200 you were, you were drinking wine and having bred you know. 0:03:05.639 --> 0:03:08.919 But it was a part of a NATO force there 0:03:08.960 --> 0:03:11.520 at the time. Yeah, so exciting. 0:03:11.760 --> 0:03:15.400 How did you get from there to IBM? 0:03:15.880 --> 0:03:18.400 A long path. As I came out of the military, 0:03:18.639 --> 0:03:26.280 I started manufacturing retail housing and did a quick stint, 0:03:26.320 --> 0:03:30.400 took a leave of absence from industry, and did a 0:03:30.560 --> 0:03:33.680 stint of yet again public service in the state of 0:03:33.720 --> 0:03:38.360 Tennessee with economic development, and got a whiff of how 0:03:38.400 --> 0:03:41.840 fun it could be to do things around data and media. 0:03:42.160 --> 0:03:45.120 Started a small media firm what we would now call 0:03:45.160 --> 0:03:49.480 a digital firm, sold it and said I wanted to 0:03:49.520 --> 0:03:51.880 go do it again somewhere, but I wanted to go 0:03:51.920 --> 0:03:54.520 to a big company. And the family at IBM brought 0:03:54.600 --> 0:03:56.760 me in and yet to let me go. 0:03:56.960 --> 0:03:58.120 That was how many years ago? 0:04:00.040 --> 0:04:00.680 Two decades? 0:04:00.840 --> 0:04:01.280 Oh wow? 0:04:01.600 --> 0:04:04.080 Yeah, so, I know I look amazingly young on but yes, 0:04:05.400 --> 0:04:08.880 you must have. And IBM was my fifth career and 0:04:09.000 --> 0:04:11.360 and and I've enjoyed a since and that's what I 0:04:11.680 --> 0:04:14.120 what I do. They build teams, grow new parts of 0:04:14.120 --> 0:04:16.320 the company and get to work with some of the 0:04:16.320 --> 0:04:19.040 most brilliant people on the face of the planet, as 0:04:19.040 --> 0:04:22.960 well as partners like Christy that just keep it exciting. 0:04:23.279 --> 0:04:25.800 Christy, you're I was delighted to learn that you are Canadian. 0:04:25.960 --> 0:04:31.680 Yes here, Yeah, but you so you were a consultant 0:04:31.680 --> 0:04:33.080 for a long time at Bane. 0:04:33.440 --> 0:04:36.680 Yes, yeah. I joined Bain Consulting intending to spend a 0:04:36.680 --> 0:04:38.760 couple of years there learn the ropes and then go 0:04:38.800 --> 0:04:42.359 get my first real job. But the value personally to 0:04:42.400 --> 0:04:44.360 my growth and development, and then that we were able 0:04:44.400 --> 0:04:46.960 to bring our clients. I ended up there for sixteen years, 0:04:47.560 --> 0:04:51.080 and then post Bain went on to another my first 0:04:51.120 --> 0:04:53.880 product company, a new relic, and then it's come full 0:04:53.920 --> 0:04:57.280 circle at Powlta Networks. But at Bain it was all 0:04:57.320 --> 0:05:00.760 about bringing expertise across different industries to help our clients 0:05:01.000 --> 0:05:04.600 improve whatever they needed to improve and bringing that expertise 0:05:04.640 --> 0:05:07.039 to bear and then you have the product lens and 0:05:07.080 --> 0:05:08.840 you think, Okay, we're going to build the absolute best 0:05:08.839 --> 0:05:11.440 product to help our customers do what they need to 0:05:11.440 --> 0:05:14.200 get done. And then I joined pal Alto about six 0:05:14.240 --> 0:05:18.360 seven months ago in a partnership's role and I'm delighted 0:05:18.360 --> 0:05:20.719 to be able to work with amazing consulting companies like 0:05:20.760 --> 0:05:22.640 IBM where we bring both to bear. 0:05:23.160 --> 0:05:26.320 How long have IBM and Paulo Alto Network's been partners? 0:05:26.960 --> 0:05:29.880 So we've been We've been working together for quite quite 0:05:29.880 --> 0:05:33.400 a long time, but we made it official, meaning we 0:05:33.720 --> 0:05:35.839 got married as strategic partners last year. 0:05:36.000 --> 0:05:38.039 Oh I see. So what is it that each of 0:05:38.080 --> 0:05:41.239 you bring to the table? What's each side special? 0:05:41.320 --> 0:05:44.200 So it's great that you asked that because about a 0:05:44.240 --> 0:05:48.160 decade ago, are now CEO Arvin Christ says, you know, 0:05:48.160 --> 0:05:50.800 it wouldn't be great if we just had this one 0:05:50.839 --> 0:05:53.320 focus with this what does IBM do? And you have 0:05:53.400 --> 0:05:55.720 this whole list, and he says, let's make it simple. 0:05:56.320 --> 0:06:01.039 We are a multi cloud, hybrid cloud AIIC company. And 0:06:01.120 --> 0:06:03.480 so when you say that, it sounds very simple, but 0:06:03.520 --> 0:06:07.480 then people, what the hell is that? What your hybrid cloud? Well, 0:06:08.160 --> 0:06:10.039 both of those two things have a lot of data 0:06:10.080 --> 0:06:13.240 involved and a lot of those mean that that data 0:06:13.320 --> 0:06:17.320 is going to sit in multiple places and distributed environments. Well, 0:06:17.360 --> 0:06:20.680 if you're able to tie those things together with multiple partners, 0:06:21.040 --> 0:06:25.160 you also have to make sure that it's secure because 0:06:25.560 --> 0:06:28.760 in the direction that we're going, where data is now 0:06:29.000 --> 0:06:31.479 being consumed in many different places and it is the 0:06:31.520 --> 0:06:35.960 fuel behind AI as we know, then you say, ah, well, 0:06:36.480 --> 0:06:38.960 who does that well and who does it in a 0:06:39.000 --> 0:06:41.800 way that's getting rid of seams, the seams that could 0:06:41.800 --> 0:06:45.840 be across multiple products, multiple product SATs even And that's 0:06:45.880 --> 0:06:46.800 where Powell comes in. 0:06:47.680 --> 0:06:51.440 I think the conventional wisdom and cybersecurity was always you 0:06:51.520 --> 0:06:54.880 need all the new tools, right, you need it every threat. 0:06:54.920 --> 0:06:56.680 It's like, whack them all. Every threat that pops up, 0:06:56.720 --> 0:07:00.200 you get the tool that's purpose built for that specific thing. Well, 0:07:00.240 --> 0:07:02.760 fast forward to you know, the RSA conference this year, 0:07:02.800 --> 0:07:06.400 there were four thousand vendors on the floor. You look 0:07:06.400 --> 0:07:09.680 at an average company, there's hundreds of cybersecurity tools. It 0:07:09.800 --> 0:07:13.640 introduces a level of complexity that is really hard to 0:07:13.680 --> 0:07:19.360 manage you as a user. Query and application, right, that 0:07:19.480 --> 0:07:23.200 query can go through a bunch of different pings from 0:07:23.240 --> 0:07:25.080 one cloud to the next. It goes into and out 0:07:25.080 --> 0:07:27.840 of assaas application. It maybe running along a network. You 0:07:27.840 --> 0:07:29.520 may be accessing it from your phone, which is an 0:07:29.600 --> 0:07:32.360 unmanaged device. It's got to go in and out. And 0:07:32.400 --> 0:07:35.080 if you say, okay, I've got to secure that phone, 0:07:35.680 --> 0:07:37.880 I've got to secure the network, I've got it. And 0:07:37.880 --> 0:07:39.760 then all of a sudden you've got sort of firewalls, 0:07:39.800 --> 0:07:43.520 software and hardwelfiles popping up everywhere. You've got cloud security, 0:07:44.080 --> 0:07:46.360 and it's you've probably heard of this concept of zero trust, 0:07:46.360 --> 0:07:47.920 which is every time you have to check and say 0:07:47.920 --> 0:07:49.680 are you allowed in here? Are you allowed in here? 0:07:49.960 --> 0:07:52.520 The number of places that can fall down it just 0:07:52.560 --> 0:07:56.239 becomes overwhelming. So you end up with either alerts firing, 0:07:56.720 --> 0:07:59.520 you know, every two seconds that you have to then 0:07:59.560 --> 0:08:02.600 go invest again, most of which are false positives or 0:08:03.160 --> 0:08:06.440 you miss something right. And so that was the conventionalism 0:08:06.560 --> 0:08:08.160 was we've got to buy all these tools, and now 0:08:08.200 --> 0:08:11.360 you've got overwhelmed CIOs and CSOs with hundreds of tools, 0:08:11.400 --> 0:08:14.520 and Palo Alto strategy has been, look, we're going to 0:08:14.600 --> 0:08:17.640 create a platform where everything can be stitched together, everything 0:08:17.680 --> 0:08:21.200 can speak the same language, and we can sort of 0:08:22.040 --> 0:08:25.000 manage throughout the architecture and watch, you know, this call 0:08:25.040 --> 0:08:29.280 as as it's passing through all these different checkpoints, and 0:08:29.520 --> 0:08:31.040 we can do it in a way that you still 0:08:31.040 --> 0:08:32.920 have the confidence that it's best to breed right, so 0:08:32.960 --> 0:08:35.600 you're not making any trade offs. But it's not so 0:08:35.640 --> 0:08:39.920 simple just to get from the spaghetti to the seamless architecture. 0:08:39.960 --> 0:08:43.440 You need, oftentimes to re engineer your business processes. You 0:08:43.520 --> 0:08:46.719 have to re architect your digital environment. And so that's 0:08:46.720 --> 0:08:49.600 where we partner with a company like IBM to bring 0:08:49.600 --> 0:08:51.760 that expertise and say we're going to help you not 0:08:51.920 --> 0:08:54.800 just deploy the best cybersecurity architecture, but really get your 0:08:54.880 --> 0:08:57.680 environment ready to have this zero testomer. 0:08:57.360 --> 0:09:01.000 As well as all of those players that cross at spaghetti. 0:09:01.679 --> 0:09:04.360 Because when you start thinking about all the other partners 0:09:04.400 --> 0:09:06.360 that you work with, if you're you think of an 0:09:06.360 --> 0:09:09.360 industry perspective, you're going to have an ERP. It could 0:09:09.360 --> 0:09:12.080 be an Oracle, it could be an SAP. You're not 0:09:12.080 --> 0:09:13.720 going to have one cloud, as I mentioned, it's gonna 0:09:13.720 --> 0:09:18.200 be possibly multiple clouds. You'll have some AWS maybe Microsoft Azure, 0:09:18.200 --> 0:09:20.360 and then even even some Google in there, and then 0:09:20.400 --> 0:09:23.320 your own that you've built in your private over there, uh, 0:09:24.240 --> 0:09:28.200 some an IBM cloud. You'll have those multiple clouds, and 0:09:28.240 --> 0:09:31.000 then you also will have you know, fit for purpose. 0:09:31.120 --> 0:09:33.640 Oh I need a I need a salesforce in there 0:09:33.880 --> 0:09:36.800 for my customer focusing. I need I'm doing some graphics, 0:09:36.800 --> 0:09:38.800 so I have Adobe, so I just as I can 0:09:38.960 --> 0:09:42.440 name name name, all of those then have to be 0:09:43.120 --> 0:09:46.080 re engineered. Seriously. I mean, come on, Malcolm, You're gonna 0:09:46.080 --> 0:09:48.480 sit there. You think how long that would take. So 0:09:48.920 --> 0:09:52.679 if you haven't done that before, you're going to have 0:09:52.720 --> 0:09:54.320 to go to each one of those individually, or you 0:09:54.360 --> 0:09:57.400 can work with a company that can tie those things together, 0:09:57.480 --> 0:10:01.240 because we are also strategic partners with them. So that's 0:10:01.280 --> 0:10:04.360 where you start to say, Okay, I see how this 0:10:04.480 --> 0:10:09.120 comes together. You have to make sure that your ecosystem 0:10:09.200 --> 0:10:12.040 is going to be stronger than your competitor's ecosystem, and 0:10:12.120 --> 0:10:14.439 you have to be secure in what you're doing because 0:10:14.480 --> 0:10:17.760 as you add more players or products, you create seams, 0:10:18.320 --> 0:10:20.920 and you want to make sure there's fewer seams and 0:10:20.960 --> 0:10:25.800 that there's zero trust across that capability you're building. And 0:10:25.840 --> 0:10:28.280 that's why the compliment between the two companies. 0:10:28.440 --> 0:10:30.480 We'll take a step back from a moment before we 0:10:30.559 --> 0:10:33.320 sort of launch. Once get into the specifics of what 0:10:33.400 --> 0:10:37.240 you guys are doing. I'm curious at this moment in 0:10:37.360 --> 0:10:43.720 twenty twenty four, how nervous should we be about cybersecurity? 0:10:43.920 --> 0:10:48.080 So compared it to five years ago or ten years ago, 0:10:48.600 --> 0:10:50.600 are we are you less nervous than you were five 0:10:50.679 --> 0:10:53.320 years ago or more nervous or all of changes going 0:10:53.360 --> 0:10:57.800 on right now increasing vulnerability or decreasing it? 0:10:58.200 --> 0:11:01.680 I would say Chris, also, I think we share the 0:11:01.720 --> 0:11:05.840 point of views that it's not necessarily being more nervous. 0:11:05.880 --> 0:11:09.800 I think you should be more prepared. Yeah, because the 0:11:09.880 --> 0:11:15.240 amounts of threat is increasing based on our dependence upon data. 0:11:16.320 --> 0:11:20.640 And that's that's where I think the attention should be placed. 0:11:20.679 --> 0:11:23.800 Is that more and more, especially with the importance of 0:11:23.840 --> 0:11:27.800 AI that you say, okay, then what's under all that? 0:11:27.840 --> 0:11:31.760 And it's the data? As I said, so knowing that 0:11:32.640 --> 0:11:33.840 you should be more concerned. 0:11:35.240 --> 0:11:39.240 Does the advent of AI and it's rapid evolution help 0:11:39.360 --> 0:11:41.160 defense more or offense more? 0:11:41.720 --> 0:11:44.600 I think it's I think it's like any mega trend 0:11:44.600 --> 0:11:48.680 that we've witnessed both. Right, So you think about AI, 0:11:48.800 --> 0:11:52.800 it's ninety nine percent great right in terms of what 0:11:52.840 --> 0:11:55.920 it's going to unlock for productivity for humanity, But it 0:11:56.000 --> 0:11:58.559 also makes it a whole lot easier to build ransomware. 0:11:58.760 --> 0:12:01.720 It's a whole lot easier to take different ways into 0:12:01.760 --> 0:12:04.200 a system, right. But I think that's true if you 0:12:04.240 --> 0:12:06.040 think about like the rise of the Internet, right, all 0:12:06.080 --> 0:12:09.600 of a sudden, everyone was putting their data online and 0:12:09.679 --> 0:12:11.920 you had to think of new ways to stay ahead 0:12:11.960 --> 0:12:13.599 and keep that secure. And I don't think AI is 0:12:13.640 --> 0:12:17.320 any different. You've got companies like Palta, partnerships like Powell 0:12:17.360 --> 0:12:22.600 and IBM that are constantly scanning the landscape for not 0:12:22.640 --> 0:12:25.160 only the current threats, but what's next, what's coming around 0:12:25.160 --> 0:12:28.000 the corner, what's after AI? And so I think taking 0:12:28.040 --> 0:12:30.360 it seriously and being prepared is probably the right way 0:12:30.360 --> 0:12:32.719 of looking at it, as opposed to because if you 0:12:32.720 --> 0:12:35.360 think about it too hard, you'll just want to crawl 0:12:35.400 --> 0:12:39.360 into a corner and stuff everything under the mattress. 0:12:39.760 --> 0:12:46.959 I am the CEO of a regional hospital chain, big 0:12:47.120 --> 0:12:52.160 distribute healthcare system, so a ton of data. The consequences 0:12:52.160 --> 0:12:56.120 of being hacked and help for ransom are life and death. 0:12:56.280 --> 0:13:00.640 Life and death. When you come so you you come down, 0:13:00.720 --> 0:13:02.480 You sit down with me, and you chat with me. 0:13:03.880 --> 0:13:06.200 Walk me through the kinds of things you would tell 0:13:06.240 --> 0:13:09.320 me about what I need to get safer. For example, 0:13:09.480 --> 0:13:12.360 let's start with one. Is it likely that I'm spending 0:13:12.360 --> 0:13:14.520 too little or am I spending money in the wrong place? 0:13:15.400 --> 0:13:19.440 Great question, It depends how you've broken it out. If 0:13:19.480 --> 0:13:22.640 you are distributing all of your dollars across a whole 0:13:22.640 --> 0:13:25.200 bunch of different tools, it's likely you're just spending the 0:13:25.240 --> 0:13:27.480 wrong money. And in fact, you know, putting it all 0:13:27.520 --> 0:13:30.280 in one place is a way of potentially saving money 0:13:30.640 --> 0:13:34.480 but keeping your security actually higher. And I'd love to 0:13:34.480 --> 0:13:36.320 hear Jason, how you would approach it. How we would 0:13:36.320 --> 0:13:38.520 approach it, of course, is by saying, you know what, 0:13:38.520 --> 0:13:41.640 what does your environment look like? You know, do you 0:13:41.720 --> 0:13:46.160 have the connected medical devices into your EMR? Are your 0:13:46.280 --> 0:13:49.760 respirators and ventilators all online? Right? And so we would 0:13:49.800 --> 0:13:52.640 talk about, okay, here's how you get coverage, and how 0:13:52.679 --> 0:13:55.200 the coverage of both the firewalls as well as the 0:13:55.280 --> 0:13:58.679 detectors all feedback into your security operation center and you 0:13:58.720 --> 0:14:01.319 can manage it and and do your learning with AI 0:14:02.360 --> 0:14:03.480 and keep yourself securing. 0:14:03.520 --> 0:14:05.800 So yeah, and I would say Christy and I would 0:14:05.840 --> 0:14:08.280 go to the same point because if you get under 0:14:08.559 --> 0:14:12.080 what she was just asking it is your data on 0:14:12.160 --> 0:14:16.320 prem and when it's on prem, how active is it 0:14:16.360 --> 0:14:20.520 across the enterprise? And so that begins the basis for 0:14:20.560 --> 0:14:22.520 the start. And then often you're going to say, well, 0:14:22.520 --> 0:14:25.720 we actually take in data from outside and then we 0:14:25.760 --> 0:14:29.240 also have the circumstances. There's a lot of PII and 0:14:29.320 --> 0:14:34.520 so that personal is the personal information, right, Yeah, And 0:14:34.600 --> 0:14:37.840 so now you're saying, okay, now, how are we securing 0:14:37.920 --> 0:14:40.760 that and where are we securing it? And so you 0:14:40.840 --> 0:14:44.640 have to start really thinking about the different areas within 0:14:44.960 --> 0:14:49.040 that hospital chain. Are you sharing that amongst your hospitals? 0:14:49.600 --> 0:14:52.760 And now you start to think of if I'm saying 0:14:52.800 --> 0:14:54.240 no to a lot of that, it's like, well, then 0:14:54.280 --> 0:14:56.920 are you as efficient as you want to be? So 0:14:57.000 --> 0:15:00.520 there is that trade off of you know, am I 0:15:00.560 --> 0:15:04.120 so tightly walled that I'm not productive? And so that's 0:15:04.160 --> 0:15:07.240 where we would start to say, what's the outcome that 0:15:07.280 --> 0:15:09.400 you're trying to get to? All Right, maybe you're good, 0:15:09.440 --> 0:15:11.800 Maybe you're you're good with your five locations and you 0:15:11.840 --> 0:15:14.320 don't need to go any further, but maybe you want 0:15:14.360 --> 0:15:16.400 to expand to fifty and by the way, you're going 0:15:16.440 --> 0:15:18.160 to go crossport or you're going to be in Toronto 0:15:18.480 --> 0:15:21.640 and in New York. Okay, well then how do you 0:15:21.720 --> 0:15:25.160 do that? And so I think that it's very easy 0:15:25.200 --> 0:15:30.560 to start jumping into any of the typical situations. But 0:15:30.680 --> 0:15:33.400 the first question that you have to ask you, as 0:15:33.480 --> 0:15:38.200 the hospital CEOs, what's your objective? What are you what 0:15:38.240 --> 0:15:40.840 are you trying to do? Because too often what we 0:15:40.920 --> 0:15:44.240 see is that there's some bright, new, shiny thing that 0:15:44.320 --> 0:15:47.040 everybody wants to put in play. You know, it's a 0:15:47.080 --> 0:15:50.520 sandwich looking for lunch, and you go, but what is 0:15:50.560 --> 0:15:52.600 it that you want to do as this Are you 0:15:52.640 --> 0:15:56.520 doing research? Are your research hospital? Are you more consumer oriented? 0:15:56.800 --> 0:15:58.960 So those are the questions you start to ask because 0:15:59.000 --> 0:16:01.800 they start to then tell a story in line with 0:16:01.800 --> 0:16:05.480 what Christy questions. And I think that that's where the again, 0:16:05.520 --> 0:16:08.600 the complement is that instead of just saying, oh, well, 0:16:08.640 --> 0:16:11.280 that's thanks for telling me all this, Malcolm, here's your 0:16:11.520 --> 0:16:16.440 ten page strategy, go find somebody. We have the benefit 0:16:17.120 --> 0:16:19.480 in IBM, and is probably why I'm still there is 0:16:19.560 --> 0:16:22.160 you know, we're very unique. We're the only company on 0:16:22.200 --> 0:16:27.000 the planet that has a consulting business at scale inside 0:16:27.000 --> 0:16:30.880 of a technology company, and so we have you know, 0:16:31.120 --> 0:16:33.160 the left brain right brain. We're able to do that, 0:16:33.720 --> 0:16:35.880 and then we're able to say, okay, now which partners 0:16:36.040 --> 0:16:40.160 are going to be most valuable for our clients. What's 0:16:40.160 --> 0:16:41.680 going to work for you? Isn't going to work for 0:16:41.720 --> 0:16:44.000 the manufacturer down the road, isn't going to work for 0:16:44.040 --> 0:16:49.000 the consumer or CpG company across the river. Those things 0:16:49.040 --> 0:16:52.760 are very specific. The threats and the scenes that I 0:16:52.800 --> 0:16:56.000 was talking about are very specific. So that's where it 0:16:56.040 --> 0:16:59.400 becomes very valuable to make sure that I'm not just 0:16:59.600 --> 0:17:02.400 giving you some strategy that's generic. 0:17:02.400 --> 0:17:07.200 But everything as a healthcare CEO, everything I have done, 0:17:07.640 --> 0:17:11.119 almost everything I've done over the last ten years, hasn't 0:17:11.119 --> 0:17:13.640 it had the effect of increasing my vulnerability. I want 0:17:13.680 --> 0:17:16.440 to digitize data within the hospital used to be on 0:17:16.480 --> 0:17:20.040 pieces of paper. I want doctors to go home and 0:17:20.160 --> 0:17:22.160 to be able to seamlessly hook into stuff at work 0:17:22.160 --> 0:17:24.680 because they got to do all their paperwork. I want 0:17:24.720 --> 0:17:27.399 to make sure the diabetes people are speaking to the 0:17:27.520 --> 0:17:31.199 organ transplant people. And so isn't that everything I have 0:17:31.280 --> 0:17:34.560 done to kind of keep up with the revolution in healthcare? 0:17:34.960 --> 0:17:37.280 Isn't that also making me more and more vulnerable to 0:17:37.840 --> 0:17:38.480 a bad actor. 0:17:38.600 --> 0:17:40.960 It's such a great question because think about the quality 0:17:41.000 --> 0:17:44.399 of healthcare delivery. Right. So now doctors aren't filling out forms, 0:17:44.400 --> 0:17:47.159 they're spending time with patients, and so the quality of 0:17:47.200 --> 0:17:49.800 care is improving and the vulnerability is improving, right, And 0:17:49.800 --> 0:17:53.679 so I think that's where having a strong cybersecurity strategy 0:17:54.320 --> 0:17:56.879 actually enables all of that. One of our products is 0:17:56.920 --> 0:17:59.359 our sas product, and we tested it with some business 0:17:59.400 --> 0:18:02.560 application and oftentimes the wrap is, oh, security is going 0:18:02.600 --> 0:18:04.760 to slow you down, like you have to add a firewall, 0:18:04.760 --> 0:18:08.639 you have to checkpoints. Our product actually increases the velocity 0:18:08.760 --> 0:18:11.199 of your ability to use that application because of the 0:18:11.200 --> 0:18:15.159 way that it is queried through our system as opposed 0:18:15.160 --> 0:18:17.720 to just through the regular network. So it doesn't slow 0:18:17.720 --> 0:18:19.959 it down and in fact, it makes it run more efficiently. 0:18:20.720 --> 0:18:25.919 That's just one minor example. But back to the healthcare question. I, 0:18:26.000 --> 0:18:28.359 as a patient want my doctors accessing all the technology 0:18:28.359 --> 0:18:30.440 and talking to each other and connecting the dots behind 0:18:30.440 --> 0:18:33.040 the scenes. I also want my data to stay private, 0:18:33.560 --> 0:18:38.720 and so having both a consulting partner who understands how 0:18:38.760 --> 0:18:41.159 to ask questions of the environment and of the applications 0:18:41.200 --> 0:18:44.040 you're using, and who understands the industry inside and out 0:18:44.480 --> 0:18:47.280 and a technology partner that builds and stays ahead of 0:18:47.320 --> 0:18:49.959 all of the different threats, come together and advise you. 0:18:50.000 --> 0:18:53.960 I think is super important. When you bring in a 0:18:54.000 --> 0:18:58.040 partner like IBM, with a platform like Palalta that covers 0:18:58.680 --> 0:19:03.240 all the different parts of your environment, you're able to say, look, 0:19:03.320 --> 0:19:06.720 where where are the vulnerabilities in the system, Where are 0:19:06.760 --> 0:19:09.760 the different endpoints that we need to have covered, and 0:19:09.800 --> 0:19:11.760 then just make sure you get that breadth of coverage, 0:19:12.600 --> 0:19:14.919 and then you're better able to so, yes, you've increased 0:19:14.960 --> 0:19:16.520 the risk, but then you've mitigated it. 0:19:17.240 --> 0:19:21.560 So to give so before I retire my healthcare analogy, 0:19:21.960 --> 0:19:25.239 because I was thinking about just trying to understand the 0:19:25.280 --> 0:19:30.080 importance of this idea of having a single platform. So 0:19:30.400 --> 0:19:33.720 if this muddle healthcare network is typical, I've acquired a 0:19:33.720 --> 0:19:36.200 whole series of over the last ten years. I bought 0:19:36.200 --> 0:19:39.040 a hospital over here, some I got some physicians, things 0:19:39.040 --> 0:19:42.160 that I snapped up over here about a diagnostics company, 0:19:42.640 --> 0:19:46.000 and so I have all of these legacy systems, and 0:19:46.040 --> 0:19:48.200 I had, like you said, maybe I got some stuff 0:19:48.240 --> 0:19:50.399 in the cloud with one company, some stuff with the cloud. 0:19:50.640 --> 0:19:53.320 And what you're saying is the first step is to 0:19:53.400 --> 0:19:57.240 kind of rationalize that put it on a single platform, 0:19:57.280 --> 0:20:00.520 so you understand where your points of weakness are as 0:20:00.520 --> 0:20:02.480 opposed to being blind to your points of weakness. 0:20:04.280 --> 0:20:09.240 There's yes, although anyone who's done any kind of M 0:20:09.240 --> 0:20:11.840 and A knows that that's a long journey, right. So 0:20:11.920 --> 0:20:15.560 I think the first step is just understanding where everything is. 0:20:16.200 --> 0:20:17.399 And then you get on a path and you say, 0:20:17.400 --> 0:20:20.240 where's the biggest risk. Let's let's neutralize or mitigate that 0:20:20.359 --> 0:20:23.880 risk one at a time. The thing about open end secure, 0:20:24.640 --> 0:20:27.199 you know Palo Alto. We keep touting the benefits of 0:20:27.200 --> 0:20:29.879 the platform. Everything on Palo Alto, your risk is going 0:20:29.920 --> 0:20:31.879 to be mitigated and you're going to have the full visibility. 0:20:32.560 --> 0:20:35.960 But you can't get there overnight. And so we've got 0:20:36.160 --> 0:20:39.480 you know, thousands of integrations with other technology companies, including 0:20:39.480 --> 0:20:42.119 our partners, to make sure that we can capture and 0:20:42.320 --> 0:20:46.520 have visibility into those those endpoints in those systems as well. 0:20:46.720 --> 0:20:48.840 And so I think step one is just figure out 0:20:48.840 --> 0:20:51.040 where everything is. Just get the scan. So Polta has 0:20:51.080 --> 0:20:52.919 a couple of products where you can kind of deploy 0:20:52.960 --> 0:20:55.720 and get a view of your attack surface. I love 0:20:55.760 --> 0:20:58.920 the analogy. Just like a digital environment is a house right, 0:20:58.960 --> 0:21:01.000 and so like you have your front lock, of course, 0:21:01.200 --> 0:21:03.119 because probably they're going to try the front door first. 0:21:03.880 --> 0:21:05.400 But that's not all you're going to do, right, You're 0:21:05.400 --> 0:21:07.000 going to make sure the whole you know, the windows 0:21:07.040 --> 0:21:09.160 are locked and there's an alarm system and all of that. 0:21:10.520 --> 0:21:12.560 And I think that's how you have to think about it, 0:21:12.680 --> 0:21:14.520 is just how do we cover the whole service? 0:21:15.119 --> 0:21:18.520 So everyone laid, people like me have been bombarded over 0:21:18.640 --> 0:21:22.040 it seems like over the last year with one thing 0:21:22.080 --> 0:21:25.320 another about how quickly AI is moving forward and how 0:21:25.400 --> 0:21:27.040 big of a deal it is suddenly is going to 0:21:27.040 --> 0:21:31.200 be in the economy. What is the impact of that 0:21:32.160 --> 0:21:38.119 dramatic change in AI's capabilities on this cybersecurity question? So 0:21:38.240 --> 0:21:40.600 what does it mean if you're defending somebody that you 0:21:40.720 --> 0:21:43.560 now have these sophisticated AI tools you just suppose. 0:21:44.520 --> 0:21:47.800 I think that AI becomes the force multiplier for cyber 0:21:49.520 --> 0:21:54.240 To think about cyber Before it was just locking your doors, 0:21:54.760 --> 0:21:57.800 locking the windows, and if you were really good, you 0:21:57.840 --> 0:22:03.800