>>from New York. It's the Q covering Escape. 19. >>Welcome back to the Cube coverage here in New York City for the first inaugural multi cloud conference called Escape, where in New York City was staying in New York, were not escaping from New York were in New York. It's all about multi Cloud, and we're here. Lisa Marie Nancy, developer advocate for Port Works, and Eric Conn, vice president of Products Works. Welcome back. Q. >>Thank you, John. Good to see >>you guys. So, um, whenever the first inaugural of anything, we want to get into it and find out why. Multi clouds certainly been kicked around. People have multiple clouds, but is there really multi clouding going on? So this seems to be the theme here about setting the foundation, architecture and data of the two kind of consistent themes. What shared guys take Eric, What's your take on this multi cloud trend? Yeah, >>I think it's something we've all been actively watching for a couple years, and suddenly it is becoming the thing right? So every we just had ah, customer event back in Europe last week, and every customer there is already running multi cloud. It's always something on their consideration. So there's definitely it's not just a discussion topic. It's now becoming a practical reality. So this event's been perfect because it's both the sense of what are people doing, What are they trying to achieve and also the business sense. So it's definitely something that is not necessarily mainstream, but it's becoming much more how they're thinking about building all their applications. Going forward, >>you know, you have almost two camps in the world. Want to get your thoughts on this guy's Because, like you have cloud native and people that are cloud native, they love it. They born the cloud that get it. Everything's cracking along. The developers air on Micro Service's They're agile train with their own micro service's. Then you got the hybrid I t. Trying to be hybrid developer, right? So you kind of have to markets coming together. So to me, I see multi cloud as kind of a combination of old legacy Data center types of I t with cloud native, not just ops and dead. But how about like trying to build developer teams inside enterprises? This seems to be a big trend, and multi club fits into that because now the reality is that I got azure. I got Amazon. Well, let's take a step back and think about the architecture. What's the foundation? So that to me, is more my opinion. But I want to get your thoughts and reactions that because if it's true, that means some new thinking has to come around around. What's the architecture? What are you trying to do? What's the workloads behavior outcome look like? What's the work flows? So there's a whole nother set of conversations that happened. >>I agree. I think the thing that the fight out there right now that we want to make mainstream is that it's a platform choice, and that's the best way to go forward. So it's still an active debate. But the idea could be I want to do multi club, but I'm gonna lock myself into the Cloud Service is if that's the intent or that's the design architecture pattern. You're really not gonna achieve the goals we all set out to do right, So in some ways we have to design ourselves or have the architecture that will let us achieve the business schools that were really going for and that really means from our perspective or from a port works perspective. There's a platform team. That platform team should run all the applications and do so in a multi cloud first design pattern. And so from that perspective, that's what we're doing from a data plan perspective. And that's what we do with Kubernetes etcetera. So from that idea going forward, what we're seeing is that customers do want to build a platform team, have that as the architecture pattern, and that's what we think is going to be the winning strategy. >>Thank you. Also, when you have the definition of cod you have to incorporate, just like with hybrid I t the legacy applications. And we saw that you throughout the years those crucial applications, as we call them People don't always want them to refer to his legacy. But those are crucial applications, and our customers were definitely thinking about how we're gonna run those and where is the right places it on Prem. We're seeing that a lot too. So I think when we talk about multi cloud, we also talk about what What is in your legacy? What is it? Yeah, I >>like I mean I use legacy. I think it's a great word because I think it really puts nail in the coffin of that old way because remember, if you think about some of the large enterprises, these legacy applications, they've been optimized for hardware and optimize their full stack. They've been build up from the ground up, so they're cool. They're running stuff, but it doesn't always translate to see a new platform designed point. So how do you mean Containers is great fit for their Cooper names. Obviously, you know is the answer. We you guys see that as well, but okay, I can keep that and still get this design point. So I guess what I want to ask you guys, as you guys are digging into some of the customer facing conversations, what are they talking about? The day talking about? The platform? Specifically? Certainly, on the security side, we're seeing everyone running away from buying tools to thinking about platforms. What's the conversation like on the cloud side >>way? Did a talk are multiplied for real talk at Barcelona? Q. Khan put your X three on Sudden. Andrew named it for reals of Izzy, but we really wanted to talk about multiplied in the real world. And when we said show of hands in Barcelona, who's running multi cloud? It was very, very few. And this was in, what, five months? Four months ago? Whereas maybe our customers are just really super advanced because of our 100 plus customers. At four words, we Eric is right. A lot of them are already running multi cloud or if not their plan, in the planning stage right now. So even in the last +56 months, this has become a reality. And we're big fans of communities. I don't know if you know Eric was the first product manager for Pernetti. Hey, he's too shy to say it on Dhe. So yeah, and we think, you know, and criminal justice to be the answer to making all They caught a reality right now. >>Well, I want to get back into G, K, E and Cooper. Very notable historic moment. So congratulations, But to your point about multi cloud, it's interesting because, you know, having multiple clouds means things, right? So, for instance, if I upgrade to office 3 65 and I kill my exchange server, I'm essentially running azure by their definition. If I'm building it, stack on AWS. I'm a native, this customer. Let's just say I want to do some tensorflow or play with big table or spanner on Google. Now >>we have three >>clouds now they're not. So they have work clothes, specific objectives. I am totally no problem. I see that like for the progressive customers, some legacy be to be people who like maybe they put their toe in the cloud. But anyone doing meaningful cloud probably has multiple clouds. But that's workload driven when you get into tying them together and is interesting. And I think that's where I think you guys have a great opportunity in this community because if open source convene the gateway to minimize the lock in and when I say lock and I mean like locking them propriety respect if his value their great use it. But if I want to move my data out of the Amazon, >>you brought up so many good points. So let me go through a few and Lisa jumping. I feel like locking. People don't wanna be locked >>in at the infrastructure level. So, like you said, if >>there's value at the higher levels of Stack, and it helps me do my business faster. That's an okay thing to exchange, but it is just locked in and it's not doing anything. They're that's not equal exchange, right, So there's definitely a move from infrastructure up the platform. So locking in >>infrastructure is what people are trying to move away from. >>From what we see from the perspective of legacy, there is a lot of things happening in industry that's pretty exciting of how legacy will also start to running containers. And I'm sure you've seen that. But containers being the basis you could run a BM as well. And so that will mean a lot for in terms of how V EMS can start >>to be matched by orchestrators like kubernetes. So that is another movement for legacy, and I wanted to acknowledge that point >>now, in terms of the patterns, there are definitely applications, like a hybrid pattern where connect the car has to upload all its data once it docks into its location and move it to the data center. So there are patterns where the workflow does move the ups are the application data between on Prem into a public cloud, for instance, and then coming back from that your trip with Lisa. There is also examples where regulations require companies to enterprise is to be able to move to another cloud in a reasonable time frame. So there's definitely a notion of Multi Cloud is both an architectural design pattern. But it's also a sourcing strategy, and that sourcing strategy is more regulation type o. R. In terms of not being locked in. And that's where I'm saying it's all those things. I'd >>love to get your thoughts on this because I like where you're going with this because it kind of takes it to a level of okay, standardization, kubernetes nights, containers, everyone knows what that is. But then you start talking about a P I gateways, for instance, right? So if I'm a car and I have five different gateways on my device, I ot devices or I have multiple vendors dealing with control playing data that could be problematic. I gotta do something like that. So I'm starting. Envision them? I just made that news case up, but my point is is that you need some standards. So on the a p I side was seeing some trends there. One saying, Okay, here's my stuff. I'll just pass parameters with FBI State and stateless are two dynamics. What do you make of that? What, What? What has to happen next to get to that next level of happiness and goodness? Because Bernays, who's got it, got it there, >>right? I feel that next level. I feel like in Lisa, Please jump. And I feel like from automation perspective, Kubernetes has done that from a P I gateway. And what has to happen next. There's still a lot of easy use that isn't solved right. There's probably tons of opportunities out there to build a much better user experience, both from the operations point of view and from what I'm trying to do is an intense because what people aren't gonna automate right now is the intent. They automate a lot of the infrastructure manual tasks, and that's goodness. But from how I docked my application, how the application did it gets moved. We're still at the point of making policy driven, easy to use, and I think there's a lot of opportunities for everyone to get better there. That's like low priority loving fruitcake manual stuff >>and communities was really good at the local food. That's a really use case that you brought up. Really. People were looking at the data now and when you're talking about persistent mean kun is his great for stateless, but for state full really crucial data. So that's where we really come in. And a number of other companies in the cloud native storage ecosystem come in and have really fought through this problem and that data management problem. That's where this platform that Aaron was talking to that >>state problem. Talk about your company. I want to go back to to, um, Google Days. Um, many war stories around kubernetes will have the same fate as map reduce. Yeah, the debates internally at Google. What do we do with it? You guys made the good call. Congratulations on doing that. What was it like to be early on? Because you already had large scale. You were already had. Borg already had all these things in place. Um, it wasn't like there was what was, >>Well, a few things l say one is It was intense, right? It was intense in the sense that amazing amount of intelligence amazing amount of intent, and right back then a lot of things were still undecided, right? We're still looking at how containers or package we're still looking at how infrastructure kit run and a lot of service is were still being rolled out. So what it really meant is howto build something that people want to build, something that people want to run with you and how to build an ecosystem community. A lot of that the community got was done very well, right? You have to give credit to things like the Sig. A lot of things like how people like advocates like Lisa had gone out and made it part of what they're doing. And that's important, right? Every ecosystem needs to have those advocates, and that's what's going well, a cz ah flip side. I think there's a lot of things where way always look back, in which we could have done a few things differently. But that's a different story for different. Today >>I will come back in the studio Palop of that. I gotta ask you now that you're outside. Google was a culture shock. Oh my God! People actually provisioning software provisioning data center culture shock when there's a little >>bit of culture shock. One thing is, and the funny thing is coming full circle in communities now, is that the idea of an application? Right? The idea of what is an application eyes, something that feels very comfortable to a lot of legacy traditional. I wanna use traditional applications, but the moment you're you've spent so much time incriminates and you say, What's the application? It became a very hard thing, and I used to have a lot of academic debates. Where is saying there is no application? It's It's a soup of resources and such. So that was a hard thing. But funny thing is covered, as is now coming out with definitions around application, and Microsoft announced a few things in that area to so there are things that are coming full circle, but that just shows how the movement has changed and how things are becoming in some ways meeting each other halfway. >>Talk about the company, what you guys are doing. Take a moment. Explain in context to multi cloud. We're here. Port works. What's the platform? It's a product. What's the value proposition? What's the state of the company. >>So the companies? Uh well, well, it's grown from early days when Lisa and I joined where we're probably a handful now. We're in four or five cities. Geography ease over 100 people over 150 customers and there. It's been a lot of enterprises that are saying, like, How do I take this pattern of doing containers and micro service is And how do I run it with my mission? Critical business crinkle workloads. And at that point, there is no mission critical business critical workload that isn't stable so suddenly they're trying to say, How do I run These applications and containers and data have different life cycles. So what they're really looking for is a data plane that works with the control planes and how controlled planes are changing the behavior. So a lot of our technology and a lot of our product innovation has been around both the data plane but a storage control plane that integrates with a computer controlled plane. So I know we like to talk about one control plane. There's actually multiple control planes, and you mentioned security, right? If I look at how applications are running way after now securely access for applications, and it's no longer have access to the data. Before I get to use it, you have to now start to do things like J W. T. Or much higher level bearer tokens to say, I know how to access this application for this life cycle for this use case and get that kind of resiliency. So it's really around having that storage. More complexity absolutely need abstraction >>layers, and you got compute. Look, leading work there. But you gotta have >>software to do it from a poor works perspective. Our products entirely software right down loans and runs using kubernetes. And so the point here is we make remarries able to run all the staple workloads out of the box using the same comment control plane, which is communities. So that's the experiences that we really want to make it so that Dev Ops teams can run anywhere close. And that's that's in some ways been part of the mix. Lisa, >>we've been covering Dev up, going back to 2010. Remember when I first was hanging around San Francisco 2008 joint was coming out the woodwork and all that early days and you look at the journey of how infrastructures code We talked about that in 2008 and now we'll get 11 years later. Look at the advancements you've been through this now The tipping point. It's just seems like this wave is big and people are on it. The developers air getting it. It's a modern renaissance of application developers, and the enterprises it's happening in the enterprise is not just like the nerds Tier one, the Alfa Geeks or >>the Cloud native. It's happening in the >>everyone's on board this time, and you and I have been in the trenches in the early stages of many open source projects. And I think with with kubernetes Arab reference of community earlier, I'm super proud to be running the world's largest CNC F for user group. And it's a great community, a diverse community, super smart people. One of my favorite things about working for works is we have some really smart engineers that have figured out what companies want, how to solve problems, and then we'll go creative. It'll open source projects. We created a project called autopilot, really largely because one of our customers, every who's in the G s space and who's running just incredible application. You can google it and see what the work they're doing. It's all there publicly, Onda We built, you know, we built an open source project for them to help them get the most out of kubernetes. We can say so. There's a lot of people in the community system doing that. How can we make communities better halfway make commitments, enterprise grade and not take years to do that? Like some of the other open source projects that we worked on, it took. So it's a super exciting time to be here, >>and open source is growing so fast now. I mean, just think about how these projects being structured. Maur and Maur projects are coming online and user price, but a lot more vendor driven projects to use be mostly and used, but now you have a lot of vendors who are users. So the line is blurring between Bender User in Open source is really fascinating. >>Well, you look at the look of the landscape on the C N. C f. You know the website. I mean, it's what 400 that are already on board. It's really important. >>They don't have enough speaking slasher with >>right. I know, and it's just it. It is users and vendors. Everybody's in this community together. It's one of things that makes it super exciting. And it it's how we know this is This was the right choice for us to base this on communities because that's what everybody, you guys >>are practically neighbors. So we're looking for seeing the studio. Palo Alto Eric, I want to ask you one final question on the product side. Road map. What you guys thinking As Kubernetes goes, the next level state, a lot of micro service is observe abilities becoming a key part of it, Obviously, automation, configuration management things are developing fast. State. What's the What's the road map for you guys? >>For us, it's been always about howto handle the mission critical and make that application run seamlessly. And then now we've done a lot of portability. So disaster recovery has been one of the biggest things for us is that customers are saying, How do I do a hybrid pattern back to your earlier question of running on Prem and in Public Cloud and do a d. R. Pale over into some of the things at least, is pointing out that we're announcing soon is non series autopilot in the idea, automatically managing applications scale from a volume capacity. And then we're actually going to start moving a lot more into some of the what you do with data after the life cycle in terms of backup and retention. So those are the things that everyone's been pushing us and the customers are all asking for. You >>know, I think data they were back in recovery is interesting. I think that's going to change radically. And I think we look at the trend of how yeah, data backup and recovery was built. It was built because of disruption of business, floods, our gains, data center failure. But I think the biggest disruptions ransomware that malware. So security is now a active disruptor. So it's not like it after the hey, if we ever have, ah, fire, we can always roll back. So you're infected and you're just rolling back infected code. That's a ransomware dream. That's what's going on. So I think data protection it needs to be >>redefined. What do you think? Absolutely. I think there's a notion of How do I get last week's data last month? And then oftentimes customers will say, If I have a piece of data volume and I suddenly have to delete it, I still need to have some record of that action for a long time, right? So those are the kinds of things that are happening and his crew bearnaise and everything. It gets changed. Suddenly. The important part is not what was just that one pot it becomes. How do I reconstruct everything? What action is not one thing. It's everywhere. That's right and protected all through the platform. If it was a platform decision, it's not some the cattlemen on the side. You can't be a single lap. It has to be entire solution. And it has to handle things like, Where do you come from? Where is it allowed to go? And you guys have that philosophy. We absolutely, and it's based on the enterprises that are adopting port works and saying, Hey, this is my romance. I'm basing it on Kubernetes. You're my date a partner. We make it happen. >>This speaks to your point of why the enterprise is in. The vendors jumped in this is what people care about Security. How do you solve this last mile problem? Storage. Networking. How do you plug those holes in Kubernetes? Because that is crucial to our >>personal private moment. Victory moment for me personally, was been a big fan of Cuban is absolutely, you know, for years. Then there were created, talked about one. The moments that got me that was really kind of a personal, heartfelt moment was enterprise buyer. And, you know, the whole mindset in the Enterprise has always been You gotta kill the old to bring in the new. And so there's always been that tension of a you know, the shiny new toy from Silicon Valley or whatever. You know, I'm not gonna just trash this and have a migration za paying that. But for I t, they don't want that to do that. They hate doing migrations, but with containers and kubernetes that could actually they don't to end of life to bring in the new project. They can do it on their own timetable or keep it around. So that took a lot of air out of the tension in on the I t. Side because they say great I can deal with the lifecycle management, my app on my own terms and go play with Cloud native and said to me, that's like that was to be like, Okay, there it is. That was validation. That means this Israel because now they can innovate without compromising. >>I think so. And I think some of that has been how the ecosystems embrace it, right. So now it's becoming all the vendors are saying my internal stack is also based on community. So even if you as an application owner or not realizing it, you're gonna take a B M next year and you're gonna run it and it's gonna be back by something like awesome. Lisa >>Marie Nappy Eric on Thank you for coming on Port Works Hot start of multiple cities Kubernetes big developer Project Open Source. Talking about multi cloud here at the inaugural Multi cloud conference in New York City. It's the Cube Courage of escape. 2019. I'm John Period. Thanks for watching

>> Welcome back to the Cuban Peterborough's chief research officer of Silicon Angle and general manager of Wicked Bond. We're as part of our continuing coverage of the arse a show. We have a great guest Z scaler amid sin. Ha! Welcome to the Cube. >> Thank you for having me here. It's a pleasure to be here. >> So, um, it what exactly does Z scaler? D'oh >> Z's killer is in the business of providing the entire security stack as a service for large enterprises. We sit in between enterprise users and the Internet and various destinations they want to goto, and we want to make sure that they have a fast, nimble Internet experience without compromising any security. >> So if I can interpret what that means, that means that as Maur companies are trying to serve their employees that Air Mobile or customers who aren't part of their corporate network they're moving more. That communication in the Cloud Z scale is making it possible for them to get the same quality of security on that communication in the cloud is he would get on premise. >> Absolutely. If you look at some of the big business transformations that are happening, work lords for enterprises are moving to the cloud. For example, enterprises are adopting Office 3 65 instead, off traditional exchange based email and on your desktop applications. They might be adopting sales force for CR M Net suite for finance box for storage. So as these workloads are moving to the cloud and employees are becoming more and more mobile, you know they might be at a coffee shop. They might be on an iPad. Um, and they might be anywhere in the world. That begs the basic security question. Where should that enterprise DMC the security stack be sitting back in the day? Enterprises had a hub and spokes model, right? They might have 50 branch offices across the world. A few mobile workers, all of them, came back over private networks to a central hub, and that hub was where racks and racks of security appliances were deployed. Maybe they started off with a firewall. Later on, they added a proxy. You are l filtering some d e l P er down the road. People realized that you need to inspect us to sell. So they added some SSL offload devices. Someone said, Hey, we need to do some sand boxing for behavioral analysis. People started adding sandboxes. And so, over time the D. M. Z got cluttered and complicated and fast forward to Today. Users have become mobile. Workloads have moved to the cloud. So if I'm sitting in a San Francisco office on my laptop trying to do my regular work, my email is in the cloud. My my court applications are sitting in the cloud. Why should I have to vpn back to my headquarters in Cincinnati over a private network, you know, incurring all the Leighton see and the delays just so that I can get inspected by some legacy appliances that are sitting in that DMC, right? So we looked at that network transformation on We started this journey at Ze scale or eight years ago, and we said, Look, if users are going to be mobile and workloads are going to be in the cloud, the entire security stack should be as close as possible to where the users are. In that example, I described, I'm sitting here. I'm going to Salesforce. We're probably going to the same data center in San Francisco. Shouldn't my entire security stag be available right where I am, um, and my administrators should have full visibility, full control from a single pane of glass. I get a fast, nimble user experience. The enterprise doesn't have to compromise in any security, and that's sort of the vision that we have executing towards. >> But it's not just for some of the newer applications or some of the newer were close. We're also seeing businesses acknowledge that the least secure member of their community has an impact on overall security. So the whole concept of even the legacy has to become increasingly a part of this broad story. So if anybody accesses anything from anywhere through the cloud that those other workloads increasing, they're gonna have to come under the scrutiny of a cloud based security option. >> Absolutely. I mean, that's a brilliant point, Peter. >> I >> think of >> it this way. Despite all those security appliances that have been deployed over time, they're still security breach is happening. And why is that? That is because users are the weakest link, right? If I'm a mobile work user, I'm sitting in a branch office. It's just painful for me to go back to those headquarter facilities just for additional scanning so two things happen either I have a painful user experience. What? I bypassed security, right? Um, and more and more of the attacks that we see leverage the user as the weakest link. I send you a phishing email. It looks like it came from HR. It has a excel sheet attached to it to update some information. But, you know, inside is lurking a macro, right? You open it. It is from a squatter domain that looks very similar to the company you work for. You click on it and your machine is infected. And then that leads to further malware being downloaded, data being expatriated out. So the Z scaler solution is very, very simple. Conceptually, we want to sit between users and the destinations they goto all across the world. And we built this network of 100 data centers. Why? Because you cannot travel faster than the speed of light. So if you're in San Francisco, you better go through our San Francisco facility. All your policies will show up here. All the latest and greatest security protections will be available. We serve 5000 large enterprises. So if we discover a new security threat because of an employee from, let's say, a General Electric. Then someone from United Airlines automatically gets protection simply because the cloud is live all the time. You're not waiting for your security boxes to get, you know, the weekly patch updates for new malware indicators and so on. Right, So, um, you get your stack right where you are. It's always up to date. User experience is not compromised. Your security administrators get a global view off things. And one >> of the >> things that that I that we haven't talked about here it is the dramatic cost savings that this sort of network transformation brings for enterprises. To put that in perspective, let's say you're a Fortune 100 organization with 100,000 employees worldwide in that, huh? Been spoke model. You are forcing all those workloads to come toe a few choke points, right? That is coming over. Very expensive. NPLs circuits private circuits from service providers. You're double trombone in traffic, back and forth. You know, you and I are in a branch. We might be on. Ah, Skype session. Ah, Google Hangout session. All our traffic goes to H Q. Goes to the cloud comeback comes back to h. Q comes back to you, there's this is too much back and forth, and you're paying for those expensive circuits and getting a poor user experience. Wouldn't it be great if you and I could go straight to the Internet? And that can only be enabled if we can provide that pervasive security stack wherever you are? And for that, we built this network of 100 data centers worldwide. Always live, always up to date you. You get routed to the closest the scaler facility. All your policy show up. They're automatically and you get the latest and greatest protection. >> So it seems as though you end up with three basic benefits. One is you get the cost benefit of being able to, uh, have being able to leverage a broader network of talent, skills and resources You reduce. Your risk is not the least of which is that the cost and the challenges configuring a whole bunch of appliances has not gotten any easier over the last. No, it hasn't cheaters. And so not only do you have user error, but you also Administrator Erin, absolutely benign, but nonetheless it's there, and then finally and this is what I want to talk about. Increasingly, the clot is acknowledged as the way that companies are going to improve their portfolio through digital assets. Absolutely. Which means new opportunities, new competition, new ways of improving customer experience. But security has become the function of no within a lot of organizations. Absolutely. So How does how does AE scaler facilitate the introduction of new business capabilities that can attack these opportunities in a much more timely way by reducing doesn't reduce some of those some of those traditional security constraints. >> Absolutely right, and we call it the Department of No right. We've talked to most people in the industry. They view their I t folks there, security forces, the department of Know Why? Because there's this big push from users to adopt newer, nimble, faster cloud based ah solutions that that improved productivity. But often I t comes in the way. No, If you look at what Izzy's killer is doing, it's trying to transform the adoption of these Cloud service. Is that do improve business productivity? In fact, there is no debate now because there are many, many industries that ever doubt adopted a cloud first strategy. Well, that means is, as they think of the network and their security, they want to make sure that cloud is front and center. Words E scaler does is it enables that cloud for a strategy without any security compromise. I'll give you some specific examples. Eight out of 10 c I ose that we talk to our thinking about office 3 65 or they have already deployed it right. One of the first challenge is that happens when you try to adopt office. 3 65 is that your legacy network and security infrastructure starts to come crumble. Very simple things happen. You have your laptop. Suddenly, that laptop has many, many persistent SSL connections to the clothes. Because exchange is moved to the cloudy directory, service is are moving to the cloud. If you have a small branch office with 2000 users, each of them having 30 40 persistent connections to the cloud will your edge firewall chokes. Why? Because it cannot maintain so many active ports at the same time, we talked about the double trombone ing of traffic back and forth. If you try to not go direct to the Internet but force everyone to go through a couple of hubs. So you pay for all the excessive band with your traditional network infrastructure, and your security infrastructure might need a forklift upgrades. So a cloud transformation project quickly becomes a network in a security transformation project. And this is where you nosy scaler helps tremendously because we were born and bred in the cloud. Many of these traditional limitations that you have with appliance based security or networking, you know, in the traditional sense don't exist for the scaler, right? We can enable your branch officers to go directly to the cloud. In fact, we've started doing some very clever things. For example, we peer with Microsoft in about 20 sites worldwide. So what that means is, when you come to the scaler for security, there's a very high likelihood that Microsoft has a presence in the same data center. We might be one or two or three millisecond hops away because we're in the same equinox facility in New York or San Jose. And so not only are you getting your full security stack where you are, you're getting the superfast peered connections to the end Cloud service is that you want to goto. You don't have to work. Worry about you know your edge Firewalls not keeping up. You don't have to worry about a massive 30 40% increase in back hole costs because you were now shipping all this extra traffic to those couple of hubs. And more importantly, you know, you've adopted these transformative technologies on your users don't have to complain about how slow they are because you know, most of the millennials hitting the workforce. I used to a very fast, nimble experience on their mobile phones with consumer APS. And then they come into the enterprise and they quickly realize that, well, this is all cumbersome and old and legacy stuff >> in me s. So let's talk a little bit about Let's talk a bit about this notion of security being everywhere and increasingly is removed to a digital business or digital orientation. With digital assets being the basis for the value proposition, which is certainly happening on a broad scale right now, it means it's security going back to the idea of security being department. No security has to move from an orientation of limiting access to appropriately sharing. Security becomes the basis for defining the digital brand. So talk to us a little bit about how the how you look out, how you see the world, that you think security's gonna be playing in ultimately defining this notion of digital brand digital perimeters from a not a iittie standpoint. But from a business value standpoint, >> absolutely. I would love to talk about that. So Izzy's killer Our cloud today sees about 30,000,000,000 transactions a day from about 5000 enterprises. So we have a very, very good pulse on what is happening in large enterprises, from from a cloud at perspective or just what users are doing on the Internet. So here are some of the things that we see. Number one. We see that about 50 60% of the threats are coming inside SSL, so it's very important to inspect SSL. The second thing that we observe is without visibility. It is very different, very difficult for your security guys to come up with a Chris policy, right? If you cannot see what is happening inside an SSL connection, how are you going to have a date? A leakage policy, right? Maybe your policy is no P I information should leak out. No source code should leak out. How can you make sure that an engineer is not dropping something in this folder, which is sinking to Google Drive or drop box in an in an SSL tano, Right. How do you prioritize mission Critical business applications like office 3 65 over streaming media, Right. So for step two, crafting good policy is 100% real time visibility. And that's what happens when you adopt the Siskel a network. You can see what any user is doing anywhere in the world within seconds. And once you have that kind of visibility, you can start formulating policies, both security and otherwise that strike a good balance between business productivity that you want to achieve without compromising security. >> That's the policy's been 10 more net. You can also end that decisions. >> Yes, right. So, for example, you can you can have a more relaxed social media policy, right? You can say Well, you know, everyone is allowed access, but they can. Maybe streaming media is restricted to one hour a day. You know, after hours, or you can say, I want to adopt um, storage applications in the clothes here are some sanctioned APS These other raps were not going to allow right. You can do policies by users, by locations by departments, right? And once you have the visibility, you can. You can be very, very precise and say, Well, boxes, my sanction story, Jap other APS are not allowed right and hear other things that a particular group of users can do on box. Or they cannot do because we were seeing every transaction between the user on going to the destination and as a result, begin, you know, we can enable the enterprise administrator to come up with very, very specific policies that are tailored for that. >> You said something really interesting. I'm gonna ask you one more question, but I'm gonna make a common here. And that common is that the power of digital technology is that it can be configured and copied and changed, and it's very mutable. It's very plastic, but at the end of the day it has to be precise, and I've never heard anybody talk about the idea of precise and security, and I think it's a very, very powerful concept. But what are what's What's the scale are talking about in our say this year. >> Well, we're going to talk about a bunch of very interesting things. First, we'll talk about the scale of private access. This is a new offering on the scale of platform. We believe that VP ends have become irrelevant because of all the discussions we just had, um, Enterprises are treating their Internet as though it was the Internet, right? You know, sort of a zero trust model. They're moving the crown jewel applications to either private cloud offerings are, you know, sort of restricting that in a very micro segmented way. And the question is, how do you access those applications? Right? And the sea skill immortal is very straightforward. You have a pervasive cloud users authenticate to the cloud and based on policies, we can allow them to go to the Internet to sites that have been sanctioned and allowed. We make sure nothing good is leaking out. Nothing bad is coming in, and that same cloud model can be leveraged for private access to crown jewel applications that traditionally would have required a full blown vpn right. And the difference between a VPN and the skill of private access is VP ends basically give you full network access keys to the kingdom, right? Whether it's a contractor with, it's an employee just so that you could access, you know, Internet application. You allow full network access, and we're just gonna getting rid of that whole notion. That's one thing we're gonna stroke ISS lots of cloud white analytics, As I mentioned, you know, we process 30,000,000,000 transactions a day. To put that in perspective, Salesforce reports about four and 1 30,000,000,000 4 1/2 to 5,000,000,000 transactions. They're about three and 1/2 1,000,000,000 Google searches done daily, right? So it is truly a tin Internet scale. We're blocking over 100,000,000 threats every day for, ah, for all our enterprise user. So we have a very good pulse on you know what's what's an average enterprise user doing? And you're going to see some interesting cloud? Wait, Analytics. Just where we talk about a one of the top prevalent Claude APs, what are the top threats? You know, by vertical buy by geography, ese? And then, you know, we as a platform has emerged. We started off as a as a sort of a proxy in the cloud, and we've added sand boxing capabilities. Firewall capabilities, you know, in our overall vision, as I said, is to be that entire security stack that sits in your inbound and outbound gateway in that DMC as a pure service. So everything from firewall at layer three to a proxy at Layer seven, everything from inline navy scanning right to full sand. Boxing everything from DLP to cloud application control. Right? And all of that is possible because, you know, we have this very scalable architecture that allows you to to do sort of single scan multiple action right in that appliance model that I describe. What ends up happening is that you have many bumps in the wire. One of the examples we use is if you wanted to build a utility company, you don't start off with small portable generators and stack them in a warehouse, right? That's inefficient. It requires individual maintenance. It doesn't scale properly. Imagine if you build a turbine and ah, and then started your utility company. You can scale better. You can do things that traditional appliance vendors cannot think about. So we build this scalable, elastic security platform, and on that platform it's very easy for us to add. You know, here's a firewall. Here's a sandbox. And what does it mean for end users? You know, you don't need to deploy new boxes. You just go and say, I want to add sand boxing capabilities or I want to add private access or I want to add DLP. And it is as simple as enabling askew, which is what a cloud service offering should be. >> Right. So we're >> hardly know software. >> So we're talking about we're talking about lower cost, less likelihood of human error, which improves the quality, security, greater plasticity and ultimately, better experience, especially for your non employees. Absolutely. All right, so we are closing up this particular moment I want Thank you very much for coming down to our Pallotta studio is part of our coverage on Peter Boris. And we've been talking to the scanner amidst, huh? Thank you very much. And back to Dio Cube.