WEBVTT - Quick bite: Which cybersecurity trend will dominate 2025?

0:00:00.960 --> 0:00:04.360
<v Speaker 1>You're listening to a Shazy's podcast, could you tell us

0:00:04.360 --> 0:00:06.399
<v Speaker 1>a little bit more around the trains with saying the cybersecurity,

0:00:06.640 --> 0:00:10.760
<v Speaker 1>there's a statistic in our predictions that eighty percent of

0:00:10.800 --> 0:00:14.200
<v Speaker 1>breaches are now happening in the cloud, and so I

0:00:14.240 --> 0:00:17.840
<v Speaker 1>think that is going to continue to ramp up. And

0:00:17.880 --> 0:00:20.400
<v Speaker 1>if you think about all the cloud service providers, so

0:00:20.400 --> 0:00:23.680
<v Speaker 1>all the usual suspects of Google, Aws, Azure, and we

0:00:23.760 --> 0:00:26.920
<v Speaker 1>have this what's called a shared responsibility model in that

0:00:27.960 --> 0:00:31.200
<v Speaker 1>they have their own security. However, most companies also have

0:00:31.640 --> 0:00:38.520
<v Speaker 1>another security that is implemented. But that whole shared responsibility

0:00:38.520 --> 0:00:41.760
<v Speaker 1>model is becoming quite interesting from a cloud perspective, just

0:00:41.760 --> 0:00:46.680
<v Speaker 1>because when something does go wrong, then the line's not

0:00:46.760 --> 0:00:50.120
<v Speaker 1>always like let's say, as an example, you decide with

0:00:50.600 --> 0:00:54.320
<v Speaker 1>share Ziase that you're not going to have any other security,

0:00:54.360 --> 0:00:55.560
<v Speaker 1>You're just going to go all in with one of

0:00:55.560 --> 0:00:59.680
<v Speaker 1>the cloud service providers, and then something happens, Chances are

0:01:00.280 --> 0:01:02.279
<v Speaker 1>the cloud the CSP is probably going to say, well,

0:01:02.280 --> 0:01:04.360
<v Speaker 1>it's not my problem. We did what we did. Our

0:01:04.760 --> 0:01:07.679
<v Speaker 1>part of the responsible piece for that you should have

0:01:07.760 --> 0:01:11.959
<v Speaker 1>had X y Z in there. So that one's quite interesting.

0:01:12.959 --> 0:01:16.959
<v Speaker 1>I'd also say the prevalence of what we were talking

0:01:16.959 --> 0:01:20.120
<v Speaker 1>about earlier with jen AI and LMS and where that's going.

0:01:20.680 --> 0:01:23.319
<v Speaker 1>We have to be thinking about fighting AI with AI.

0:01:23.880 --> 0:01:28.319
<v Speaker 1>If you're a company who has is doing something from

0:01:28.319 --> 0:01:32.640
<v Speaker 1>a cyber perspective, and that who whatever organization that you're

0:01:32.680 --> 0:01:36.080
<v Speaker 1>working with, that they have not invested in using AI

0:01:36.280 --> 0:01:39.160
<v Speaker 1>and machine learning tools to have that type of automation,

0:01:40.600 --> 0:01:42.880
<v Speaker 1>you're going to be in a really, really world of

0:01:42.959 --> 0:01:47.880
<v Speaker 1>hurt because you cannot fight that with a human. You've

0:01:47.920 --> 0:01:51.000
<v Speaker 1>got to go and make the hopefully keep the AI

0:01:51.120 --> 0:01:54.520
<v Speaker 1>and machine learning and everything else smarter than what the

0:01:54.520 --> 0:01:57.240
<v Speaker 1>bad actors are doing. But you absolutely have to fight

0:01:57.280 --> 0:02:00.000
<v Speaker 1>AI with AI. Has there been a big steep hop

0:02:00.280 --> 0:02:03.960
<v Speaker 1>envestment into the AI space, Absolutely, yeah, one hundred percent.

0:02:04.080 --> 0:02:09.560
<v Speaker 1>So we've got a few different categories, but it's precision AI,

0:02:09.720 --> 0:02:13.600
<v Speaker 1>so we've actually that's our term that we've trademarked, and

0:02:14.160 --> 0:02:18.000
<v Speaker 1>from a generative AI perspective, then it's making sure that

0:02:18.680 --> 0:02:21.600
<v Speaker 1>you are able to understand exactly where things are coming

0:02:21.600 --> 0:02:24.400
<v Speaker 1>from and that not only the integrity of the AI

0:02:24.800 --> 0:02:28.919
<v Speaker 1>is correct, but also that it's secure. And so those

0:02:28.960 --> 0:02:31.560
<v Speaker 1>are the things in that we also talked earlier about

0:02:32.000 --> 0:02:35.120
<v Speaker 1>cloud and developers, and because you'll know a lot of

0:02:35.160 --> 0:02:39.360
<v Speaker 1>developers that are grabbing things to develop now through AI,

0:02:39.800 --> 0:02:42.800
<v Speaker 1>So we're making sure that that's secure and we have

0:02:43.480 --> 0:02:46.680
<v Speaker 1>it's an AI security posture assessment, so we can go

0:02:46.720 --> 0:02:50.040
<v Speaker 1>into an organization and say we're going to run some

0:02:50.120 --> 0:02:52.679
<v Speaker 1>tests and diagnostics through and go and do something and

0:02:52.919 --> 0:02:55.200
<v Speaker 1>basically be able to come back and say, this is

0:02:55.400 --> 0:02:58.959
<v Speaker 1>your security posture from an AI perspective. So if you

0:02:59.040 --> 0:03:00.480
<v Speaker 1>hit to summarize what you say, I think should be

0:03:00.480 --> 0:03:03.640
<v Speaker 1>top of mind from Vista's for listening. We're not thinking

0:03:03.639 --> 0:03:06.720
<v Speaker 1>about cybersecurity. What would that be? So one thing I

0:03:06.760 --> 0:03:10.560
<v Speaker 1>haven't talked about. We do think twenty twenty five is

0:03:10.680 --> 0:03:13.120
<v Speaker 1>the year of the browser. And what I mean by

0:03:13.120 --> 0:03:18.000
<v Speaker 1>that is such a high percentage of work is done

0:03:18.120 --> 0:03:21.520
<v Speaker 1>in a browser if you think about it. And part

0:03:21.560 --> 0:03:24.120
<v Speaker 1>of one of the ways that we've addressed that is

0:03:24.120 --> 0:03:26.760
<v Speaker 1>we acquired a company about a year ago and now

0:03:26.800 --> 0:03:29.400
<v Speaker 1>it's been automatically integrated in so we all use it

0:03:29.480 --> 0:03:33.320
<v Speaker 1>as well. It's called Prisma Access Browser and it basically

0:03:33.360 --> 0:03:37.280
<v Speaker 1>can tighten down anything. So within your organization, if you

0:03:37.280 --> 0:03:41.200
<v Speaker 1>have contractors or you've got BYOD, basically whenever you're from

0:03:41.200 --> 0:03:43.720
<v Speaker 1>a shares use perspective to say, Okay, we know that

0:03:43.800 --> 0:03:47.560
<v Speaker 1>this is safe, this is secure whenever they're working on

0:03:47.560 --> 0:03:50.680
<v Speaker 1>our stuff because we've locked down the browser in the past.

0:03:51.120 --> 0:03:53.600
<v Speaker 1>That was kind of a bit of sprawl. So if

0:03:53.640 --> 0:03:57.320
<v Speaker 1>I were an investor, I'd probably be having a look

0:03:57.360 --> 0:04:00.480
<v Speaker 1>around that. It's a big bat investment. Something we just

0:04:00.520 --> 0:04:02.680
<v Speaker 1>trust and use, isn't it exactly? And that's the thing.

0:04:02.880 --> 0:04:06.440
<v Speaker 1>It's yeah, you're spot on it. It's something that I

0:04:06.480 --> 0:04:08.840
<v Speaker 1>think a lot of us trust our phones and trust

0:04:09.360 --> 0:04:12.360
<v Speaker 1>all kinds of different things. And but yeah, just that

0:04:12.480 --> 0:04:16.320
<v Speaker 1>security perspective, that's just something else to kind of think about.

0:04:16.560 --> 0:04:19.159
<v Speaker 1>Investing involves the risk you might lose the money you

0:04:19.160 --> 0:04:22.480
<v Speaker 1>start with. We recommend talking to a licensed financial advisor.

0:04:23.160 --> 0:04:26.960
<v Speaker 1>We also recommend reading product disclosure documents before deciding to invest.