WEBVTT 00:00:00.000 --> 00:00:02.620 Welcome to the GCLine 5G. It's the latest inside 00:00:02.620 --> 00:00:05.280 scoop on everything 5G. We typically talk about 00:00:05.280 --> 00:00:07.459 six topics in 20 minutes, but today we're doing 00:00:07.459 --> 00:00:10.339 a special standalone edition. And we're joined 00:00:10.339 --> 00:00:13.500 by Zscaler, Ken and Nathan. Welcome to our podcast. 00:00:14.599 --> 00:00:16.839 Hey. Good to be here, Will. Thanks. Thank you. 00:00:16.879 --> 00:00:18.640 Hey, so before we get started, let's start with 00:00:18.640 --> 00:00:20.519 you, Nathan. Quick introduction on what you do 00:00:20.519 --> 00:00:23.780 at Zscaler. Yeah. Hey, I run innovation here, 00:00:23.859 --> 00:00:25.699 so I get to look after all the cool new toys 00:00:25.699 --> 00:00:28.120 and figure out what works, what doesn't. And 00:00:28.120 --> 00:00:29.579 yeah, get to find out what's going to be the 00:00:29.579 --> 00:00:31.300 direction for the company over the next five 00:00:31.300 --> 00:00:34.119 to 10 years. Awesome. And Ken, we got to meet, 00:00:34.159 --> 00:00:36.060 I got to meet both of y 'all at Zenith Live, 00:00:36.219 --> 00:00:38.600 but we had a great conversation as well. What 00:00:38.600 --> 00:00:41.280 are you responsible for, Ken? I do the strategy 00:00:41.280 --> 00:00:44.000 on the innovation team, currently focused on 00:00:44.000 --> 00:00:47.600 5G and satellite. Well, we talk about 5G on this 00:00:47.600 --> 00:00:49.979 podcast. We're beginning to talk about 6G as 00:00:49.979 --> 00:00:53.200 well. But let's talk about Zscaler Cellular. 00:00:53.259 --> 00:00:56.520 So I spent time with y 'all at Zenith Live. On 00:00:56.520 --> 00:00:58.840 July 8th, you had the big announcement. Ken, 00:00:59.039 --> 00:01:01.560 I spent a lot of time with you. I went up to 00:01:01.560 --> 00:01:04.819 the show floor. I got a sim as well, and I'm 00:01:04.819 --> 00:01:06.959 going to be playing with that. But maybe, Nathan, 00:01:07.040 --> 00:01:09.459 let's start with you. What is Zscaler Cellular 00:01:09.459 --> 00:01:12.780 all about? Yeah, happy to give some insights. 00:01:12.900 --> 00:01:14.680 So from our point of view, Zscaler Celia really 00:01:14.680 --> 00:01:17.319 is nothing more than the next evolution of connecting 00:01:17.319 --> 00:01:19.959 our customers to their zero trust exchange, their 00:01:19.959 --> 00:01:22.959 policy engine. And what I mean by that is today 00:01:22.959 --> 00:01:25.480 we have client connector for the end users. We 00:01:25.480 --> 00:01:27.620 have edge of network forwarding for machines 00:01:27.620 --> 00:01:30.799 and workloads. And there was a gap, which was 00:01:30.799 --> 00:01:35.099 the devices that are not Wi -Fi or not Ethernet 00:01:35.099 --> 00:01:37.079 connected. The things out in the field, the 4G, 00:01:37.140 --> 00:01:39.859 5G, even. for what it's worth, back to 2G devices 00:01:39.859 --> 00:01:42.519 that customers have. And the crux of that is 00:01:42.519 --> 00:01:45.239 very simple. We enable those devices to connect 00:01:45.239 --> 00:01:48.920 directly into a Zscaler custom policy, and they 00:01:48.920 --> 00:01:51.040 can get their zero trust controls, their protection, 00:01:51.299 --> 00:01:53.939 their visibility, as if they were for end users 00:01:53.939 --> 00:01:56.219 that are in a workload, in a workstation, in 00:01:56.219 --> 00:01:57.980 an office or a building or in a cloud, we can 00:01:57.980 --> 00:01:59.780 now do it for anything that's cellular connected. 00:02:00.000 --> 00:02:01.879 And the goal is to do it anywhere in the world 00:02:01.879 --> 00:02:05.140 for where those devices may exist. Yeah. And 00:02:05.140 --> 00:02:07.640 so Ken, from an innovation standpoint, I think 00:02:07.640 --> 00:02:10.300 this is pretty innovative because all you have 00:02:10.300 --> 00:02:13.860 to do is just use the Zscaler SIM, right? There's 00:02:13.860 --> 00:02:16.539 no overlay. There's no friction associated with 00:02:16.539 --> 00:02:19.139 this. So can you spend a little bit of time on 00:02:19.139 --> 00:02:21.259 kind of the implementation? It's straightforward, 00:02:21.919 --> 00:02:25.599 interesting, tricky, all at the same time. You 00:02:25.599 --> 00:02:28.300 have a SIM. SIM really is just a way of uniquely 00:02:28.300 --> 00:02:33.719 identifying some device to a telco system. telco 00:02:33.719 --> 00:02:35.680 devices don't attach to any network till you 00:02:35.680 --> 00:02:38.500 stick a sim in them or an e -sim in them and 00:02:38.500 --> 00:02:41.060 once you do it says oh you're this are you allowed 00:02:41.060 --> 00:02:43.479 to be on my network do i know who you are do 00:02:43.479 --> 00:02:46.939 you have a rate plan how do i charge you are 00:02:46.939 --> 00:02:49.319 you my customer are you someone else's customer 00:02:50.199 --> 00:02:53.180 And that's great. But you also will go through 00:02:53.180 --> 00:02:56.740 the telco system, which has cybersecurity ranging 00:02:56.740 --> 00:03:00.539 from well -known, easily hacked from the 4G days, 00:03:00.800 --> 00:03:03.479 3G days, right up to 5G, where it's supposed 00:03:03.479 --> 00:03:06.860 to address most, but as we find out, not all 00:03:06.860 --> 00:03:10.719 areas of cybersecurity. So we said, we already 00:03:10.719 --> 00:03:13.500 do zero trust cybersecurity at Zscaler. We keep 00:03:13.500 --> 00:03:15.580 attackers out of your system. We keep your IP, 00:03:15.719 --> 00:03:18.949 your crown jewels in your system. He said, could 00:03:18.949 --> 00:03:21.590 we do something at the sim level? And Nathan 00:03:21.590 --> 00:03:23.590 had been playing. I love Nathan playing around. 00:03:23.770 --> 00:03:25.810 True experimentally said, hey, Ken, look at this. 00:03:26.150 --> 00:03:29.090 Wow. I would love to curse on this podcast, but 00:03:29.090 --> 00:03:32.030 I'm not going to because that was how excited 00:03:32.030 --> 00:03:35.729 I got. I said, yeah, this is what the market's 00:03:35.729 --> 00:03:38.009 going to want. You can stick it in any, because 00:03:38.009 --> 00:03:40.030 normally it's like telco device. All you got 00:03:40.030 --> 00:03:42.120 to put a client on it. My thing can't take a 00:03:42.120 --> 00:03:45.419 client. Why not? It's like a drone or an autonomous 00:03:45.419 --> 00:03:47.819 vehicle. And there's real -time systems. And 00:03:47.819 --> 00:03:50.719 I can't just stick some enterprise client on 00:03:50.719 --> 00:03:53.460 in the middle of the network stack and say, yeah, 00:03:53.460 --> 00:03:55.139 this is all going to work just fine. Because 00:03:55.139 --> 00:03:58.139 in truth, it doesn't. But if you have the SIM 00:03:58.139 --> 00:04:01.240 and do the zero trust right from the transmitter 00:04:01.240 --> 00:04:04.719 back in the internet. That's when it works great. 00:04:04.860 --> 00:04:07.099 You don't have to modify anything. You don't 00:04:07.099 --> 00:04:10.219 have to put clients on. At some level, you don't 00:04:10.219 --> 00:04:13.259 need MDM even, mobile device management, although 00:04:13.259 --> 00:04:15.860 it's useful for some really interesting things, 00:04:15.960 --> 00:04:18.199 which we may or may not be able to talk about 00:04:18.199 --> 00:04:20.800 on this podcast. There, I'm teasing because I'm 00:04:20.800 --> 00:04:23.360 going to let Nathan talk about it, maybe. Hey, 00:04:23.420 --> 00:04:27.060 Anshul is our end device expert, and I know he's 00:04:27.060 --> 00:04:29.540 probably dying to ask the application questions. 00:04:29.779 --> 00:04:33.350 Take it away. Yeah, I would love to know what 00:04:33.350 --> 00:04:36.329 are some of the end device applications for this 00:04:36.329 --> 00:04:38.509 Z -scale or cellular and how are they different 00:04:38.509 --> 00:04:40.769 from other applications that are in use today? 00:04:41.870 --> 00:04:44.269 Yeah, I think I'll jump in with this one because 00:04:44.269 --> 00:04:45.850 it's been a lot of fun actually dealing with 00:04:45.850 --> 00:04:48.310 the types of customers and their ecosystem of 00:04:48.310 --> 00:04:50.370 devices. And one thing that I will say is that 00:04:50.370 --> 00:04:54.009 every day we are completely surprised as to where... 00:04:54.560 --> 00:04:57.240 a cellular modem has been deployed. And it is 00:04:57.240 --> 00:04:59.480 incredible range. And to give you bookends, and 00:04:59.480 --> 00:05:01.259 then I'll give you specifics, we have things 00:05:01.259 --> 00:05:04.079 like every vending machine has been SIM enabled 00:05:04.079 --> 00:05:07.699 since probably 1997. Just doing stock taking, 00:05:07.980 --> 00:05:10.579 sending information about how many cans of Coke 00:05:10.579 --> 00:05:12.699 have been sold or whatever else. The other end 00:05:12.699 --> 00:05:15.319 of the scale, which I find ironic, given that 00:05:15.319 --> 00:05:17.240 I'm Australian and that Australia was a prison 00:05:17.240 --> 00:05:20.399 colony, is ankle trackers for prisoners. They 00:05:20.399 --> 00:05:22.279 are all SIM connected as well. So you kind of 00:05:22.279 --> 00:05:25.129 have this giant spectrum. By the way, To continue 00:05:25.129 --> 00:05:27.569 that joke, I leave my ankle tracker in Australia. 00:05:27.850 --> 00:05:29.410 When I go back home, they reattach it. And when 00:05:29.410 --> 00:05:31.769 I fly out, they take it off. But the diversity 00:05:31.769 --> 00:05:34.290 is huge. And so where we're seeing this become 00:05:34.290 --> 00:05:36.470 really interesting for our customers is in... 00:05:36.839 --> 00:05:40.100 three main areas. One is headless devices, similar 00:05:40.100 --> 00:05:42.019 to what Ken mentioned, like drones, but think 00:05:42.019 --> 00:05:44.439 about things like devices that are out, maybe 00:05:44.439 --> 00:05:47.139 a sensor on a highway or a rail infrastructure 00:05:47.139 --> 00:05:50.899 or track and tracing of a package. Those are 00:05:50.899 --> 00:05:52.879 the things where information is critically needing 00:05:52.879 --> 00:05:55.759 to be connected and sent to a destination. And 00:05:55.759 --> 00:05:59.629 often those destinations are private. So that 00:05:59.629 --> 00:06:01.990 would normally mean historically a VPN on the 00:06:01.990 --> 00:06:05.589 client side or private APN from a telco. And 00:06:05.589 --> 00:06:07.829 what we're saying here is actually we're not 00:06:07.829 --> 00:06:10.189 reliant on the telcos to backhaul traffic into 00:06:10.189 --> 00:06:13.009 a private APN into a data center. You go straight 00:06:13.009 --> 00:06:15.350 in from that SIM into the Zscaler policy engine 00:06:15.350 --> 00:06:17.829 and then Zscaler says, oh, that's private. Send 00:06:17.829 --> 00:06:20.629 that via Zscaler private access. So it's a direct 00:06:20.629 --> 00:06:22.670 hop, not a backhaul, which is a big advantage 00:06:22.670 --> 00:06:25.680 for those private workloads. There's probably 00:06:25.680 --> 00:06:28.019 two other very interesting examples of call -out. 00:06:28.079 --> 00:06:31.120 One is the direct -to -internet. So devices, 00:06:31.180 --> 00:06:32.939 again, these are devices sitting out on the side 00:06:32.939 --> 00:06:35.680 of the highway or rail or whatever, and they're 00:06:35.680 --> 00:06:37.459 being misused as well. People are figuring out 00:06:37.459 --> 00:06:39.959 that if I crack open the box that's not protected 00:06:39.959 --> 00:06:42.779 by anything, there may be a padlock. I open it 00:06:42.779 --> 00:06:44.399 up, I can pull the SIM out, I can stick it in 00:06:44.399 --> 00:06:47.860 my device. What can I do with it? And so everything 00:06:47.860 --> 00:06:49.740 coming to us goes through the Z -scale policy, 00:06:49.899 --> 00:06:52.860 and we can say. YouTube and Netflix and all those 00:06:52.860 --> 00:06:54.740 other high bandwidth things that consume the 00:06:54.740 --> 00:06:57.660 services get blocked. And you only allow the 00:06:57.660 --> 00:06:59.399 destination on the internet is needed. Maybe 00:06:59.399 --> 00:07:02.500 it's a green grass IoT sensor or something. And 00:07:02.500 --> 00:07:05.459 the third part is, this is one where I think 00:07:05.459 --> 00:07:09.939 that we have a very unique position. First of 00:07:09.939 --> 00:07:11.980 all, Zscaler doesn't allow any network -to -network 00:07:11.980 --> 00:07:13.680 connections. We don't allow IP -to -IP connectivity. 00:07:14.120 --> 00:07:16.879 We have to go through a policy engine. If you 00:07:16.879 --> 00:07:18.540 think about one of these devices that's remote. 00:07:19.050 --> 00:07:21.110 and you need to support it, log into it and fix 00:07:21.110 --> 00:07:23.790 something, that would require, in the historical 00:07:23.790 --> 00:07:27.029 private APN world, some sort of routable network 00:07:27.029 --> 00:07:29.550 path and some ingress location someone can VPN 00:07:29.550 --> 00:07:31.490 into or connect to a network and then move across. 00:07:32.029 --> 00:07:34.970 We don't believe in that. So we have built it 00:07:34.970 --> 00:07:37.610 so that you only connect to the Zscaler policy 00:07:37.610 --> 00:07:40.269 engine from wherever you are in the world. And 00:07:40.269 --> 00:07:42.829 if policy says you can get access, we will actually 00:07:42.829 --> 00:07:45.350 broker the connection between that initiated 00:07:45.350 --> 00:07:48.790 user or thing or process back to the actual SIM 00:07:48.790 --> 00:07:50.730 initiated system. So whatever it may be, it could 00:07:50.730 --> 00:07:54.389 be a SSH on a sensor. It could be a web policy 00:07:54.389 --> 00:07:56.850 engine on some sort of, I don't know, portal 00:07:56.850 --> 00:07:58.829 or whatever it could be. And we'll enable that 00:07:58.829 --> 00:08:00.610 to happen, meaning we're only allowing authorized 00:08:00.610 --> 00:08:03.089 connections into the device. So there's no way 00:08:03.089 --> 00:08:06.209 to get access in and out. without going through 00:08:06.209 --> 00:08:08.370 the Zscaler policy engine. I think that's a crux 00:08:08.370 --> 00:08:10.410 that differentiates us between anything else. 00:08:10.449 --> 00:08:12.949 We're not backhauling it to a network to apply 00:08:12.949 --> 00:08:15.449 controls. We're putting it directly in line between 00:08:15.449 --> 00:08:18.949 Zscaler, the SIM going to its destination and 00:08:18.949 --> 00:08:20.629 the destinations or the other sources coming 00:08:20.629 --> 00:08:23.509 into the app or the SIM as a destination. So 00:08:23.509 --> 00:08:25.470 we become that broker of control and policy, 00:08:25.649 --> 00:08:27.689 which again, to my earlier point, we did for 00:08:27.689 --> 00:08:29.470 users already and did for workloads. This is 00:08:29.470 --> 00:08:32.139 now the next extension. So what you've built 00:08:32.139 --> 00:08:35.440 is a very mature platform, the zero trust exchange, 00:08:35.740 --> 00:08:39.470 right? But I'm wondering, Ken. Just the sheer 00:08:39.470 --> 00:08:41.549 number of devices. So one of the biggest challenges 00:08:41.549 --> 00:08:43.669 that mobile network operators face are just the 00:08:43.669 --> 00:08:45.970 sheer numbers of devices. And so Nathan was just 00:08:45.970 --> 00:08:48.769 describing a lot of IoT use cases, right? And 00:08:48.769 --> 00:08:53.950 that's huge. And IoT tends to create massive 00:08:53.950 --> 00:08:56.669 threat surfaces and porous threat surfaces because 00:08:56.669 --> 00:08:59.190 traditionally standards have been all over the 00:08:59.190 --> 00:09:02.330 place. But so Ken, from your perspective, does 00:09:02.330 --> 00:09:05.970 what Zscaler has created with Zscaler Cellular, 00:09:06.070 --> 00:09:10.139 will it scale? to support these massive number 00:09:10.139 --> 00:09:14.419 of devices? Short answer is yes. The joke is, 00:09:14.440 --> 00:09:16.919 what do you think the scaler in Zscaler is? It 00:09:16.919 --> 00:09:19.940 meant the Zenith scaling. We blow through what? 00:09:20.120 --> 00:09:23.440 I think it's now 600 billion transactions a day 00:09:23.440 --> 00:09:26.379 for our customers. And we're not at the limit. 00:09:26.480 --> 00:09:29.240 We can push huge amounts of data. You can do 00:09:29.240 --> 00:09:31.279 things like, and the fun thing about the SIMs 00:09:31.279 --> 00:09:33.919 I love is you can do things like buy a security 00:09:33.919 --> 00:09:37.379 camera that has a 5G connection only on it, stick 00:09:37.379 --> 00:09:40.480 the SIM in, move the thing around, no cables. 00:09:40.559 --> 00:09:42.840 You just need the power supply or solar power 00:09:42.840 --> 00:09:47.899 for it. And you're handling high bandwidth, 4K 00:09:47.899 --> 00:09:50.840 video, able to do instant object recognition 00:09:50.840 --> 00:09:55.299 at the edge or anywhere else. You can take gigantic 00:09:55.299 --> 00:09:59.809 mining equipment. that needs to be remotely operated 00:09:59.809 --> 00:10:02.730 in the bottom of a shaft several tens of thousands 00:10:02.730 --> 00:10:05.129 of meters deep, stick a stick in it, and you 00:10:05.129 --> 00:10:09.330 have a secure two -way connection no matter what. 00:10:09.509 --> 00:10:13.190 This is absolutely amazing. You get cybersecurity 00:10:13.190 --> 00:10:16.070 and controllability and ability to reach in and 00:10:16.070 --> 00:10:18.830 administer a device with a little piece of plastic 00:10:18.830 --> 00:10:21.769 or a digital certificate. I don't need clients. 00:10:21.809 --> 00:10:25.309 I've remoted the client away. I just need the 00:10:25.309 --> 00:10:28.340 connection. Yeah, that's where I was just really 00:10:28.340 --> 00:10:30.899 blown away when I spent time with both of you 00:10:30.899 --> 00:10:33.399 at Zenith Live. It's just the fact that it's 00:10:33.399 --> 00:10:36.019 just, it's a sim. And we've talked about some 00:10:36.019 --> 00:10:38.360 very compelling use cases, Ken. You were alluding 00:10:38.360 --> 00:10:40.240 to this. There are some other use cases that 00:10:40.240 --> 00:10:43.100 I'm sure are, and we, Anshul and I have talked 00:10:43.100 --> 00:10:46.840 about the application of 5G in military applications. 00:10:47.059 --> 00:10:49.639 And like, so the Marine Corps is using private 00:10:49.639 --> 00:10:52.179 5G networks to manage logistics and that sort 00:10:52.179 --> 00:10:54.299 of thing. Anshul, do you have a question you 00:10:54.299 --> 00:10:56.669 want to? shoot either one of their ways. I want 00:10:56.669 --> 00:10:59.409 to monopolize the competition. No, I'm really 00:10:59.409 --> 00:11:01.970 curious about, there's a lot of enterprise applications 00:11:01.970 --> 00:11:03.629 that you guys have talked about, a lot of IoT, 00:11:03.909 --> 00:11:07.090 but being the consumer guy, do you see there 00:11:07.090 --> 00:11:09.070 being any consumer applications that could benefit 00:11:09.070 --> 00:11:11.669 from this? There you go. It's a good question. 00:11:11.789 --> 00:11:14.889 Ken, do you mind if I go first? Oh, please. Absolutely. 00:11:16.379 --> 00:11:20.139 Ken will be the closer on this stuff. As always. 00:11:20.279 --> 00:11:22.379 So I think the key thing is from an enterprise 00:11:22.379 --> 00:11:25.460 user point of view, we've already got the software 00:11:25.460 --> 00:11:29.320 on an iOS, Android, Mac, Windows device that 00:11:29.320 --> 00:11:30.799 we can do. And it provides different insights. 00:11:31.159 --> 00:11:34.779 It's a software layer that allows for also diversity 00:11:34.779 --> 00:11:36.200 of connectivity. So if you have your phone and 00:11:36.200 --> 00:11:39.000 it goes to Wi -Fi, we can enable that to be securely 00:11:39.000 --> 00:11:40.519 provided over there. Obviously, the cellular 00:11:40.519 --> 00:11:43.720 service is provided solely within cellular. But 00:11:43.720 --> 00:11:46.169 with that being said. we do have some advantages 00:11:46.169 --> 00:11:47.710 and one we haven't alluded to and i probably 00:11:47.710 --> 00:11:49.769 i'm just remiss and not even saying this is that 00:11:49.769 --> 00:11:52.830 we allow for the cellular connected devices to 00:11:52.830 --> 00:11:56.809 be on multiple carrier networks globally so that 00:11:56.809 --> 00:11:58.809 if one carrier is not available for whatever 00:11:58.809 --> 00:12:01.269 reason maybe you're out of range maybe the carrier 00:12:01.269 --> 00:12:03.629 goes down or maybe you change countries or whatever 00:12:03.629 --> 00:12:06.269 it may be we have built it to be a multi -roaming 00:12:06.269 --> 00:12:09.370 sim so there is a mechanism that could help some 00:12:09.370 --> 00:12:11.230 enterprises when it comes to maybe perhaps roaming 00:12:11.230 --> 00:12:13.429 to new countries sending them to countries that 00:12:13.429 --> 00:12:16.639 are maybe not the most well -renowned for security. 00:12:16.960 --> 00:12:19.259 So we can provide control, we can provide security 00:12:19.259 --> 00:12:21.399 for those users and connectivity for those users 00:12:21.399 --> 00:12:23.100 when they go somewhere. So yes, there's an enterprise 00:12:23.100 --> 00:12:25.440 user space aspect, but I wouldn't look at it 00:12:25.440 --> 00:12:27.679 as being a replacement for the client -side software 00:12:27.679 --> 00:12:29.940 because obviously client enables user authentication. 00:12:30.100 --> 00:12:32.259 You've got code to assess the posture of the 00:12:32.259 --> 00:12:34.919 device, all those values. Now, those two things 00:12:34.919 --> 00:12:37.139 together, yeah, that becomes very interesting, 00:12:37.279 --> 00:12:39.720 the cellular and the client -side. But I would 00:12:39.720 --> 00:12:41.580 say the enterprise space beyond, there's a lot 00:12:41.580 --> 00:12:43.740 more that we're looking at. This is where I can 00:12:43.740 --> 00:12:45.120 throw to Ken and talk about some of the stuff 00:12:45.120 --> 00:12:46.960 that we're doing, we're thinking about doing, 00:12:47.019 --> 00:12:49.419 and now we're exploring in and around, as you 00:12:49.419 --> 00:12:51.639 said, the kind of the government space as well. 00:12:51.659 --> 00:12:53.240 Ken, I'll let you continue from there. Yeah. 00:12:53.860 --> 00:12:56.740 Government is simply a different kind of big 00:12:56.740 --> 00:12:59.480 organization. They have this, a lot of the needs 00:12:59.480 --> 00:13:03.009 overlap. We look at government. and defense use 00:13:03.009 --> 00:13:07.610 cases, energy use cases, and they map very closely 00:13:07.610 --> 00:13:10.210 to what we see in the enterprise. You've got 00:13:10.210 --> 00:13:12.730 autonomous vehicles, you've got a remote vehicle, 00:13:12.889 --> 00:13:16.159 you've got people out in the field. who as far 00:13:16.159 --> 00:13:18.159 as an IT system, you could say they look like 00:13:18.159 --> 00:13:20.600 salespeople. They're operating semi -independently 00:13:20.600 --> 00:13:22.840 and they need to work on a variety of networks. 00:13:23.159 --> 00:13:25.659 We can do things for customers like I'd like 00:13:25.659 --> 00:13:28.059 to push huge amounts of data all the time. I 00:13:28.059 --> 00:13:30.460 need an all you can eat data plan. It has to 00:13:30.460 --> 00:13:32.940 work everywhere in the world. Or I'm not going 00:13:32.940 --> 00:13:35.259 to push a lot of data. I want the cheapest possible 00:13:35.259 --> 00:13:38.980 plan. We can rotate people to that. Or I don't 00:13:38.980 --> 00:13:40.899 care if it's an intermittent connection because 00:13:40.899 --> 00:13:43.860 I cache data so I can go with a very inexpensive 00:13:43.860 --> 00:13:48.700 and possibly spotty service provider that meets 00:13:48.700 --> 00:13:52.340 their needs. Or I can have the always on high 00:13:52.340 --> 00:13:56.559 volume, high bandwidth provider and with a different 00:13:56.559 --> 00:13:59.750 type of contract. And because we're Zscaler, 00:13:59.750 --> 00:14:02.350 we can look into things like, okay, you want 00:14:02.350 --> 00:14:05.529 all you can eat for 4K video all the time for 00:14:05.529 --> 00:14:08.409 security. Great. If you're okay with going with 00:14:08.409 --> 00:14:12.190 one provider, two providers compared to the several 00:14:12.190 --> 00:14:16.250 hundred, you can get a much better deal. It's 00:14:16.250 --> 00:14:19.509 telco. There are so many different plans. And 00:14:19.509 --> 00:14:22.429 because we have so many different relationships 00:14:22.429 --> 00:14:25.629 with telco vendors around the world, we can offer. 00:14:26.080 --> 00:14:29.419 a wide variety of options to customers you can't 00:14:29.419 --> 00:14:34.019 get on your own. That's massive amounts of data 00:14:34.019 --> 00:14:37.360 for global customers. You get some really interesting 00:14:37.360 --> 00:14:41.559 rates. Yeah, I bet. And I was just speaking with 00:14:41.559 --> 00:14:44.840 Verizon recently and their leader that's leading 00:14:44.840 --> 00:14:48.019 their IoT business. And we talked about security. 00:14:48.200 --> 00:14:51.320 I didn't bring this up because I was pre -briefed 00:14:51.320 --> 00:14:53.639 and had to wait until the announcement on July 00:14:53.639 --> 00:14:56.419 8th. One thing, getting back to Anshul's point 00:14:56.419 --> 00:14:58.860 on consumer, I think Nathan, you and I were talking 00:14:58.860 --> 00:15:01.159 about this at Zenith Live was like, you could 00:15:01.159 --> 00:15:03.820 potentially use this solution to, if you're, 00:15:03.840 --> 00:15:07.240 let's say you're, you want to be anonymous, right? 00:15:07.379 --> 00:15:09.320 And you're roaming from country to country, right? 00:15:09.519 --> 00:15:12.740 This is going through the Zscaler exchange. And 00:15:12.740 --> 00:15:15.279 so you could potentially anonymize that. So it 00:15:15.279 --> 00:15:17.600 could be a wealthy person. It could be a famous 00:15:17.600 --> 00:15:20.059 person. It could be Taylor Swift. I don't know. 00:15:20.100 --> 00:15:22.139 So there's that application too, right? Yeah, 00:15:22.139 --> 00:15:24.059 absolutely. My daughter was just listening to 00:15:24.059 --> 00:15:25.840 Taylor Swift on the radio this morning. So there 00:15:25.840 --> 00:15:27.399 you go. No, but actually it's an interesting 00:15:27.399 --> 00:15:29.820 point because yes, ultimately the traffic is 00:15:29.820 --> 00:15:33.570 coming to Zscaler. and we are in control of where 00:15:33.570 --> 00:15:35.789 that goes. So think of it very similar to any 00:15:35.789 --> 00:15:38.110 other version from Zscaler. All the initiating 00:15:38.110 --> 00:15:39.970 source is going to, the network path is going 00:15:39.970 --> 00:15:42.289 to see is traffic going to a gateway. That gateway 00:15:42.289 --> 00:15:45.110 is Zscaler. So from there, we can do whatever 00:15:45.110 --> 00:15:46.610 we want with the traffic and that's up to the 00:15:46.610 --> 00:15:48.389 customers and we can build it up for various 00:15:48.389 --> 00:15:50.370 different types of use cases. But absolutely, 00:15:50.490 --> 00:15:52.309 that means that we're in that path, we own the 00:15:52.309 --> 00:15:53.870 path, we can decide what to do with the path. 00:15:54.210 --> 00:15:56.779 And again... built on policy base for the customer 00:15:56.779 --> 00:15:59.320 to want to achieve. But that's extremely powerful, 00:15:59.419 --> 00:16:00.759 Will, as you alluded to. There's things that 00:16:00.759 --> 00:16:02.700 can be done. Today, our customers do that with 00:16:02.700 --> 00:16:04.860 edge of network forwarding. They do it with Client 00:16:04.860 --> 00:16:07.159 Connector. On the client side of things, the 00:16:07.159 --> 00:16:09.360 one thing I will say, and I need to obviously 00:16:09.360 --> 00:16:12.179 make the statement, use Zscaler properly. Don't 00:16:12.179 --> 00:16:14.860 break any local laws because we can't be held 00:16:14.860 --> 00:16:16.899 responsible for those things. But yeah, of course 00:16:16.899 --> 00:16:18.600 you can do it. And the example I'll give you, 00:16:18.659 --> 00:16:21.649 which is just a fun one for me, is that... I 00:16:21.649 --> 00:16:24.009 have my personal policy engine for Zscaler. I 00:16:24.009 --> 00:16:25.970 have my kids run the software on their devices 00:16:25.970 --> 00:16:29.850 to access our Minecraft server at home. So anywhere 00:16:29.850 --> 00:16:32.090 in the world, we can log in using Client Connector 00:16:32.090 --> 00:16:34.009 from their laptops to access our own Minecraft 00:16:34.009 --> 00:16:36.659 server. But if I want to join... I could maybe 00:16:36.659 --> 00:16:39.899 throw Zscaler cellular sim in my device and have 00:16:39.899 --> 00:16:42.179 policy available to do that too. Now, nobody 00:16:42.179 --> 00:16:43.820 else can connect to that Minecraft server. No 00:16:43.820 --> 00:16:46.159 one else can see that Minecraft server. No one 00:16:46.159 --> 00:16:48.039 else knows it exists. No one even knows the connection. 00:16:48.159 --> 00:16:49.860 They just see this connection going to Zscaler. 00:16:50.039 --> 00:16:52.659 They have no idea about it. So yes, my policy 00:16:52.659 --> 00:16:54.500 is built so I can have a private Minecraft server 00:16:54.500 --> 00:16:56.740 with my kids. But you could do other things as 00:16:56.740 --> 00:16:59.909 well. Again, don't break any laws. I'm impressed 00:16:59.909 --> 00:17:01.990 that you have a Minecraft server in your home. 00:17:02.070 --> 00:17:05.109 I bet Anshul has one as well. He's a total techie. 00:17:05.230 --> 00:17:07.250 Hey, guys, it's been a great conversation. But 00:17:07.250 --> 00:17:09.549 as we sort of wind things down, let's talk about 00:17:09.549 --> 00:17:12.069 availability, right? So you're in preview right 00:17:12.069 --> 00:17:14.710 now. Ken, when should we expect to see Zscaler 00:17:14.710 --> 00:17:18.009 Cellular hit the mainstream here in sort of general 00:17:18.009 --> 00:17:21.890 availability? He's holding one off. If I didn't 00:17:21.890 --> 00:17:24.460 have this. blurry background you'd be seeing 00:17:24.460 --> 00:17:26.400 i'm just going to cover the code on it because 00:17:26.400 --> 00:17:29.000 who knows how higher resolution you got you can 00:17:29.000 --> 00:17:32.519 get them right now okay yeah oh look i have more 00:17:32.519 --> 00:17:36.230 than one Yeah. So I'm willing to give you that. 00:17:36.230 --> 00:17:39.049 We can organize that and give you a specific 00:17:39.049 --> 00:17:41.450 example. We are live, limited availability for 00:17:41.450 --> 00:17:43.970 customers until August 1st, general availability. 00:17:44.230 --> 00:17:46.430 Anyone can buy from us. You can buy from us now. 00:17:46.509 --> 00:17:48.329 It's just a matter of process more than anything 00:17:48.329 --> 00:17:50.250 else. So we are fully available for customers 00:17:50.250 --> 00:17:52.369 to be able to operate this today. So we're really 00:17:52.369 --> 00:17:55.069 happy to hear any inquiry at all. Great. You 00:17:55.069 --> 00:17:58.509 got two weeks. And for our viewers and listeners, 00:17:59.029 --> 00:18:02.289 can they go to zscaler .com to learn more or 00:18:02.289 --> 00:18:04.349 can you share? that information yeah there's 00:18:04.349 --> 00:18:06.670 a there's actually a sub page of zscaler .com 00:18:06.670 --> 00:18:09.130 for our zscaler cellular just do a quick google 00:18:09.130 --> 00:18:10.690 search you'll find it but otherwise we'll provide 00:18:10.690 --> 00:18:13.109 a link afterwards if you will but also they can 00:18:13.109 --> 00:18:16.450 reach out to us at srm at zscaler .com it's really 00:18:16.450 --> 00:18:19.369 easy and we'll be happy to fill any inbound questions 00:18:19.369 --> 00:18:21.670 discussions happy to talk about partnerships 00:18:21.670 --> 00:18:24.250 talk about how to deploy it all those things 00:18:24.250 --> 00:18:26.150 we're open to every conversation because we think 00:18:26.150 --> 00:18:28.390 there's as you pointed out well this is the really 00:18:28.890 --> 00:18:31.930 rich opportunity for us to really provide that 00:18:31.930 --> 00:18:33.910 next level of control and protection for our 00:18:33.910 --> 00:18:36.089 customers around the world, which is extremely 00:18:36.089 --> 00:18:39.109 exciting. I love it. When you think about 5G, 00:18:39.130 --> 00:18:42.309 5G new radio from a standard perspective, it's 00:18:42.309 --> 00:18:45.490 got encryption improvements over LTE, but this 00:18:45.490 --> 00:18:48.029 just provides another layer, another level of 00:18:48.029 --> 00:18:50.769 protection. At the end of the day, cybersecurity 00:18:50.769 --> 00:18:54.589 is about a layered approach. So Nathan, Ken, 00:18:54.730 --> 00:18:56.109 I want to thank you for your time. It's been 00:18:56.109 --> 00:18:58.390 a great conversation. Anshul? Why don't you take 00:18:58.390 --> 00:19:01.269 us home? Absolutely. We hope our viewers and 00:19:01.269 --> 00:19:02.849 listeners found this week's topic interesting. 00:19:03.069 --> 00:19:05.190 If anyone would like to provide insights on a 00:19:05.190 --> 00:19:08.089 future 5G topic for a future podcast, please 00:19:08.089 --> 00:19:10.930 reach out to us on social media. Will's at WillTownTac 00:19:10.930 --> 00:19:13.589 and I'm Anshul Saag. And Ken and Nathan are both 00:19:13.589 --> 00:19:16.569 at Zscaler. So thanks a lot for listening. And 00:19:16.569 --> 00:19:18.150 don't forget to rate us and subscribe.