WEBVTT - Smart Talks with IBM: How AI Can Accelerate Cybersecurity 0:00:04.440 --> 0:00:12.639 Welcome to tech Stuff, a production from iHeartRadio. This season 0:00:12.720 --> 0:00:16.200 on smart Talks with IBM, Malcolm Gladwell and team are 0:00:16.239 --> 0:00:19.479 diving into the transformative world of artificial intelligence with a 0:00:19.520 --> 0:00:24.120 fresh perspective on the concept of open What does open 0:00:24.560 --> 0:00:27.920 really mean in the context of AI. It can mean 0:00:28.000 --> 0:00:31.600 open source code or open data, but it also encompasses 0:00:31.720 --> 0:00:36.040 fostering an ecosystem of ideas, ensuring diverse perspectives are heard, 0:00:36.159 --> 0:00:39.919 and enabling new levels of transparency. Join hosts from your 0:00:39.960 --> 0:00:43.560 favorite Pushkin podcasts as they explore how openness and AI 0:00:43.800 --> 0:00:49.040 is reshaping industries, driving innovation, and redefining what's possible. You'll 0:00:49.080 --> 0:00:52.360 hear from industry experts and leaders about the implications and 0:00:52.400 --> 0:00:56.160 possibilities of open AI, and of course, Malcolm Gladwell will 0:00:56.200 --> 0:00:58.200 be there to guide you through the season with his 0:00:58.360 --> 0:01:01.840 unique insights. Look out for new episodes of Smart Talks 0:01:01.920 --> 0:01:05.360 every other week on the iHeartRadio app, Apple Podcasts, or 0:01:05.360 --> 0:01:08.920 wherever you get your podcasts, and learn more at IBM 0:01:09.080 --> 0:01:11.360 dot com slash smart Talks. 0:01:14.480 --> 0:01:17.800 Hello, Hello, Welcome to Smart Talks with IBM, a podcast 0:01:17.880 --> 0:01:24.319 from Pushkin Industries, iHeartRadio and IBM. I'm Malcolm Glappwell. This season, 0:01:24.480 --> 0:01:27.399 we're diving back into the world of artificial intelligence, but 0:01:27.520 --> 0:01:33.920 with a focus on the powerful concept of open its possibilities, implications, 0:01:34.240 --> 0:01:37.760 and misconceptions. We'll look at openness from a variety of 0:01:37.760 --> 0:01:41.920 angles and explore how the concept is already reshaping industries, 0:01:42.360 --> 0:01:46.160 ways of doing business and our very notion of what's possible. 0:01:47.280 --> 0:01:50.400 On today's episode, I'm joined by Jason Kelly, the global 0:01:50.440 --> 0:01:54.680 Managing Partner for IBM Strategic Partners and Ecosystems, and by 0:01:54.720 --> 0:01:59.120 Christy Fredericks, the Senior Vice president and Chief Partnership Officer 0:01:59.440 --> 0:02:04.080 at Polowa Networks. We discussed how their partnership in the 0:02:04.120 --> 0:02:10.040 cybersecurity space helps strengthen enterprises by focusing on seamless cybersecurity 0:02:10.080 --> 0:02:15.359 solutions tailored to meet the evolving threat landscape. By leveraging 0:02:15.400 --> 0:02:19.960 AI and automation, this collaboration aims to modernize security programs, 0:02:20.360 --> 0:02:25.359 improve response times, and produce risks. Jason and Christy both 0:02:25.400 --> 0:02:29.639 bring a tremendous amount of experience and expertise to the subject. 0:02:30.760 --> 0:02:45.440 I think you're really going to enjoy this one, Jason, Christy, 0:02:45.560 --> 0:02:48.680 Welcome to Smart Talks with IBM. Thank you for joining me. 0:02:48.880 --> 0:02:49.280 Thank you. 0:02:49.440 --> 0:02:50.320 It's great to be here. 0:02:50.639 --> 0:02:54.120 We are here to discuss cybersecurity and the partnership between 0:02:54.160 --> 0:02:57.360 IBM and Palo Alto Networks. But before we get there, 0:02:57.600 --> 0:02:59.280 I wanted you guys to tell me a little bit 0:03:00.080 --> 0:03:04.079 out yourself. Jason, let's start with you. I see on 0:03:04.120 --> 0:03:08.680 your resume west Point, which makes we think there's some 0:03:08.760 --> 0:03:11.440 interesting things going on there. How did you get to 0:03:11.480 --> 0:03:12.160 west Point? 0:03:12.760 --> 0:03:15.240 West Point? West Point was the decision. First, it was 0:03:15.280 --> 0:03:18.399 it was affordable back in the day. But I had 0:03:18.440 --> 0:03:20.280 a sense of service. My father was a World War 0:03:20.280 --> 0:03:23.280 Two vet, so I grew up on the weekends watching 0:03:23.400 --> 0:03:27.320 World War two video. You know, he's army as well. Yeah, 0:03:27.360 --> 0:03:31.880 and so I thought, oh, that'd be exciting, and I 0:03:31.919 --> 0:03:35.160 thought I do some type of service. Went there and 0:03:35.240 --> 0:03:37.960 now I have the biggest family, extended family I could 0:03:37.960 --> 0:03:41.280 ever have. So it was very exciting. Played football lucked out, 0:03:42.120 --> 0:03:47.640 meaning I wasn't recruited. I walked on and that kept 0:03:47.640 --> 0:03:49.680 me there because it gave me something and outlet with 0:03:49.720 --> 0:03:53.200 all the other pressures. Defensive back I was. I was 0:03:53.440 --> 0:03:55.320 great at knocking the ball down, not the best at 0:03:55.320 --> 0:03:55.760 catching it. 0:03:55.880 --> 0:04:00.480 Yeah, and then you were a ranger I was. 0:04:00.560 --> 0:04:04.000 I was privileged to be a US Army airborne ranger station, 0:04:04.080 --> 0:04:06.560 but did most of my time in northern Italy. We're 0:04:06.600 --> 0:04:10.480 part of the eighty second Airbarnship Post. Oh yeah, that's 0:04:10.520 --> 0:04:13.040 what people say, seriously, like, you know, you were you 0:04:13.080 --> 0:04:15.720 were northern, you were drinking wine and having bred, you know. 0:04:16.200 --> 0:04:19.479 But it was a part of a NATO force there 0:04:19.480 --> 0:04:22.040 at the time. Yeah, so exciting. 0:04:22.279 --> 0:04:25.960 How did you get from there to IBM? 0:04:26.400 --> 0:04:28.960 A long path. As I came out of the military, 0:04:29.160 --> 0:04:36.840 I started manufacturing retail housing and did a quick stint, 0:04:36.839 --> 0:04:40.919 took a leave of absence from industry, and did a 0:04:41.080 --> 0:04:44.240 stint of yet again public service in the state of 0:04:44.240 --> 0:04:48.880 Tennessee with economic development and got a whiff of how 0:04:48.920 --> 0:04:52.360 fun it could be to do things around data and media. 0:04:52.720 --> 0:04:55.680 Started a small media firm what we would now call 0:04:55.680 --> 0:04:59.920 a digital firm, sold it and said I wanted to 0:05:00.080 --> 0:05:02.440 go do it again somewhere, but I want to go 0:05:02.480 --> 0:05:05.119 to a big company. And the family at IBM brought 0:05:05.120 --> 0:05:07.279 me in and yet to let me go. 0:05:07.520 --> 0:05:08.640 That was how many years ago? 0:05:10.520 --> 0:05:14.360 Two decades? Oh wow, So I know I look amazingly young, but. 0:05:14.400 --> 0:05:16.600 Yes, because you must have. 0:05:17.480 --> 0:05:20.400 And IBM was my fifth career and and and I've 0:05:20.520 --> 0:05:22.479 I've enjoyed it since and that's what I what I 0:05:22.520 --> 0:05:25.200 do there, build teams, grow new parts of the company, 0:05:25.440 --> 0:05:28.239 and get to work with some of the most brilliant 0:05:28.240 --> 0:05:29.920 people on the face of the planet, as well as 0:05:29.960 --> 0:05:33.480 partners like like Christy that just keep it exciting. 0:05:33.800 --> 0:05:36.400 Christy, you're I was delighted to learn that you are Canadian? 0:05:36.480 --> 0:05:42.200 Yes here, yeah? But you so you were a consultant 0:05:42.240 --> 0:05:44.200 for a long time a Bane Yes. 0:05:44.520 --> 0:05:47.400 Yeah. I joined Baine Consulting intending to spend a couple 0:05:47.400 --> 0:05:49.560 of years there learn the ropes and then go get 0:05:49.560 --> 0:05:53.000 my first real job. But the value personally to my 0:05:53.040 --> 0:05:54.960 growth and development, and then that we were able to 0:05:55.000 --> 0:05:57.520 bring our clients. I ended up there for sixteen years 0:05:58.080 --> 0:06:02.360 and then post Bane went onto another my first product company, 0:06:02.400 --> 0:06:05.080 a new relic, and then it's come full circle at 0:06:05.120 --> 0:06:08.719 Polota Networks. But at Bain it was all about bringing 0:06:08.760 --> 0:06:12.520 expertise across different industries to help our clients improve whatever 0:06:12.560 --> 0:06:15.520 they needed to improve and bringing that expertise to bear. 0:06:16.160 --> 0:06:18.120 And then you have the product lens and you think, Okay, 0:06:18.120 --> 0:06:20.200 we're going to build the absolute best product to help 0:06:20.320 --> 0:06:23.120 our customers do what they need to get done, and 0:06:23.160 --> 0:06:25.640 then I joined pal Alto about six seven months ago 0:06:26.400 --> 0:06:29.200 in a partnerships role and I'm delighted to be able 0:06:29.240 --> 0:06:32.359 to work with amazing consulting companies like IBM where we 0:06:32.400 --> 0:06:33.160 bring both to bear. 0:06:33.720 --> 0:06:36.880 How long have IBM and Palo Alto Network's been partners? 0:06:37.480 --> 0:06:40.400 So we've been We've been working together for quite quite 0:06:40.400 --> 0:06:43.920 a long time, but we made it official, meaning we 0:06:44.240 --> 0:06:46.400 got married as strategic partners last year. 0:06:46.560 --> 0:06:48.520 Oh I see. So what is it that each of 0:06:48.640 --> 0:06:51.760 you bring to the table? What's each side special? 0:06:51.839 --> 0:06:54.760 So it's great that you asked that because about a 0:06:54.800 --> 0:06:58.720 decade ago, are now CEO Arvin Christ says, you know, 0:06:58.720 --> 0:07:01.320 it wouldn't be great if we has had this one 0:07:01.360 --> 0:07:04.039 focus with what does IBM do and you have this 0:07:04.080 --> 0:07:06.919 whole list, and he says, let's make it simple. We 0:07:07.040 --> 0:07:11.720 are a multi cloud, hybrid cloud AI company. And so 0:07:11.800 --> 0:07:14.600 when you say that, it sounds very simple. But then people, 0:07:14.880 --> 0:07:18.000 what the hell is that? What your hybrid cloud? Well, 0:07:18.680 --> 0:07:21.120 both of those two things have a lot of data involved, 0:07:21.320 --> 0:07:23.920 and a lot of those mean that that data is 0:07:23.920 --> 0:07:27.840 going to sit in multiple places and distributed environments. Well, 0:07:27.880 --> 0:07:31.240 if you're able to tie those things together with multiple partners. 0:07:31.560 --> 0:07:35.680 You also have to make sure that it's secure because 0:07:36.120 --> 0:07:39.280 in the direction that we're going, where data is now 0:07:39.520 --> 0:07:42.000 being consumed in many different places and it is the 0:07:42.040 --> 0:07:46.480 fuel behind AI as we know. Then you say, ah, well, 0:07:47.000 --> 0:07:49.480 who does that well and who does it in a 0:07:49.520 --> 0:07:52.320 way that's getting rid of seams, the seams that could 0:07:52.360 --> 0:07:56.400 be across multiple products, multiple product SATs even And that's 0:07:56.400 --> 0:07:57.360 where Powell comes in. 0:07:58.200 --> 0:08:01.960 I think the canal wisdom in cybersecurity was always you 0:08:02.040 --> 0:08:05.440 need all the new tools, right, you need it every threat. 0:08:05.440 --> 0:08:07.200 It's like, whack them all. Every threat that pops up, 0:08:07.240 --> 0:08:10.720 you get the tool that's purpose built for that specific thing. Well, 0:08:10.760 --> 0:08:13.280 fast forward to you know, the RSA conference this year. 0:08:13.320 --> 0:08:16.920 There were four thousand vendors on the floor. You look 0:08:16.960 --> 0:08:20.240 at an average company, there's hundreds of cybersecurity tools. It 0:08:20.320 --> 0:08:24.680 introduces a level of complexity that is really hard to manage. 0:08:25.040 --> 0:08:30.360 You as a user, query and application right, that query 0:08:30.440 --> 0:08:33.959 can go through a bunch of different pings from one 0:08:33.960 --> 0:08:35.680 cloud to the next. It goes into and out of 0:08:35.679 --> 0:08:38.040 as SaaS application. It may be running along a network, 0:08:38.280 --> 0:08:39.959 you may be accessing it from your phone, which is 0:08:39.960 --> 0:08:42.800 an unmanaged device. It's got to go in and out. 0:08:42.840 --> 0:08:45.600 And if you say, okay, I've got to secure that phone, 0:08:46.200 --> 0:08:48.480 I've got to secure the network, I've got it. Then 0:08:48.480 --> 0:08:50.720 all of a sudden you've got sort of firewalls, software 0:08:50.720 --> 0:08:54.040 and hardwel flows popping up everywhere. You've got cloud security, 0:08:54.600 --> 0:08:56.880 and it's you've probably heard of this concept of zero trust, 0:08:56.880 --> 0:08:58.480 which is every time you have to check and say 0:08:58.480 --> 0:09:00.200 are you allowed in here? Are you allowed in here? 0:09:00.480 --> 0:09:03.040 The number of places that can fall down it just 0:09:03.080 --> 0:09:06.800 becomes overwhelming. So you end up with either alerts firing, 0:09:07.280 --> 0:09:10.120 you know, every two seconds that you have to then 0:09:10.120 --> 0:09:13.160 go investigate in most of which are false positives or 0:09:13.679 --> 0:09:16.959 you miss something right. And so that was the conventionalism 0:09:17.080 --> 0:09:18.719 was we've got to buy all these tools, and now 0:09:18.720 --> 0:09:21.880 you've got overwhelmed CIOs and CSOs with hundreds of tools, 0:09:21.960 --> 0:09:25.120 and Palo Alto strategy has been, look, we're going to 0:09:25.120 --> 0:09:28.160 create a platform where everything can be stitched together, everything 0:09:28.200 --> 0:09:31.760 can speak the same language, and we can sort of 0:09:32.559 --> 0:09:35.520 manage throughout the architecture and watch, you know, this call 0:09:35.600 --> 0:09:39.800 as as it's passing through all these different checkpoints, and 0:09:40.040 --> 0:09:41.560 we can do it in a way that you still 0:09:41.600 --> 0:09:43.440 have the confidence that it's best to breed right, so 0:09:43.480 --> 0:09:46.120 you're not making any trade offs. But it's not so 0:09:46.160 --> 0:09:50.439 simple just to get from the spaghetti to the seamless architecture. 0:09:50.480 --> 0:09:54.000 You need, oftentimes to re engineer your business processes. You 0:09:54.080 --> 0:09:57.240 have to re architect your digital environment. And so that's 0:09:57.280 --> 0:10:00.200 where we partner with a company like IBM to bring 0:10:00.200 --> 0:10:02.280 that expertise and say, we're going to help you not 0:10:02.440 --> 0:10:05.320 just deploy the best cybersecurity architecture, but really get your 0:10:05.400 --> 0:10:08.440 environment ready to have this zero customers as well as. 0:10:08.360 --> 0:10:12.600 All of those players that cross that spaghetti, because when 0:10:12.600 --> 0:10:15.160 you start thinking about all the other partners that you 0:10:15.200 --> 0:10:17.840 work with, if you're you think of an industry perspective, 0:10:17.880 --> 0:10:20.440 you're going to have an ERP. It could be an Oracle, 0:10:20.480 --> 0:10:22.960 it could be an SAP. You're not going to have 0:10:23.000 --> 0:10:24.920 one cloud, as I mentioned, it's going to be possibly 0:10:25.200 --> 0:10:28.760 multiple clouds. You'll have some AWS maybe Microsoft asure and 0:10:28.800 --> 0:10:31.040 then even even some Google in there, and then your 0:10:31.080 --> 0:10:33.840 own that you've built in your private over there, uh, 0:10:34.760 --> 0:10:38.760 some an IBM cloud. You'll have those multiple clouds, and 0:10:38.760 --> 0:10:41.800 then you also will have you know, fit for purpose, Oh, 0:10:41.920 --> 0:10:44.480 I need a I need a salesforce in there for 0:10:44.920 --> 0:10:47.400 my customer focusing I need. I'm doing some graphics, so 0:10:47.440 --> 0:10:49.680 I have Adobe, so I just as I can name 0:10:49.760 --> 0:10:54.840 name name, all of those then have to be re engineered. Seriously. 0:10:55.440 --> 0:10:57.240 I mean, come on, Malcolm, you're gonna sit there you 0:10:57.280 --> 0:11:00.320 think how long that would take. So if you haven't 0:11:00.400 --> 0:11:03.480 done that before, you're going to have to go to 0:11:03.520 --> 0:11:05.560 each one of those individually, or you can work with 0:11:05.880 --> 0:11:08.560 a company that can tie those things together, because we 0:11:08.600 --> 0:11:12.120 are also strategic partners with them. So that's where you 0:11:12.120 --> 0:11:15.640 start to say, Okay, I see how this comes together. 0:11:16.559 --> 0:11:20.080 You have to make sure that your ecosystem is going 0:11:20.080 --> 0:11:22.920 to be stronger than your competitor's ecosystem, and you have 0:11:22.960 --> 0:11:25.320 to be secure in what you're doing because as you 0:11:25.400 --> 0:11:29.000 add more players or products, you create seams, and you 0:11:29.040 --> 0:11:32.160 want to make sure there's fewer seams and that there's 0:11:32.240 --> 0:11:37.120 zero trust across that capability you're building. And that's why 0:11:37.200 --> 0:11:38.840 the compliment between the two companies. 0:11:38.960 --> 0:11:41.000 Well, take a step back from a moment before we 0:11:41.120 --> 0:11:43.840 sort of launch, once get into the specifics of what 0:11:43.960 --> 0:11:47.760 you guys are doing. I'm curious at this moment in 0:11:47.920 --> 0:11:54.240 twenty twenty four, how nervous should we be about cybersecurity? 0:11:54.440 --> 0:11:58.640 So compared it to five years ago or ten years ago. 0:11:59.160 --> 0:12:01.600 Are we are less nervous than you were five years ago? 0:12:01.600 --> 0:12:04.240 Were more nervous? Or all of changes going on right 0:12:04.280 --> 0:12:08.320 now increasing vulnerability or decreasing it? 0:12:08.720 --> 0:12:12.200 I would say Christie, also, I think we share the 0:12:12.240 --> 0:12:16.400 point of view is that it's not necessarily being more nervous. 0:12:16.400 --> 0:12:20.960 I think you should be more prepared because the amounts 0:12:21.440 --> 0:12:25.760 of threat is increasing based on our dependence upon data. 0:12:26.840 --> 0:12:31.160 And that's that's where I think the attention should be placed. 0:12:31.200 --> 0:12:34.640 Is that more and more, especially with the importance of AI, 0:12:35.720 --> 0:12:38.480 that you say, okay, then what's under all that? And 0:12:38.520 --> 0:12:43.240 it's the data, as I said, So knowing that you 0:12:43.280 --> 0:12:44.880 should be more concerned. 0:12:45.800 --> 0:12:49.760 Does the advent of AI and its rapid evolution help 0:12:49.880 --> 0:12:51.680 defense more or offense more? 0:12:52.240 --> 0:12:55.120 I think it's I think it's like any mega trend 0:12:55.160 --> 0:12:59.200 that we've witnessed both. Right, So you think about AI. 0:12:59.320 --> 0:13:03.679 It's great, right in terms of what it's going to 0:13:03.760 --> 0:13:07.080 unlock for productivity, for humanity, but it also makes it 0:13:07.120 --> 0:13:09.720 a whole lot easier to build ransomware. It's a whole 0:13:09.760 --> 0:13:13.120 lot easier to test different ways into a system. Right. 0:13:13.520 --> 0:13:15.280 But I think that's true if you think about like 0:13:15.360 --> 0:13:16.960 the rise of the Internet, right, all of a sudden, 0:13:17.000 --> 0:13:20.720 everyone was putting their data online and you had to 0:13:20.760 --> 0:13:23.240 think of new ways to stay ahead and keep that secure. 0:13:23.280 --> 0:13:25.840 And I don't think AI is any different. You've got 0:13:25.960 --> 0:13:29.400 companies like Palta, partnerships like Powell and IBM that are 0:13:30.640 --> 0:13:34.080 constantly scanning the landscape for not only the current threats, 0:13:34.120 --> 0:13:36.800 but what's next, what's coming around the corner, what's after AI? 0:13:37.440 --> 0:13:39.760 And so I think taking it seriously and being prepared 0:13:39.840 --> 0:13:41.920 is probably the right way of looking at it, as 0:13:41.960 --> 0:13:44.120 opposed to because if you think about it too hard, 0:13:44.160 --> 0:13:46.839 you'll just want to crawl into a corner and stuff 0:13:46.840 --> 0:13:49.920 everything under the mattress. 0:13:50.280 --> 0:13:57.480 I am the CEO of a regional hospital chain, big 0:13:57.640 --> 0:14:02.679 distribute healthcare system, so a ton of data. The consequences 0:14:02.720 --> 0:14:06.640 of being hacked and help for ransom are life and death. 0:14:06.800 --> 0:14:10.400 Life and death. Right littally, when you come so, you 0:14:10.840 --> 0:14:12.720 come down, you sit down with me, and you chat 0:14:12.760 --> 0:14:16.240 with me. Walk me through the kinds of things you 0:14:16.280 --> 0:14:18.840 would tell me about what I need to get safer. 0:14:19.160 --> 0:14:22.360 For example, let's start with one. Is it likely that 0:14:22.400 --> 0:14:24.320 I'm spending too little? Or am I spending money in 0:14:24.360 --> 0:14:25.040 the wrong place. 0:14:25.920 --> 0:14:29.960 Great question. It depends how you've broken it out. If 0:14:30.000 --> 0:14:33.120 you are distributing all of your dollars across a whole 0:14:33.160 --> 0:14:35.720 bunch of different tools, it's likely you're just spending the 0:14:35.760 --> 0:14:38.040 wrong money. And in fact, you know, putting it all 0:14:38.040 --> 0:14:40.800 in one place is a way of potentially saving money 0:14:41.160 --> 0:14:45.000 but keeping your security actually higher. And I'd love to 0:14:45.040 --> 0:14:46.880 hear Jason, how you would approach it. How we would 0:14:46.880 --> 0:14:49.080 approach it, of course, is by saying, you know, what, 0:14:49.080 --> 0:14:52.200 what does your environment look like? You know, do you 0:14:52.240 --> 0:14:56.720 have the connected medical devices into your EMR? Are your 0:14:56.840 --> 0:15:00.360 respirators and ventilators all online? Right? And so we would 0:15:00.360 --> 0:15:03.200 talk about, okay, here's how you get coverage and how 0:15:03.240 --> 0:15:05.720 the coverage of both the firewalls as well as the 0:15:05.800 --> 0:15:09.240 detectors all feedback into your security operation center and you 0:15:09.240 --> 0:15:13.000 can manage it and do your learning with AI and 0:15:13.080 --> 0:15:14.000 keep yourself securing. 0:15:14.040 --> 0:15:16.360 So yeah, and I would say Christy and I would 0:15:16.360 --> 0:15:18.840 go to the same point because if you get under 0:15:19.120 --> 0:15:22.600 what she was just asking, it is your data on 0:15:22.720 --> 0:15:26.840 prem and when it's on prem, how active is it 0:15:26.880 --> 0:15:31.040 across the enterprise? And so that begins the basis for 0:15:31.120 --> 0:15:33.040 the start and then often you're going to say, well, 0:15:33.080 --> 0:15:36.240 we actually take in data from outside, and then we 0:15:36.280 --> 0:15:39.800 also have the circumstances. There's a lot of PII and 0:15:39.840 --> 0:15:45.280 so that personal is the personal information, right, And so 0:15:45.320 --> 0:15:48.640 now you're saying, okay, now, how are we securing that 0:15:48.960 --> 0:15:51.440 and where are we securing it? And so you have 0:15:51.520 --> 0:15:55.680 to start really thinking about the different areas within that 0:15:55.920 --> 0:16:00.240 hospital chain. Are you sharing that amongst your hospitals? And 0:16:00.280 --> 0:16:03.480 now you start to think of if I'm saying no 0:16:03.560 --> 0:16:04.960 to a lot of that, it's like, well, then are 0:16:05.000 --> 0:16:07.680 you as efficient as you want to be? So there 0:16:07.760 --> 0:16:11.160 is that trade off of you know, am I so 0:16:11.320 --> 0:16:14.920 tightly walled that I'm not productive? And so that's where 0:16:14.960 --> 0:16:17.960 we would start to say, what's the outcome that you're 0:16:17.960 --> 0:16:20.160 trying to get to? All Right, maybe you're good, Maybe 0:16:20.200 --> 0:16:22.560 you're you're good with your five locations and you don't 0:16:22.800 --> 0:16:24.960 need to go any further, but maybe you want to 0:16:25.000 --> 0:16:27.000 expand to fifty and by the way, you're going to 0:16:27.080 --> 0:16:29.080 go crossport or you're going to be in Toronto and 0:16:29.200 --> 0:16:32.480 in New York. Okay, well then how do you do that? 0:16:33.360 --> 0:16:36.040 And so I think that it's very easy to start 0:16:36.120 --> 0:16:41.600 jumping into any of the typical situations. But the first 0:16:41.640 --> 0:16:45.960 question that you have to ask you as the hospital CEOs, 0:16:46.400 --> 0:16:49.360 what's your objective? What are you what are you trying 0:16:49.480 --> 0:16:52.040 to do? Because too often what we see is that 0:16:52.400 --> 0:16:55.720 there's some bright, new, shiny thing that everybody wants to 0:16:56.040 --> 0:16:58.440 put in play. You know, it's a sandwich looking for 0:16:58.560 --> 0:17:01.440 lunch and you go, but what is it that you 0:17:01.520 --> 0:17:04.000 want to do as this? Are you doing research? Are 0:17:04.000 --> 0:17:07.680 your research hospital? Are you more consumer oriented? So those 0:17:07.720 --> 0:17:10.119 are the questions you start to ask because they start 0:17:10.160 --> 0:17:13.880 to then tell a story in line with what Christy questions. 0:17:13.920 --> 0:17:16.720 And I think that that's where the again, the complement 0:17:17.240 --> 0:17:19.960 is that instead of just saying, oh, well, that's thanks 0:17:20.040 --> 0:17:23.199 for telling me all this, Malcolm, here's your ten page strategy, 0:17:23.880 --> 0:17:28.399 go find somebody. We have the benefit in IBM. And 0:17:28.440 --> 0:17:30.520 it's probably why I'm still there is you know, we're 0:17:30.640 --> 0:17:33.399 very unique. We're the only company on the planet that 0:17:33.560 --> 0:17:38.679 has a consulting business at scale inside of a technology company, 0:17:39.560 --> 0:17:42.840 and so we have, you know, the left brain, right brain. 0:17:42.920 --> 0:17:45.480 We're able to do that and then we're able to say, okay, 0:17:45.480 --> 0:17:49.280 now which partners are going to be most valuable for 0:17:49.359 --> 0:17:51.719 our clients? What's going to work for you, isn't going 0:17:51.760 --> 0:17:54.119 to work for the manufacturer down the road, isn't going 0:17:54.160 --> 0:17:57.880 to work for the consumer or CpG company across the river. 0:17:59.000 --> 0:18:02.600 Those things are bare very specific. The threats and the 0:18:02.640 --> 0:18:05.800 scenes that I was talking about are very specific. So 0:18:05.920 --> 0:18:08.439 that's where it becomes very valuable to make sure that 0:18:09.400 --> 0:18:12.400 I'm not just giving you some strategy that's generic. 0:18:12.920 --> 0:18:17.720 But everything as a healthcare CEO, everything I have done, 0:18:18.160 --> 0:18:21.520 almost everything I've done over the last ten years, has 0:18:21.600 --> 0:18:24.200 it had the effect of increasing my vulnerability. I want 0:18:24.200 --> 0:18:26.960 to digitize data within the hospital used to be on 0:18:27.000 --> 0:18:30.560 pieces of paper. I want doctors to go home and 0:18:30.680 --> 0:18:32.680 to be able to seamlessly hook into stuff at work 0:18:32.720 --> 0:18:35.199 because they got to do all their paperwork. I want 0:18:35.240 --> 0:18:37.919 to make sure the diabetes people are speaking to the 0:18:38.040 --> 0:18:41.720 organ transplant people. And so isn't that everything I have 0:18:41.840 --> 0:18:45.080 done to kind of keep up with the revolution in healthcare? 0:18:45.480 --> 0:18:47.840 Isn't that also making me more and more vulnerable to 0:18:48.359 --> 0:18:49.000 a bad actor. 0:18:49.160 --> 0:18:51.520 It's such a great question because think about the quality 0:18:51.520 --> 0:18:54.919 of healthcare delivery. Right, So now doctors aren't filling out forms, 0:18:54.960 --> 0:18:57.679 They're spending time with patients, and so the quality of 0:18:57.720 --> 0:19:00.439 care is improving and the vulnerability is improving, and so 0:19:00.480 --> 0:19:05.159 I think that's where having a strong cybersecurity strategy actually 0:19:05.320 --> 0:19:07.600 enables all of that. One of our products is our 0:19:07.640 --> 0:19:10.600 sas product, and we tested it with some business applications, 0:19:10.640 --> 0:19:13.200 and oftentimes the wrap is, oh, security is going to 0:19:13.240 --> 0:19:15.280 slow you down, right, like you have to add a firewall, 0:19:15.320 --> 0:19:19.159 you have to checkpoints. Our product actually increases the velocity 0:19:19.560 --> 0:19:21.720 of your ability to use that application because of the 0:19:21.760 --> 0:19:25.679 way that it is queried through our system as opposed 0:19:25.720 --> 0:19:28.240 to just through the regular network. So it doesn't slow 0:19:28.280 --> 0:19:30.480 it down and in fact, it makes it run more efficiently. 0:19:31.240 --> 0:19:36.479 That's just one minor example. But back to the healthcare question. I, 0:19:36.520 --> 0:19:38.879 as a patient want my doctors accessing all the technology 0:19:38.880 --> 0:19:40.960 and talking to each other and connecting the dots behind 0:19:40.960 --> 0:19:43.560 the scenes. I also want my data to stay private, 0:19:44.119 --> 0:19:49.240 and so having both a consulting partner who understands how 0:19:49.280 --> 0:19:51.720 to ask questions of the environment and of the applications 0:19:51.720 --> 0:19:54.600 you're using, and who understands the industry inside and out, 0:19:55.000 --> 0:19:57.800 and a technology partner that builds and stays ahead of 0:19:57.840 --> 0:20:00.600 all of the different threats come together advise you. I 0:20:00.600 --> 0:20:04.920 think is super important. When you bring in a partner 0:20:04.920 --> 0:20:08.600 like IBM, with a platform like pal Alta that covers 0:20:08.920 --> 0:20:12.720 you know, all the different parts of your environment, you're 0:20:12.760 --> 0:20:16.280 able to say, look, where where are the vulnerabilities in 0:20:16.320 --> 0:20:19.360 the system, Where are the different endpoints that we need 0:20:19.400 --> 0:20:21.280 to have covered, And then just make sure you get 0:20:21.320 --> 0:20:24.920 that breadth of coverage and then you're better able to so, yes, 0:20:24.960 --> 0:20:27.040 you've increased the risk, but then you've mitigated it. 0:20:27.760 --> 0:20:32.119 So to give so before I retire my healthcare analogy, 0:20:32.480 --> 0:20:35.800 because I was thinking about just trying to understand the 0:20:35.840 --> 0:20:40.600 importance of this idea of having a single platform. So 0:20:40.960 --> 0:20:44.240 if this mudtle healthcare network is typical, I've acquired a 0:20:44.240 --> 0:20:46.720 whole series of over the last ten years. I bought 0:20:46.720 --> 0:20:49.560 a hospital over here, some I got some physicians things 0:20:49.560 --> 0:20:52.720 that I snapped up over here. I bought a diagnostics company, 0:20:53.160 --> 0:20:56.560 and so I have all of these legacy systems and 0:20:56.600 --> 0:20:58.760 I had, like you said, maybe I got some stuff 0:20:58.760 --> 0:21:00.920 in the cloud with one company, some stuff with the cloud. 0:21:01.160 --> 0:21:03.840 And what you're saying is the first step is to 0:21:03.920 --> 0:21:07.800 kind of rationalize that put it on a single platform, 0:21:07.840 --> 0:21:11.040 so you understand where your points of weakness are as 0:21:11.040 --> 0:21:13.040 opposed to being blind to your points of weakness. 0:21:14.800 --> 0:21:19.760 There's yes, although anyone who's done any kind of M 0:21:19.760 --> 0:21:22.359 and A knows that that's a long journey, right. So 0:21:22.440 --> 0:21:26.080 I think the first step is just understanding where everything is, 0:21:26.720 --> 0:21:27.960 and then you get on a path and you say, 0:21:27.960 --> 0:21:31.080 where's the biggest risk. Let's neutralize or mitigate that risk 0:21:31.119 --> 0:21:34.400 one at a time. The thing about open end Secure, 0:21:35.160 --> 0:21:37.720 you know, Palo Alto. We keep touting the benefits of 0:21:37.760 --> 0:21:40.439 the platform. Everything on Palo Alto, your risk is going 0:21:40.440 --> 0:21:42.439 to be mitigated and you're going to have the full visibility. 0:21:43.119 --> 0:21:46.480 But you can't get there overnight. And so we've got 0:21:46.720 --> 0:21:50.000 you know, thousands of integrations with other technology companies, including 0:21:50.040 --> 0:21:52.679 our partners, to make sure that we can capture and 0:21:52.880 --> 0:21:57.040 have visibility into those those endpoints in those systems as well. 0:21:57.280 --> 0:21:59.320 And so I think step one is just figure out 0:21:59.320 --> 0:22:01.840 where everything is, get the scan, so politize a couple 0:22:01.880 --> 0:22:03.880 of products where you can kind of deploy and get 0:22:03.920 --> 0:22:06.760 a view of your attack surface. I love the analogy. 0:22:06.920 --> 0:22:09.560 Just like a digital environment is a house, right, and 0:22:09.600 --> 0:22:11.520 so like you have your front door log of course, 0:22:11.760 --> 0:22:13.679 because probably they're going to try the front door first, 0:22:14.440 --> 0:22:15.920