WEBVTT - Palo Alto Networks CEO Talks CyberArk Acquisition

0:00:02.520 --> 0:00:06.519
<v Speaker 1>Bloomberg Audio Studios, podcasts, radio.

0:00:06.720 --> 0:00:09.520
<v Speaker 2>News, Nikesh, I think we get right into the numbers, right.

0:00:09.640 --> 0:00:14.040
<v Speaker 2>The situation is for your EPs guidance come down, revenue

0:00:14.080 --> 0:00:16.159
<v Speaker 2>is beaten, and so I'm trying to understand, like the

0:00:16.280 --> 0:00:19.000
<v Speaker 2>environment that you're in, you know, what is it that

0:00:19.000 --> 0:00:22.000
<v Speaker 2>that's weighing on profitability for the balance of this year.

0:00:23.320 --> 0:00:24.720
<v Speaker 3>Well, first of all, nice to see you, Ed, and

0:00:24.760 --> 0:00:27.000
<v Speaker 3>thank you for having me on. I think the market

0:00:27.080 --> 0:00:29.960
<v Speaker 3>is not paying attention to our numbers carefully. We just

0:00:30.040 --> 0:00:32.000
<v Speaker 3>completed our largest acquisition.

0:00:31.560 --> 0:00:33.880
<v Speaker 4>In cyber Arc. We had a great quarter.

0:00:34.080 --> 0:00:38.440
<v Speaker 3>Our numbers are across every known consensus metric. The market

0:00:38.479 --> 0:00:40.680
<v Speaker 3>is not understanding that our guidance for the next two

0:00:40.720 --> 0:00:43.920
<v Speaker 3>quarters includes cyber Arc. If you take the consensus cyber

0:00:44.040 --> 0:00:47.400
<v Speaker 3>Arc and ours, we are actually getting above the collective consensus.

0:00:47.479 --> 0:00:49.920
<v Speaker 3>But the market hasn't understood the dilution of shares, so

0:00:49.960 --> 0:00:57.560
<v Speaker 3>I think they have it wrongs. Actually, the board I always.

0:00:57.520 --> 0:00:59.040
<v Speaker 4>Above consens across the board.

0:00:59.240 --> 0:01:01.760
<v Speaker 3>These are the post market bots which haven't figured this out.

0:01:02.480 --> 0:01:04.800
<v Speaker 2>I always enjoy you joining us on the network. You're

0:01:04.840 --> 0:01:08.199
<v Speaker 2>always honest, You're always very specific about M and A. Right,

0:01:09.200 --> 0:01:11.280
<v Speaker 2>the math that people are doing is the guide for

0:01:11.319 --> 0:01:14.320
<v Speaker 2>next gen ARR growth is fifty three to fifty four

0:01:14.319 --> 0:01:18.440
<v Speaker 2>percent cyber arc chronosphere, but that would suggest that that

0:01:18.720 --> 0:01:22.360
<v Speaker 2>organically growth is neared a sort of twenty percent. Can

0:01:22.400 --> 0:01:24.280
<v Speaker 2>you see the math that they're doing.

0:01:24.760 --> 0:01:26.360
<v Speaker 3>Yes, I see the map, but I think if they

0:01:26.440 --> 0:01:31.560
<v Speaker 3>listen carefully, cyber Arc computes ARR differently from us, So

0:01:31.600 --> 0:01:34.120
<v Speaker 3>we've had to trip out a few hundred million dollars

0:01:34.160 --> 0:01:36.760
<v Speaker 3>of cyber RKERR. Hence, if you dig that out and

0:01:36.800 --> 0:01:39.920
<v Speaker 3>netted back, we're actually doing better collectively than we're guided.

0:01:39.959 --> 0:01:42.880
<v Speaker 3>This all clarify by tomorrow morning as the market opens,

0:01:42.880 --> 0:01:45.920
<v Speaker 3>but I think the market hasn't understood the comments are

0:01:45.920 --> 0:01:49.520
<v Speaker 3>CFO made around the fact that our computation of ARR

0:01:50.080 --> 0:01:50.680
<v Speaker 3>is different.

0:01:50.800 --> 0:01:53.760
<v Speaker 4>It's more conservative than cyber Arc. Cyber arcs is more

0:01:54.000 --> 0:01:55.240
<v Speaker 4>as aggressive than ours.

0:01:55.480 --> 0:01:58.360
<v Speaker 1>If you turn down their ARR down to the way

0:01:58.440 --> 0:02:01.640
<v Speaker 1>we compute it, actually actively, our RIRR guidance is a

0:02:01.760 --> 0:02:05.680
<v Speaker 1>success of what we previously guide it organically individually.

0:02:07.320 --> 0:02:11.960
<v Speaker 2>On the call, you mentioned a nine figure chronosphed deal.

0:02:12.639 --> 0:02:16.120
<v Speaker 2>You didn't name the customer. Somebody from the cell side

0:02:16.120 --> 0:02:18.400
<v Speaker 2>asked you about the deal, they didn't ask you to

0:02:18.480 --> 0:02:19.320
<v Speaker 2>name the customer.

0:02:19.600 --> 0:02:23.160
<v Speaker 4>Who's the customer in a cat it's a popular LLLM

0:02:23.200 --> 0:02:23.480
<v Speaker 4>out there.

0:02:23.520 --> 0:02:25.720
<v Speaker 3>I think more importantly, what is there to understand is

0:02:25.720 --> 0:02:28.600
<v Speaker 3>that Cronis Fair is a net new startup. They came

0:02:28.680 --> 0:02:31.000
<v Speaker 3>up with a new way of doing observability which is

0:02:31.040 --> 0:02:34.480
<v Speaker 3>much more cost effective, much more efficient, and can scale

0:02:34.520 --> 0:02:37.000
<v Speaker 3>to the volume that elms are putting out there. That's

0:02:37.040 --> 0:02:39.040
<v Speaker 3>the reason we bought the company, the fact that two

0:02:39.080 --> 0:02:41.680
<v Speaker 3>hundred and fifty engineers can build something so amazing that

0:02:41.840 --> 0:02:46.600
<v Speaker 3>provides a leap frog opportunity against current players in observability.

0:02:47.000 --> 0:02:50.079
<v Speaker 3>That's what we bought them for. They've been under tests

0:02:50.160 --> 0:02:53.600
<v Speaker 3>for many months with this LLM. They've fully been accepted

0:02:53.600 --> 0:02:56.519
<v Speaker 3>across the platform. They will be replacing an incumbent vendor,

0:02:56.960 --> 0:02:59.560
<v Speaker 3>and as that continues to grow, we expect to see

0:02:59.560 --> 0:03:02.600
<v Speaker 3>continued growth of RR for that one customer. But additionally,

0:03:02.800 --> 0:03:04.720
<v Speaker 3>obviously knos Fair is talking to a whole bunch of

0:03:04.720 --> 0:03:07.919
<v Speaker 3>net new customers who are looking for either get off there,

0:03:08.120 --> 0:03:12.840
<v Speaker 3>do it yourself observability platforms or the place expensive observable

0:03:12.919 --> 0:03:14.919
<v Speaker 3>platforms that they've subscribed to in the past.

0:03:15.800 --> 0:03:19.400
<v Speaker 2>Nikesh like observability is so core to what is happening

0:03:19.480 --> 0:03:23.200
<v Speaker 2>Inegentic right now, if we move on the assumption that

0:03:23.280 --> 0:03:27.080
<v Speaker 2>the customer is one of the key frontier labs, would

0:03:27.120 --> 0:03:28.880
<v Speaker 2>you just talk a little bit about why they came

0:03:28.919 --> 0:03:32.600
<v Speaker 2>to you for security rather than do security themselves.

0:03:32.600 --> 0:03:32.639
<v Speaker 3>That.

0:03:33.160 --> 0:03:36.160
<v Speaker 2>I know that might sound like silly question, but actually

0:03:36.640 --> 0:03:38.760
<v Speaker 2>you know a lot of the frontier labs have teams

0:03:38.840 --> 0:03:42.200
<v Speaker 2>right they're looking at this issue themselves. They see value

0:03:42.240 --> 0:03:44.520
<v Speaker 2>clearly in what parallelto networks is offering.

0:03:45.600 --> 0:03:48.960
<v Speaker 4>Well, the number observability is beyond the model. Right.

0:03:49.000 --> 0:03:51.520
<v Speaker 3>The model LM people are focused on making sure their

0:03:51.520 --> 0:03:52.680
<v Speaker 3>model is amazing.

0:03:52.360 --> 0:03:54.000
<v Speaker 4>It does all the things that are expected to do.

0:03:54.040 --> 0:03:55.800
<v Speaker 3>But observability is to look at it from an end

0:03:55.800 --> 0:03:58.520
<v Speaker 3>to end perspective to see how do they make sure

0:03:58.560 --> 0:04:01.280
<v Speaker 3>that the customers are theirs who are using these things

0:04:01.480 --> 0:04:04.600
<v Speaker 3>and the usage continues to double almost every quarter. How

0:04:04.600 --> 0:04:06.640
<v Speaker 3>do they make sure that all their systems, our low

0:04:06.720 --> 0:04:10.160
<v Speaker 3>latency are working perfectly and there's nothing in the entire

0:04:10.280 --> 0:04:12.600
<v Speaker 3>end to end delivery chain that is underperforming.

0:04:12.640 --> 0:04:14.040
<v Speaker 4>So that's what observability does.

0:04:14.200 --> 0:04:16.400
<v Speaker 3>The reason they're coming to us is because they're busy

0:04:16.440 --> 0:04:19.279
<v Speaker 3>building the best models, applying their AI research to the models.

0:04:19.480 --> 0:04:22.039
<v Speaker 3>We're busy with Thronosphair making sure that the end to

0:04:22.120 --> 0:04:25.080
<v Speaker 3>end proposition works and there is very low latency.

0:04:25.080 --> 0:04:26.000
<v Speaker 4>By the way, this app.

0:04:26.080 --> 0:04:28.720
<v Speaker 3>This is true for not just LLLM, this is true

0:04:28.760 --> 0:04:31.240
<v Speaker 3>for every consumer app there is out there ability to

0:04:31.279 --> 0:04:34.440
<v Speaker 3>take Uber, door, Dash or YouTube. Every one of these

0:04:34.760 --> 0:04:38.279
<v Speaker 3>has to have an underpinning observability platform to make sure

0:04:38.320 --> 0:04:40.960
<v Speaker 3>that it's fully available ninety nine point nine nine percent

0:04:41.000 --> 0:04:44.200
<v Speaker 3>of the time, so that because every minute it is

0:04:44.240 --> 0:04:47.640
<v Speaker 3>not working at the capability and the latency that is

0:04:47.640 --> 0:04:49.279
<v Speaker 3>required is lost revenue.

0:04:50.200 --> 0:04:53.359
<v Speaker 2>Nickish very quickly your acquired KOI. The idea is greater

0:04:53.520 --> 0:04:57.640
<v Speaker 2>visibility into AI threats. But just succinctly, what problem did

0:04:57.640 --> 0:04:59.520
<v Speaker 2>that solve for you on the team? What are you getting?

0:05:00.320 --> 0:05:02.320
<v Speaker 3>Yeah, look, I think if you look at the adoption

0:05:02.440 --> 0:05:05.480
<v Speaker 3>of AI and at the enterprise end, you were seeing

0:05:05.560 --> 0:05:08.200
<v Speaker 3>a tremendous amount of adoption in vibecoding. People are using

0:05:08.240 --> 0:05:12.960
<v Speaker 3>cloud code, Cursor, Codex, and many many open source coding platforms.

0:05:13.000 --> 0:05:15.520
<v Speaker 3>As they use it, all that action is happening at

0:05:15.520 --> 0:05:19.000
<v Speaker 3>the endpoint, at the developer laptop, and that's where that's

0:05:19.040 --> 0:05:22.680
<v Speaker 3>an uncovered area of security. You have to protect that laptop,

0:05:22.760 --> 0:05:25.600
<v Speaker 3>that endpoint or the developer to ensure that you can

0:05:25.640 --> 0:05:27.600
<v Speaker 3>deliver code safely and security.

0:05:27.960 --> 0:05:30.040
<v Speaker 4>Coy saw the opportunity inn here and a half ago.

0:05:30.400 --> 0:05:34.040
<v Speaker 3>They build a capability, they have hot people are adopting

0:05:34.040 --> 0:05:36.880
<v Speaker 3>them across the board. Anyone who's trying to use vibecoding,

0:05:36.920 --> 0:05:39.320
<v Speaker 3>anybody's trying to use get on this recording bandwagon.

0:05:39.400 --> 0:05:42.719
<v Speaker 4>Find efficiencies, need that security at the end point. This

0:05:42.839 --> 0:05:45.359
<v Speaker 4>is different than other endpoint security. Both US and.

0:05:45.279 --> 0:05:48.520
<v Speaker 3>Another place in the industry sell called ADR. This is

0:05:48.640 --> 0:05:51.360
<v Speaker 3>very specific to endpoint security for agentic capability.

0:05:51.480 --> 0:05:54.440
<v Speaker 4>That's what COY does. So that's the reason we acquired COY.

0:05:55.400 --> 0:05:58.599
<v Speaker 2>A Keshra pala alto Network CEO, jumping straight from the

0:05:58.600 --> 0:06:00.560
<v Speaker 2>earning school to bringing back television