(bright upbeat music) >> Welcome back, everybody, to the Supercloud 2. My name is Dave Vellante. And I'm pleased to welcome Nir Zuk. He's the founder and CTO of Palo Alto Networks. Nir, good to see you again. Welcome. >> Same here. Good to see you. >> So let's start with the right security architecture in the context of today's fragmented market. You've got a lot of different tools, you've got different locations, on-prem, you've got hardware and software. Tell us about the right security architecture from your standpoint. What's that look like? >> You know, the funny thing is using the word security in architecture rarely works together. (Dave chuckles) If you ask a typical information security person to step up to a whiteboard and draw their security architecture, they will look at you as if you fell from the moon. I mean, haven't you been here in the last 25 years? There's no security architecture. The architecture today is just buying a bunch of products and dropping them into the infrastructure at some relatively random way without really any guiding architecture. And that's a huge challenge in cybersecurity. It's always been, we've always tried to find ways to put an architecture into writing blueprints, whatever you want to call it, and it's always been difficult. Luckily, two things. First, there's something called zero trust, which we can talk a little bit about more, if you want, and zero trust among other things is really a way to create a security architecture, and second, because in the cloud, in the supercloud, we're starting from scratch, we can do things differently. We don't have to follow the way we've always done cybersecurity, again, buying random products, okay, maybe not random, maybe there is some thinking going into it by buying products, one of the other, dropping them in, and doing it over 20 years and ending up with a mess in the cloud, we have an opportunity to do it differently and really have an architecture. >> You know, I love talking to founders and particularly technical founders from StartupNation. I think I saw an article, I think it was Erie Levine, one of the founders or co-founders of Waze, and he had a t-shirt on, it said, "Fall in love with the problem, not the solution." Is that how you approached architecture? You talk about zero trust, it's a relatively new term, but was that in your head when you thought about forming the company? >> Yeah, so when I started Palo Alto Networks, exactly, by the way, 17 years ago, we got funded January, 2006, January 18th, 2006. The idea behind Palo Alto Networks was to create a security platform and over time take more and more cybersecurity functions and deliver them on top of that platform, by the way, as a service, SaaS. Everybody thought we were crazy trying to combine many functions into one platform, best of breed and defense in death and putting all your eggs in the same basket and a bunch of other slogans were flying around, and also everybody thought we were crazy asking customers to send information to the cloud in order to secure themselves. Of course, step forward 17 years, everything is now different. We changed the market. Almost all of cybersecurity today is delivered as SaaS and platforms are ruling more and more the world. And so again, the idea behind the platform was to over time take more and more cybersecurity functions and deliver them together, one brain, one decision being made for each and every packet or system call or file or whatever it is that you're making the decision about and it works really, really well. As a side effect, when you combine that with zero trust and you end up with, let's not call it an architecture yet. You end up with with something where any user, any location, both geographically as well as any location in terms of branch office, headquarters, home, coffee shop, hotel, whatever, so any user, any geographical location, any location, any connectivity method, whether it is SD1 or IPsec or Client VPN or Client SVPN or proxy or browser isolation or whatever and any application deployed anywhere, public cloud, private cloud, traditional data center, SaaS, you secure the same way. That's really zero trust, right? You secure everything, no matter who the user is, no matter where they are, no matter where they go, you secure them exactly the same way. You don't make any assumptions about the user or the application or the location or whatever, just because you trust nothing. And as a side effect, when you do that, you end up with a security architecture, the security architecture I just described. The same thing is true for securing applications. If you try to really think and not just act instinctively the way we usually do in cybersecurity and you say, I'm going to secure my traditional data center applications or private cloud applications and public cloud applications and my SaaS applications the same way, I'm not going to trust something just because it's deployed in the private data center. I'm not going to trust two components of an application or two applications talking to each other just because they're deployed in the same place versus if one component is deployed in one public cloud and the other component is deployed in another public cloud or private cloud or whatever. I'm going to secure all of them the same way without making any trust assumptions. You end up with an architecture for securing your applications, which is applicable for the supercloud. >> It was very interesting. There's a debate I want to pick up on what you said because you said don't call it an architecture yet. So Bob Muglia, I dunno if you know Bob, but he sort of started the debate, said, "Supercloud, think of it as a platform, not an architecture." And there are others that are saying, "No, no, if we do that, then we're going to have a bunch of more stove pipes. So there needs to be standard, almost a purist view. There needs to be a supercloud architecture." So how do you think about it? And it's a bit academic, I know, but do you think of this idea of a supercloud, this layer of value on top of the hyperscalers, do you think of that as a platform approach that each of the individual vendors are responsible for the architecture? Or is there some kind of overriding architecture of standards that needs to emerge to enable the supercloud? >> So we can talk academically or we can talk practically. >> Yeah, let's talk practically. That's who you are. (Dave laughs) >> Practically, this world is ruled by financial interests and none of the public cloud providers, especially the bigger they are has any interest of making it easy for anyone to go multi-cloud, okay? Also, on top of that, if we want to be even more practical, each of those large cloud providers, cloud scale providers have engineers and all these engineers think they're the best in the world, which they are and they all like to do things differently. So you can't expect things in AWS and in Azure and GCP and in the other clouds like Oracle and Ali and so on to be the same. They're not going to be the same. And some things can be abstracted. Maybe cloud storage or bucket storage can be abstracted with the layer that makes them look the same no matter where you're running. And some things cannot be abstracted and unfortunately will not be abstracted because the economical interest and the way engineers work won't let it happen. We as a third party provider, cybersecurity provider, and I'm sure other providers in other areas as well are trying or we're doing our best. We're not trying, we are doing our best, and it's pretty close to being the way you describe the top of your supercloud. We're building something that abstracts the underlying cloud such that securing each of these clouds, and by the way, I would add private cloud to it as well, looks exactly the same. So we use, almost always, whenever possible, the same terminology, no matter which cloud we're securing and the same policy and the same alerts and the same information and so on. And that's also very important because when you look at the people that actually end up using the product, security engineers and more importantly, SOC, security operations center analysts, they're not going to study the details of each and every cloud. It's just going to be too much. So we need to abstract it for them. >> Yeah, we agree by the way that the supercloud definition is inclusive of on-prem, you know, what you call private cloud. And I want to pick up on something else you said. I think you're right that abstracting and making consistent across clouds something like object storage, get put, you know, whether it's an S3 bucket or an Azure Blob, relatively speaking trivial. When you now bring that supercloud concept to something more complex like security, first of all, as a technically feasible and inferring the answer there is yes, and if so, what do you see as the main technical challenges of doing so? >> So it is feasible to the extent that the different cloud provide the same functionality. Then you step into a territory where different cloud providers have different paths services and different cloud providers do things a little bit differently and they have different sets of permissions and different logging that sometimes provides all the information and sometimes it doesn't. So you end up with some differences. And then the question is, do you abstract the lowest common dominator and that's all you support? Or do you find a way to be smarter than that? And yeah, whatever can be abstracted is abstracted and whatever cannot be abstracted, you find an easy way to represent that to your users, security engineers, security analysts, and so on, which is what I believe we do. >> And you do that by what? Inventing or developing technology that presents that experience to users? Could you be more specific there? >> Yeah, so different cloud providers call their storage in different names and you use different ways to configure them and the logs come out the same. So we normalize it. I mean, the keyword is probably normalization. Normalize it. And we try to, you know, then you have to pick a winner here and to use someone's terminology or you need to invent new terminology. So we try to use the terminology of the largest cloud provider so that we have a better chance of doing that but we can't always do that because they don't support everything that other cloud providers provide, but the important thing is, with or thanks to that normalization, our customers both on the engineering side and on the user side, operations side end up having to learn one terminology in order to set policies and understand attacks and investigate incidents. >> I wonder if I could pick your brain on what you see as the ideal deployment model to achieve this supercloud experience. For example, do you think instantiating your stack in multiple regions and multiple clouds is the right way to do it? Or is building a single global instance on top of the clouds a more preferable way? Are maybe other models we should consider? What do you see as the trade off of these different deployment models and which one is ideal in your view? >> Yeah, so first, when you deploy cloud security, you have to decide whether you're going to use agents or not. By agents, I mean something working, something running inside the workload. Inside a virtual machine on the container host attached to function, serverless function and so on and I, of course, recommend using agents because that enables prevention, it enables functionality you cannot get without agents but you have to choose that. Now, of course, if you choose agent, you need to deploy AWS agents in AWS and GCP agents in GCP and Azure agents in Azure and so on. Of course, you don't do it manually. You do it through the CICD pipeline. And then the second thing that you need to do is you need to connect with the consoles. Of course, that can be done over the internet no matter where your security instances is running. You can run it on premise, you can run it in one of the other different clouds. Of course, we don't run it on premise. We prefer not to run it on premise because if you're secured in cloud, you might as well run in the cloud. And then the question is, for example, do you run a separate instance for AWS for GCP or for Azure, or you want to run one instance for all of them in one of these clouds? And there are advantages and disadvantages. I think that from a security perspective, it's always better to run in one place because then when you collect the information, you get information from all the clouds and you can start looking for cross-cloud issues, incidents, attacks, and so on. The downside of that is that you need to send all the information to one of the clouds and you probably know that sending data out of the cloud costs a lot of money versus keeping it in the cloud. So theoretically, you can build an architecture where you keep the data for AWS in AWS, Azure in Azure, GCP in GCP, and then you try to run distributed queries. When you do that, you find out you'd end up paying more for the compute to do that than you would've paid for sending all the data to a central location. So we prefer the approach of running in one place, bringing all the data there, and running all the security, the machine learning or whatever, the rules or whatever it is that you're running in one place versus trying to create a distributed deployment in order to try to save some money on the data, the network data transfers. >> Yeah, thank you for that. That makes a lot of sense. And so basically, should we think about the next layer building security data lake, if you will, and then running machine learning on top of that if I can use that term of a data lake or a lake house? Is that sort of where you're headed? >> Yeah, look, the world is headed in that direction, not just the cybersecurity world. The world is headed from being rule-based to being data-based. So cybersecurity is not different and what we used to do with rules in the past, we're now doing with machine learning. So in the past, you would define rules saying, if you see this, this, and this, it's an attack. Now you just throw the data at the machine, I mean, I'm simplifying it, but you throw data at a machine. You'll tell the machine, find the attack in the data. It's not that simple. You need to build the right machine learning models. It needs to be done by people that are both cybersecurity experts and machine learning experts. We do it mostly with ex-military offensive people that take their offensive knowledge and translate it into machine learning models. But look, the world is moving in that direction and cybersecurity is moving in that direction as well. You need to collect a lot of data. Like I said, I prefer to see all the data in one place so that the machine learning can be much more efficient, pay for transferring the data, save money on the compute. >> I think the drop the mic quote it ignite that you had was within five years, your security operation is going to be AI-powered. And so you could probably apply that to virtually any job over the next five years. >> I don't know if any job. Certainly writing essays for school is automated already as we've seen with ChatGPT and potentially other things. By the way, we need to talk at some point about ChatGPT security. I don't want to think what happens when someone spends a lot of money on creating a lot of fake content and teaches ChatGPT the wrong answer to a question. We start seeing ChatGPT as the oracle of everything. We need to figure out what to do with the security of that. But yeah, things have to be automated in cybersecurity. They have to be automated. They're just too much data to deal with and it's just not even close to being good enough to wait for an incident to happen and then going investigate the incident based on the data that we have. It's better to look at all the data all the time, millions of events per second, and find those incidents before they happen. There's no way to do that without machine learning. >> I'd love to have you back and talk about ChatGPT. I know they're trying to put in some guardrails but there are a lot of unintended consequences, aren't there? >> Look, if they're not going to have a person filtering the data, then with enough money, you can create thousands or tens of thousands of pieces of articles or whatever that look real and teach the machine something that is totally wrong. >> We were talking about the hyper skills before and I agree with you. It's very unlikely they're going to get together, band together, and create these standards. But it's not a static market. It's a moving train, if you will. So assuming you're building this cross cloud experience which you are, what do you want from the hyperscalers? What do you want them to bring to the table? What is a technology supplier like Palo Alto Networks bring? In other words, where do you see ongoing as your unique value add and that moat that you're building and how will that evolve over time vis-a-vis the hyperscaler evolution? >> Yeah, look, we need APIs. The more data we have, the more access we have to more data, the less restricted the access is and the cheaper the access is to the data because someone has to pay today for some reason for accessing that data, the more secure their customers are going to be. So we need help and are helping by the way a lot, all of them in finding easy ways for customers to deploy things in the cloud, access data, and again, a lot of data, very diversified data and do it in a cost-effective way. >> And when we talk about the edge, I presume you look at the edge as just another data center or maybe it's the reverse. Maybe the data center is just another edge location, but you're seeing specific edge security solutions come out. I'm guessing that you would say, that's not what we want. Edge should be part of that architecture that we talked about earlier. Do you agree? >> Correct, it should be part of the architecture. I would also say that the edge provides an opportunity specifically for network security, whereas traditional network security would be deployed on premise. I'm talking about internet security but half network security market, and not just network security but also the other network intelligent functions like routing and QS. We're seeing a trend of pushing those to the edge of the cloud. So what you deploy on premise is technology for bringing packets to the edge of the cloud and then you run your security at the edge, whatever that edge is, whether it's a private edge or public edge, you run it in the edge. It's called SASE, Secure Access Services Edge, pronounced SASE. >> Nir, I got to thank you so much. You're such a clear thinker. I really appreciate you participating in Supercloud 2. >> Thank you. >> All right, keep it right there for more content covering the future of cloud and data. This is Dave Vellante for John Furrier. I'll be right back. (bright upbeat music)

>>The Cube presents Ignite 22, brought to you by Palo Alto Networks. >>Welcome back to Vegas, guys and girls, it's great to have you with us. The Cube Live. Si finishing our second day of coverage of Palo Alto Ignite. 22 from MGM Grand in Las Vegas. Lisa Martin here with Dave Valante. Dave Cybersecurity is one of my favorite topics to talk about because it is so interesting. It is so dynamic. My other favorite thing is to hear the voice of our vendors' customers. And we could to >>Do that. I always love to have the customer on you get you get right to the heart of the matter. Yeah. Really understand. You know, what I like to do is sort of when I listen to the keynotes, try to see how well it aligns with what the customers are actually doing. Yeah. So let's >>Do it. We're gonna unpack that now. Michael Fagan joins us, the Chief Transformation Officer at Village Roadshow. Welcome Michael. It's great to have you >>And thank you. It's a pleasure to be here. >>So this is a really interesting entertainment company. I find the name interesting, but talk to us a little bit about Village Roadshow so the audience gets an understanding of all of the things that you guys do cuz theme parks is part of >>This. Yeah, so Village Road show's Australia's largest cinema exhibitor in conjunction with our partners at event. We also own and operate Australia's largest theme parks. We have Warner Brothers movie World, wet and Wild. SeaWorld Top Golf in Australia is, is operated by us plus more. We also do studio, we also own movie studios, so Aquaman, parts of the Caribbean. We're, we're filming our movie studios Elvis last year. And we also distribute and produce movies and TV shows. Quite diverse group. >>Yeah, you guys have won a lot of awards. I mean, I don't know, academy Awards, golden Globe, all that stuff, you know, and so it's good. Congratulations. Yeah. >>Thank you. >>Cool stuff. I wanna also, before we dig into the use case here, talk to us about the role of a chief transformation officer. How long have you been in that role? What does it encompass and what do you get to drive from a transformation perspective? Yeah, >>So the, the, the nature and pace of disruption is accelerating and on, on one side. And then on the other side, the running business as usual is becoming increasingly complex and, and more difficult to do. So running both simultaneously and at pace can put organizations at risk, both financially and and other ways. So in my role as Chief Transformation officer, I support the rest of the executive team by giving them additional capacity and also bring capability to the team that wasn't there before. So I do a lot of strategic and thought leadership. There's some executive coaching in there, a lot of financial modeling and analysis. And I believe that when a transformation role in particularly a chief transformation role is done correctly, it's a very hands-on role. So there's certain things where I, I dive right down and I'm actually hands in, hands-on leading teams or leading pieces of work. So I might be leading particular projects. I tried to drive profit revenue and profitability across the divisions and does any multi or cross-divisional opportunities or initiative, then I will, I will lead those. >>The transformation, you know, a while ago was cloud, right? Okay, hey, cloud and transformation officers, whether or not they had that title, we'll tell you, look, you gotta change the operating model. You can't just, you know, lift and shift in the cloud. That's, you know, that's pennies. We want, you know, big bucks. That's the operating. Now it's, I'm my question is, is did the pandemic just accelerate your transformation or, or was it, you know, deeper than that? >>Yeah, so what in my role have both digital and business transformation, some of it has been organizational. I think the pandemic has had a, a significant and long lasting effect on society, not just on, on business. So I think if you think about how work work used to be a, a place you went to and how it was done beforehand, before the, before COVID versus now where, you know, previously, you know, within the enterprise you had all of the users, you had all of the applications, you had all of the data, you had all of the people. And then since March, 2020, just overnight, that kind of inverted and, you know, you had people working from home and a person working from home as a branch office of one. So, so we ended up with another thousand branches literally overnight. A lot of the applications that we use are now SASS or cloud-based, whether that's timekeeping with Kronos or communica employee communication or work Jam. So they're not sitting within our data center, they're not sitting within, within our enterprise. It's all external. >>So from a security perspective, you obviously had to respond to that and we heard a lot about endpoint and cloud security and refactoring the network and identity. These guys aren't really an identity. They partner for that, but still a lot of change in focus that the CISO had to deal with. How, how did you guys respond to that? And, and you had a rush to do it. Yeah. And so as you sit back now, where do you go from here? >>Well we had, we had two major triggers for our, our network and security transformation. The first being COVID itself, and then the second beam, we had a, a major MPLS telco renewal that came up. So that gave you an opportunity to look at what we were doing and essentially our network was designed for a near, that no longer exists for when, for when p like I said, when people, when people were from home, all the applications were inside. So, and we had aging infrastructure, our firewalls were end of life. So initially we started off with an SD WAN at the SD WAN layer and an SD WAN implementation. But when we investigated and saw the security capabilities that are available now, we that to a full sassy WAN implementation. >>Why Palo Alto Networks? Because you, you had, you said you had an aging infrastructure designed for an era that doesn't exist anymore, but you also had a number of tools. We've been talking about a consolidation a lot the last couple days. Yeah. How did, what did you consolidate and why with Palo Alto? >>So we had a great partner in Australia, incidentally also called Cube. Cube Networks. Yeah. That we worked with great >>Names. Yeah, right. >>So we, so we, we worked for Cube. We ran a, a form of tender process. And Palo Alto with, you know, Prisma access and Global Global Protect was the only, the only solution that gave us everything that we needed in terms of network modernization, the agility that we required. So for example, in our theme part, we want to send out a hotdog cart or an ice cream cart, and that becomes, all of a sudden you got a new branch that I want to spin up this branch in 10 minutes and then I wanna spin it back down again. So from agility perspective, from a flexibility perspective, the security that, that we wanted, you know, from a zero trust perspective, and they were the only, certainly from a zero trust perspective, they're probably the only vendor that, that exists that, that actually provided the, the, all those capabilities. >>And did you consolidate tools or you were in the process of consolidating tools now? >>Yeah, so we actually, we actually consolidated down to, to, to a, to a single vendor. And in my previous role I had, I had implemented SD WAN before and you know, interoperability is a, is a major issue in the IT industry. I think there's, it's probably the only industry in the, the only industry I can think of certainly that where we, we ship products that aren't ready. They're not of all the features, they, they don't have all the features that they should have. They're their plans. They were releasing patches, releasing additional features every, every couple of months. So, you know, if you, if if Ford sold the card, I said, Hey, you're gonna give you backseats in a couple of months, they'd be uproar. But, but we do that all the time in, in it. So I had, when I previously implemented an Sdwan transformation, I had products from two tier one vendors that just didn't talk to one another. And so when I went and spoke to those vendors, they just went, well, it's not me. It's clearly, clearly those guys. So, so there's a lot to be said for having a, you know, a champion team rather than a team of champions. And Palo Alto have got that full stack fully integrated that was, you know, exactly meant what we were looking for. >>They've been talking a lot the last couple days about integration and it, and I've talked with some of their executives and some analysts as well, including Dave about that seems to be a differentiator for them because they really focus on that. Their m and a strategy is very, it seems to be very clear and there's purpose on that backend integration instead of leaving it to the customer, like Village Road show to do it. They also talked a lot about the consolidation. I'm just curious, Michael, in terms of like what you've heard at the show in the last couple of days. >>Yeah, I mean I've been hearing to same mess, but actually we've, we've lived in a >>You're living it. That's what I wanted to >>Know. So, so, you know, we had a choice of, you know, do you try and purchase so-called best of breed products and then put a lot of effort into integrating them and trying to get them to work, which is not really what we want to spend time doing. I don't, I don't wanna be famous for, you know, integration and, you know, great infrastructure. I want to be, I want Village to be famous for delivering great experiences to our customers. Memories that last a lifetime. And you know, when kids grow up in Australia, they, everybody remembers going to the theme parks. That's what, that's what I want our team to be doing and to be delivering those great experiences, not to be trying to plug together bits of software and it may or may not work and have vendors pointing at one another and then we are left carrying the cannon and holding the >>Baby. So what was the before and after, can you give us a sense as to how life changed, you know, pre that consolidation versus post? >>Yeah, so our, our, our infrastructure, say our infrastructure was designed for, you know, the, you know, old ways of working where we had you knowm routers that were, you know, not designed for cloud, for modern traffic, including cloud Destin traffic, an old MPLS network. We used to back haul all the traffic from, from our branches back to central location run where we've got, you know, firewall walls, we've got a dmz, we could run advanced inspection services on that. So if you had a branch that wanted to access a website that was housed next door, even if it was across the country, then it would, we would pull that all the way back to Melbourne. We would apply advanced inspection services to it, send it up to the cloud out back across the country. Traffic would come back, come down to us, back out to our branch. >>So you talk about crossing the country four times, even at the website is, is situated next door now with, with our sasi sdwan transformation just pops out to the cloud now straight away. And the, the difference in performance for our, for our team and for our customers, it, it's phenomenal. So you'll talk about saving minutes, you know, on a log on and, and seconds then and on, on an average transaction and second zone sound like a lot. But when you, it's every click up, they're saving a second and add up. You're talking about thousands of man hours every month that we've saved. >>If near Zuke were sitting right here and said, what could we do better? You know, what do you need from us that we're not delivering today that you want to, you want us to deliver that would change your life. Yeah, >>There's two things. One, one of which I think they're all, they're already doing, but I actually haven't experienced myself. It's around the autonomous digital experience management. So I've now got a thousand users who are sitting at home and they've got, when they've got a problem, I don't know, is it, is it my problem or is it their problem? So I know that p were working on a, an A solution that digital experience solution, which can actually tell, well actually know you're sitting in your kitchen and your routes in your front room, maybe you should move closer to the route. So there, there they, that's one thing. And the second thing is using AI to tell me things that I wouldn't be able to figure out with a human training. A lot of time sifting through data. So things like where I've potentially overcompensated and, you know, overdelivered on the network and security side or of potentially underdelivered on a security side. So having AI to, you know, assess all of those millions and probably billions of, you know, transactions and packets that are moving around our network and say, Hey, you could optimize it more if you, if you dial this down or dial this up. >>So you said earlier we, this industry has a habit of shipping products before, you know they're ready. So based on your experience, seems like, first of all, it sounds like you got a at least decent technical background as well. When do you expect to have that capability? Realistically? When can we expect that as an industry? >>I think I, I think, like I said, the the rate and nature of change is, is, I think it's accelerating. The halflife of degree is short. I think when I left university, what I, what I learned in first year was, was obsolete within five years, I'd say now it's probably obsolete of you. What'd you learn in first year? It's probably obsolete by the time you finish your degree. >>Six months. Yeah, >>It's true. So I think the, the, the rate of change and the, the partnership that I see Palo building with the likes of AWS and Google and that and how they're coming together to, to solve, to jointly solve these problems is I think we will see this within 12 months. >>Who, who are your clouds? You got multiple clouds >>Or We got multiple clouds. Mostly aws, but there are certain things that we run that run in run in Azure as well. We, we don't really have much in GCP or, or, or some of the other >>Azure for collaboration and teams, stuff like that. >>Ah, we, we run, we run SAP that's we hosted in, in Azure and our cinema ticketing system is, is was run in Azure. It's, it was only available in, in in Azure the time we're mo we are mostly an AWS >>Shop. And what do you do with aws? I mean, pretty much everything else is >>Much every, everything else, anything that's customer facing our websites, they give us great stability. Great, great availability, great performance, you know, we've had and, and, and, and a very variable as well. So, we'll, you know, our, our pattern of selling movie tickets is typically, you know, fairly flat except when, you know, there's a launch of a, of a new movie. So all of a sudden we might say you might sell, you know, at 9:00 AM when, you know, spider-Man went on sale last year, I think we sold 100 times the amount of tickets in the forest, 10 minutes. So our website didn't just scale look beautifully, just took in all of that extra traffic scale up. We're at only any intervention and then scale back down >>Taylor Swift needs that she does need that. So yeah. And so is your vision to have Palo Alto networks security infrastructure have be a common sort of layer across those clouds and maybe even some on-prem? Is it, are you, are you working toward that? Yeah, >>We, yeah, we, yeah, we, we'd love to have, you know, our end, our end customers don't really care about the infrastructure that we run. They won't be >>Able to unless it breaks. >>Unless it breaks. Yeah. They wanna be able to go to see a movie. Do you wanna be able to get on a rollercoaster? They wanna be able to go, you know, play around around a top golf. So having that convergence and that seamless integration of working across cloud network security now for most of our team, they, they don't know and they don't need to know. In fact, I, I frankly don't want them to know and be, be thinking about networks and clouds. I kind of want them thinking about how do we sell more cinema tickets? How do we give a great experience to our guests? How do we give long lasting lifetime memories to, to the people who come visit our parks? >>That's what they want. They want that experience. Right. I'd love to get your final thoughts on, we, we had you give a great overview of the ch the role that you play as Chief transformation officer. You own digital transformation, you want business transformation. What advice would you give to either other treat chief transformation officers, CISOs, CSOs, CEOs about partnering, what's the right partner to really improve your security posture? >>I think there's, there's two things. One is if you haven't looked at this in the last two years and made some changes, you're outta date. Yeah. Because the world has changed. We've seen, I mean, I've heard somebody say it was two decades worth of, I actually think it's probably five 50 years worth of change in, in Australia in terms of working habits. So one, you need to do something. Yeah. Need to, you need to have a look at this. The second thing I think is to try and partner with someone that has similar values to your organization. So Village is a, it's a wonderful, innovative company. Very agile. So the, like the, the concept of gold class cinema, so, you know, big proceeds, recliners, waiter service, elevated foods concept that, that was invented by village in 1997. Thank you. And we had thanks finally came to the states so decade later, I mean we would've had the CEO of every major cinema chain in the world come to come to Melbourne and have a look at what Village is doing and go, yeah, we're gonna export that back around around the world. It's probably one of, one of Australia's unknown exports. Yeah. So it's, yeah, so, so partnering. So we've got a great innovation history and we'd like to think of ourselves as pretty agile. So working with partners who are, have a similar thought process and, and managed to an outcome and not to a contract Yeah. Is, is important for us. >>It's all about outcomes. And you've had some great outcomes, Michael, thank you for joining us on the program, walking us through Village Roadshow, the challenges that you had, how you tackled them, and, and next time I think I'm in a movie theater and I'm in reclining chair, I'm gonna think about you and village. So thank you. We appreciate your insights, your time. Thank you. Thanks Michael. For Michael Fagan and Dave Valante. I'm Lisa Martin. You've been watching The Cube. Our live coverage of Palo Alto Networks. Ignite comes to an end. We thank you so much for watching. We appreciate you. You're watching the Cube, the leader in live enterprise and emerging emerging tech coverage next year. >>Yeah.

>> Narrator: TheCUBE presents Ignite '22, brought to you by Palo Alto Networks. >> Greetings from the MGM Grand Hotel in beautiful Las Vegas. It's theCUBE Live Day two of our coverage of Palo Alto Networks, ignite 22. Lisa Martin, Dave Vellante. Dave, what can I say? This has been a great couple of days. The amount of content we have created and shared with our viewers on theCUBE is second to none. >> Well, the cloud has completely changed the way that people think about security. >> Yeah. You know at first it was like, oh, the cloud, how can that be secure? And they realized, wow actually cloud is pretty secure if we do it right. And so shared responsibility model and partnerships are critical. >> Partnerships are critical, especially as more and more organizations are multicloud by default. Right? These days we're going to be bring Google into the conversation. Josh Haslet joins us. Strategic Partnership Manager at Google. Welcome. Great to have you Josh. >> Hi Lisa, thanks for having me here. >> So you are a secret squirrel from Palo Alto Networks. Talk to me a little bit about your background and about your role at Google in terms of partnership management. >> Sure, I feel like we need to add that to my title. [Lisa] You should, secret squirrel. >> Great. Yeah, so as a matter of fact, I've been at Google for two and a half years. Prior to that, I was at Palo Alto Networks. I was managing the business development relationship with Google, and I was kind of at the inception of when the cash came in and, and decided that we needed to think about how to do security in a new way from a platform standpoint, right? And so it was exciting because when I started with the partnership, we were focusing on still securing you know, workloads in the cloud with next generation firewall. And then as we went through acquisitions the Palo Alto added it expanded the capabilities of what we could do from cloud security. And so it was very exciting, you know, to, to make sure that we could onboard with Google Cloud, take a look at how not only Palo Alto was enhancing their solutions as they built those and delivered those from Google Cloud. But then how did we help customers adopt cloud in a more easy fashion by making things, you know more tightly integrated? And so that's really been a lot of what I've been involved in, which has been exciting to see the growth of both organizations as we see customers shifting to cloud transformation. And then how do they deploy these new methodologies and tools from a security perspective to embrace this new way of working and this new way of, you know creating applications and doing digital transformation. >> Important, since work is no longer a place, it's an activity. Organizations have have to be able to cater to the distributed workforce. Of course, the, the, the workforce has to be able to access everything that they need to, but it has to be done in a secure way regardless of what kind of company you are. >> Yeah, you're right, Lisa. It's interesting. I mean, the pandemic has really changed and accelerated that transformation. I think, you know really remote working has started previous to that. And I think Nikesh called that out in the keynote too right? He, he really said that this has been ongoing for a while, but I think, you know organizations had to figure out how to scale and that was something that they weren't as prepared for. And a lot of the technology that was deployed for VPN connectivity or supporting remote work that was fixed hardware. And so cloud deployment and cloud architecture specifically with Prisma access really enabled this transformation to happen in a much faster, you know, manner. And where we've come together is how do we make sure that customers, no matter what device, what user what application you're accessing. As we take a look at ZTNA, Zero Trust Network Access 2.0, how can we come together to partner to make sure the customers have that wide range of coverage and capability? >> How, how do you how would you describe Josh Google's partner strategy generally and specifically, you know, in the world of cyber and what makes it unique and different? >> Yeah, so that's a great question. I think, you know, from Google Cloud perspective we heard TK mention this in the keynote with Nikesh. You know, we focus on on building a secure platform first and foremost, right? We want to be a trusted cloud for customers to deploy on. And so, you know, we find that as customers do one of two things, they're looking at, you know, reducing cost as they move to cloud and consolidate workloads or as they embrace innovation and look at, you know leveraging things like BigQuery for analytics and you know machine learning for the way that they want to innovate and stay ahead of the competition. They have to think about how do they secure in a new way. And so, not only do we work on how do we secure our own platform, we work with trusted partners to make sure that customers have you mentioned it earlier, Dave the shared security model, right? How do they take a look at their applications and their workloads and this new way of working as they go to CI/CD pipelines, they start thinking about DevSecOps. How do they integrate tooling that is frictionless and seamless for their, for their teams to deploy but allows them to quickly embrace that cloud transformation journey. And so, yes, partners are critical to that. The other thing is, you know we find that, you mentioned earlier, Lisa that customers are multicloud, right? That's kind of the the new normal as we look at enterprises today. And so Google Cloud's going to do a great job at securing our platform, but we need partners that can help customers deploy policy that embraces not only the things that they put in Google Cloud but as they're in their transformation journey. How that embraces the estates that are in data centers the things that are still on-prem. And really this is about making sure that the applications no matter where they are, the databases no matter where they are, and the users no matter where they are are all secure in that new framework of deploying and embracing innovation on public cloud. >> One of the things that almost everybody from Palo Alto Networks talks about is their partnering strategy their acquisition strategy integrations. And I was doing some research. There's over 50 joint integrations that Google Cloud and Palo Alto Networks. Have you talked about Zero Trust Network Access 2.0 that was announced yesterday. >> Correct. >> Give us a flavor of what that is and what does it deliver that 1.0 did not? >> Well, great. And what I'd like to do is touch a little bit on those 50 integrations because it's been, you know, a a building rolling thunder, shall we say as far as how have we taken a look at customers embracing the cloud. The first thing was we took a look at at how do we make sure that Palo Alto solutions are easier for customers to deploy and to orchestrate in Google Cloud making their journey to embracing cloud seamless and easy. The second thing was how could we make that deployment and the infrastructure even more easy to adopt by doing first party integrations? So earlier this year we announced cloud IDS intrusion detection system where we actually have first party directly in our console of customers being able to simply select, they want to turn on inspection of the traffic that's running on Google Cloud and it leverages the threat detection capability from Palo Alto Networks. So we've gone from third party integration alone to first party integration. And that really takes us to, you know, the direction of what we're seeing customers need to embrace now which is, this is your Zero Trusts strategy and Zero Trust 2.0 helps customers do a number of things. The first is, you know, we don't want to just verify a user and their access into the environment once. It needs to be continuous inspection, right? Cause their state could change. I think, you know, the, the teams we're talking about some really good ways of addressing, you know for instance, TSA checkpoints, right? And how does that experience look? We need to make sure that we're constantly evaluating that user's access into the environment and then we need to make sure that the content that's being accessed or, you know, loaded into the environment is inspected. So we need continuous content inspection. And that's where our partnership really comes together very well, is not only can we take care of any app any device, any user, and especially as we take a look at you know, embracing contractor like use cases for instance where we have managed devices and unmanaged devices we bring together beyond Corp and Prisma access to take a look at how can we make sure any device, any user any application is secure throughout. And then we've got content inspection of how that ZTNA 2.0 experience looks like. >> Josh, that threat data that you just talked about. >> Yeah. >> Who has access to that? Is it available to any partner, any customer, how... it seems like there's gold in them, NAR hills, so. >> There is. But, this could be gold going both ways. So how, how do you adjudicate and, how do you make sure that first of all that that data's accessible for, for good and not in how do you protect it against, you know, wrong use? >> Well, this is one of the great things about partnering with Palo Alto because technically the the threat intelligence is coming from their ingestion of malware, known threats, and unknown threats right into their technology. Wildfire, for instance, is a tremendous example of this where unit 42 does, you know, analysis on unknown threats based upon what Nikesh said on stage. They've taken their I think he said 27 days to identification and remediation down to less than a minute, right? So they've been able to take the intelligence of what they ingest from all of their existing customers the unknown vulnerabilities that are identified quickly assessing what those look like, and then pushing out information to the rest of their customers so that they can remediate and protect against those threats. So we get this shared intelligence from the way that Palo Alto leverages that capability and we've brought that natively into Google Cloud with cloud intrusion detection. >> So, okay, so I'm, I'm I dunno why I have high frequency trading in my mind cause it used to be, you know, like the norm was, oh it's going to take a year to identify an intrusion. And, and, and now it's down to, you know take was down to 27 days. Now it's down to a minute. Now it's not. That's best practice. And I'm, again, I'm thinking high frequency trading how do I beat the speed of light? And that's kind of where we're headed, right? >> Right. >> And so that's why he said one minute's not enough. We have to keep going. >> That's right. >> So guys got your best people working on that? >> Well, as a matter of fact, so Palo Alto Networks, you know when we take a look at what Nikesh said from stage, he talked about using machine learning and AI to get ahead of what we what they look at as far as predictability not only about behaviors in the environment so things that are not necessarily known threats but things that aren't behaving properly in the environment. And you can start to detect based on that. The second piece of it then is a lot of that technology is built on Google Cloud. So we're leveraging, their leveraging the capabilities that come together with you know, aggregation of, of logs the file stitching across the entire environment from the endpoint through to cloud operations the things that they detect for network content inspection putting all those files together to understand, you know where has the threat vector entered how has it gone lateral inside the environment? And then how do you make sure that you remediate all of those points of intrusion. And so yeah it's been exciting to see how our product teams have worked together to continue to advance the capabilities for speed for customers. >> And secure speed is critical. We had the opportunity this morning to speak with Lee Claridge, the chief product officer, and you know one of the things that I had heard about Lee is that despite all of the challenges in cybersecurity and the amorphous expansion of the threat network and the sophistication of the adversaries he's really optimistic about what it's going to enable organizations to do. I see you smiling. Do you share that optimism? >> I, I do. I think, you know, when you bring, when you bring leaders together to tackle big problems, I think, you know we've got the right teams working on the right things and we understand the problems that the customers are facing. And so, you know, from a a Google cloud perspective we understand that partnering with Palo Alto Networks helps to make sure that that optimism continues. You know, we work on continuous innovation when it comes to Google Cloud security framework, but then partnering with Palo Alto brings additional capabilities to the table. >> Vision for the, for the partnership. Where do you want to see it go? What's... we're two to five years down the road, what's it look like? Maybe two to three years. Let's go. >> Well, it was interesting. I, I think neer was the one that mentioned on stage about, you know how AI is going to start replacing us in our main jobs, right? I I think there's a lot of truth to that. I think as we look forward, we see that our teams are going to continue to help with automation remediation and we're going to have the humans working on things that are more interesting and important. And so that's an exciting place to go because today the reality is that we are understaffed in cybersecurity across the industry and we just can't hire enough people to make sure that we can detect, remediate and secure, you know every user endpoint and environment out there. So it's exciting to see that we've got a capability to move in a direction to where we can make sure that we get ahead of the threat actors. >> Yeah. So he said within five years your SOC will be AI based and and basically he elaborated saying there's a lot of stuff that you're doing today that you're not going to be doing tomorrow. >> That's true. >> And that's going to continue to be a moving target I would think Google is probably ahead in that game and ahead of most, right? I mean, you guys were there early. I mean, I remember when Hadoop was all the rage like just at the beginning you guys like, yeah, you know Google's like, no, no, no, we're not doing Hadoop anymore. That's like old news. So you tended to be, I don't know, at least five maybe seven years ahead of the industry. So I imagine you using a lot of those AI techniques in your own business today. >> Absolutely. I mean, I think you see it in our consumer products, and you certainly see it in the the capabilities we make available to enterprise as far as how they can innovate on our cloud. And we want to make sure that we continue to provide those capabilities, you know not only for the tools that we build but the tools that customers use. >> What's the, as we kind of get towards the end of our conversation here, we we talk about zero trust as, as a journey, as an approach. It's not a product, it's not a tool. What is the, who's involved in the zero trust journey from the customers perspective? Is this solely with the CSO, CSO, CIOs or is this at the CEO level going, we have to be a data company but we have to be a secure data company 24/7. >> It's interesting as you've seen malware, phishing, ransomware attacks. >> Yeah. >> This is not only just a CSO CIO conversation it's a board level conversation. And so, you know the way to address this new way of working where we have very distributed environments where you can't create a perimeter anymore. You need to strategize with zero trust. And so continuously, when we're talking to customers we're hearing that as a main initiative, you know from the CIO's office and from the board level. >> Got it, last question. The upgrade path for existing customers from 1., ZTNA 1.0 to 2.0. How simple is that? >> It's easy. You know, when we take- >> Is there an easy button? >> So here's the great thing [Dave] If you're feeling lucky. [Lisa] Yeah. (group laughs) >> Well, Palo Alto, right? Billing prisma access has really taken what was traditional security that was an on-prem or a data center deployed strategy to cloud-based. And so we've worked with customers like Princeton University who had to quickly transition from in-person learning to distance learning find a way to ramp their staff their faculty and their students. And we were able to, you know Palo Alto deploy it on Google Cloud's, you know network that solution in very quick order and had those, you know, everybody back up and running. So deployment and upgrade path is, is simple when you look at cloud deployed architectures to address zero trusts network. >> That's awesome. Some of those, some of those use cases that came out of the pandemic were mind blowing but also really set the table for other organizations to go, yes, this can be done. And it doesn't have to take forever because frankly where security is concerned, we don't have time. >> That's right. And it's so much faster than traditional architectures where you had to procure hardware. >> Yeah. >> Deploy it, configure it, and then, you know push agents out to all the endpoints and and get your users provisioned. In this case, we're talking about cloud delivered, right? So I've seen, you know, with Palo Alto deploying for customers that run on Google Cloud they've deployed tens of thousands of users in a very short order. You know, we're talking It was, it's not months anymore. It's not weeks anymore. It's days >> Has to be days. Josh, it's been such a pleasure having you on the program. Thank you for stopping by and talking with Dave and me about Google Cloud, Palo Alto Networks in in addition to secret squirrel. I feel like when you were describing your background that you're like the love child of Palo Alto Networks and Google Cloud, you might put that on your cartoon. >> That is a huge compliment. I really appreciate that, Lisa, thank you so much. >> Thanks so much, Josh. [Josh] It's been a pleasure being here with you. [Dave] Thank you >> Oh, likewise. For Josh Haslett and Dave, I'm Lisa Martin. You're watching theCUBE, the leader in live coverage for emerging and enterprise tech. (upbeat outro music)

(upbeat music) >> Okay, Chloe, thank you very much. Hey folks, in here in the Cloud City We with Danielle Royston. Great to see you. Watching you up on stage, I got to say, as the CEO of TelcoDR, leader and chief executive of that company. As well as a great visionary, you laid out the vision. It's hard to debate that. I mean, I think there's people who will say that vision, is like freedom, no one can debate it. It's not going to happen. >> Yeah, there's still a lot of debate in our industry about it. There's a lot of articles being written about it. I've referenced one about, you know, should we let the dragons into the castle? For me, I think it's super obvious. I think other industries are like "Duh, we've made the move." And Telco is still like, "Hmm, we're not sure." And so, am I a visionary, I don't know. I'm just sort of just Babe Ruth-ing it a little bit. I think that's where we're going. >> You know you do, you have a lot of content, podcasts, you write blogs, you do a lot of speaking. You brought it all together on stage, right? That has got to feel good. >> Yeah. >> You've got a body of work and it came together very nicely. How did you feel up there? >> Oh my God, it's absolutely nerve wrecking. I sort of feel like, you know, could you tell if my hands were shaking? Right, could you tell that my heart was racing? >> It's a good feeling. >> I don't know. >> Come on! >> I'll be honest, I'm happy it's over, I'm happy. I think I did a really great job and I'm really happy >> Yeah, you did a great job, I love the dragon reference-- >> Have it in the can. >> Fantastic, loved the Game of Thrones vibe there. It was cool-- >> Totally. >> One of the things I wanted pick up on, I thought it was very interesting and unique was the iPhone reference 14 years ago, because that really, to me, was a similar moment because that shifted the smartphone. A computer that happened to make phone calls. And then we all knew who was the leader at that time, Nokia, Blackberry with the phones, and they became toast. That ushered in a whole another era of change, wealth creation, innovation, new things. >> Yeah. Well, up until that moment, carriers had been designing the phones themselves. They were branded with their logos. And so Steve Jobs fought for the design of the iPhone. He designed it with the consumer, with the user in mind. But I think what it really, I mean, it's such a big pivotal moment in our industry because it singled the end of voice revenue and ushered in the era of data. But it also introduced the OTT players, right? That came in through the apps and started a siphon approved from the carriers. And this is like, it's a pivotal moment in the industry, like, changed the industry forever. >> It's a step function, it was a step function change, it's obvious, everyone knew it. But what's interesting is that we were riffing yesterday about O-RAN and Android. So you have iPhone, but Android became a very successful open source project that changed the landscape of the handset. Some are saying that that kind of phenomenon is coming here. Into Telco with software, kind of like an Android model where that'll come in. What's your thoughts on that, reaction to that? >> Yeah, well the dis-aggregation of the hardware, right? We're in the iconic Erickson booth, right? They get most of their revenue from RAN, from Radio Access Networks. And now with the introduction of Open RAN, right? With 50% less CapEx, 40% less OPEX, you know, I think it's easiest for Greenfield operators like Dish, that are building a brand new network. But just this month, Vodafone announced they're going to build the world's largest Open RAN network. Change is happening and the big operators are starting to adopt Open RAN in a real big way. >> So to me, riding the dragon means taking the advantage of new opportunities on top of that dragon. Developing apps like the iPhone did. And you mentioned Android, they got it right. Remember the Windows Phone, right? They tried to take Windows and shove it to the phone-- >> Barely. >> It was a kin phone too. >> I try to delete it from my, look here, beep! >> I'm going to take this old world app and I'm going to shove it into the new world, and guess what, it failed. So if the Telco is trying to do the same thing here, it will fail, but if they start building 5G apps in the cloud and pick the cloud native and think about the consumer, isn't really that the opportunity that you're talking about? >> Well, I think it is, absolutely. And I think it's a wake up call for the vendors in our space, right? And I'm certainly trying to become a vendor with Totogi. I'm really pushing my idea. But you can't take, using your Windows example on the Windows Phone, you can't take a Windows app and stuff it onto a phone and you can't take these old school applications that were written 20 years ago and just stuff them into the cloud, right? Cloud is not a place, it's a way to design applications and it all needs to be rewritten and let's go write, rewrite it. >> It's not a destination as we always say. Let's take a step back on the keynote 'cause I know we just did a couple of highlights there, wasn't the whole thing. We were watching it, by the way, we thought you did a great job, you were very cool and calm under pressure. But take us through the core ideas in the keynote. Break down the core elements of what the talk was about. >> Yeah, I think the headline really is, you know, just like there were good and bad things about the iPhone, right? It killed voice, but introduced data and all these other things. There's good and bad things about the public cloud, right? It's not going to be smooth sailing, no downsides. And so I acknowledge that, even though I'm the self appointed queen, you know? This self appointed evangelist. And so, I think that if you completely ignore the public cloud, try to stick your head in the sand and pretend it doesn't exist, I think there's nothing but downsides for Telcos. And so I think you need to learn how to maximize the advantage there, ride he dragon, like spew some fire and, you know, get some speed and height, and then you can double your ARPU. But I think, going from there, so the next three, I was trying to give examples of what I meant by that, of why it's a double-edged sword, why it's two sides of the coin. And I think there's three areas, which is the enterprise, the network, and a relationship with subscribers. And so that really what the talk, that's what the talk is about >> The three main pillars. >> Yeah, yeah! >> Future, work, enterprise, transition, Open RAN. >> The network and then the relationship with the subscribers. >> Those are the structural elements you see. >> Yeah, yeah, yeah. >> What's the most important one you think, right now, that people are focused on? >> I mean, I think the first one, with work, that's an easy one to do, because there's not too much downside, right? I think we all learned that we could work productively from home. The reason public cloud matter there is because we had tools like Zoom and G Suite and we didn't need to be, I mean, imagine if that this had happened even 20 years ago, right? Broadband at the home wasn't ready, the tools weren't ready. I mean, it would have been, I mean a bigger disaster than it was, right? And so this is an opportunity to sort of ride this work from home wave that a lot of CEOs are saying, we're not coming back or we're going to have smaller offices. And all of those employees need fiber to their home. They need 5G at their home. I mean, if I'm a head of enterprise in a Telco, I am shifting my 5G message from like random applications or whatever, to be like, how are you getting big pipes to the home so your workers can be productive there? And that, I don't hear Telco's talking about that and that's a really big idea. >> You know, you say it's a no brainer, but it's interesting you had your buildings crumbling, which was great, very nice effect in the talk. I heard a executive, Wall Street executive the other day, talking about how, "My people will be back in the office. "I'm going to mandate vaccinations, they're going to be back "in the office, you work for me. "Even though it's an employee friendly environment "right now, I don't care". And I was shocked. I go, okay, this is just an old guy. But, and it's not just the fact that it's an old guy, old guard doing that because I take two examples of old guys, Michael Dell and Frank Slootman. >> Yeah. >> Right, Michael Dell, you know, hundred billion dollar company, Frank Slootman, hottest, you know, software company. Both of them, sort of agree. It's a no brainer. >> Yeah. >> Why should I spend all this money on buildings? And my people are going to be more productive. They love it, so. Why fight the fashion? >> Well, I think the office and I can talk about this for a long time and I know we don't have that much time, but on offices, it's a way to see when did you come in and when did you leave, and look over your shoulder and what we're working on. And that's what offices are for. Now, we tell ourselves it's about collaboration and all this other stuff. And you know, these guys are saying, "come back to the office." It's because they don't have an answer on how to manage productivity. What are you working on? Are you off, are you authentically working 40 hours a week? I want to see, I know if at least you're here, you're here. Now, you might be playing, you know, Minesweeper. You might be playing Minesweeper on your computer, but at least you were, your butt was at your computer. So yeah, I think this is a pivotal moment in work. I think Telcos could push it, to work from home. We'll get you the pipes, we'll get you the cloud-based tools to help manage productivity, to change in work style. >> Yeah, and we've covered this in theCube many times, about how software is going to enable this virtual first model, no one's actually built software for virtual first. I think that's going to happen. Again, back to your team software, but I want to ask you about software defined infrastructure. You mentioned O-RAN, and as software eats the world and eats infrastructure, you still need infrastructure. So, talk about the relationship of how you see O-RAN competing and winning with the balance of software versus the commodity argument. >> Yeah, and I think this is really where people get scared in Telco. I mean, authentically nervous, right. Where you're like, okay, really the public cloud is at that network edge, right? We're really going to like, who are we? It's an identity crisis. We're not the towers anymore. We're renting space, right? We're now dis-aggregating the network, putting the edge cloud right there and it's AWS or Google. Who are we, what do we do, are we networks? Are we a tech company? Right, and so I'm like, guys, you are your subscribers and you don't focus on that. I mean, it's kind of like a last thought. >> So you're like a therapist then too, not just an evangelist. >> I'm a little bit of a therapist. >> Okay, lay down on the couch, Telco. >> Let's talk about what your problems are. (laughs) >> They have tower issues. >> All seriousness, no but, the tower is changing is backhauling. Look at direct connects for instance. The rise of direct and killed the exchanges. I mean, broadband, backhaul, last mile, >> Yeah. >> Completely, still issues, >> Yeah. >> But it's going to software and so that's there. The other thing I want to get to quickly, I know we don't have a lot of time, is the love relationship you talk about with subscribers. We had Peter Adderton on, from a Boost Mobile, formerly Boost Mobile, earlier. He was saying, if you don't have a focus on the customer, then you're just selling minutes and that's it. >> Yeah. >> And his point was, they don't really care. >> Yeah. Let's talk about organizational energy, right? How much energy is contained within any organization, not just Telco, but any organization. To some of your people time is the hours they work per week. And then you think of that as a sack on how you're allocating your time and spending your time, right? And so I think they spend 50% of their time, maybe more, fighting servers, machines, the network, right? And having all these battles. How much of that organizational energy is dedicated to driving great subscriber experiences? And it just shrunk, right? And I think that's where the public cloud can really help them. Like ride the dragon. Let the dragon deal with some of this underlying stuff. So that you can ride a dragon, survey the land, focus on your subscriber and back to the software. Use software, just like the OTT players are doing. They are taking away your ARPU. They're siphoning your ARPU, 'cause they're providing a better customer experience. You need to compete on that dimension. Not the network, not the three Telcos in the country. You're competing again, WhatsApp, Apple, Amazon, Facebook. And you spent how much of your organizational energy to focus on that? Very small. >> And that's where digital platforms roll by, it uses the word platform, why? Because everybody wants to be a platform. Why do you want to be a platform? Because I want to be like Amazon, they're a platform. And you think about Netflix, right? It's not, you know, you don't think about Netflix UK or Netflix Spain, right? >> It's global. >> There's one Netflix >> Yeah, yeah. >> You don't think about their marketing department or their sales department or their customer service, you think about the app. >> Yeah. >> You know. One interface. And that's what digital platforms allow you to do. And granted, there's a lot of public policy to deal with, but if you're shooting satellites up in space, >> Yeah. >> You know, now, you own that space, right, global network. >> And what makes Netflix so good, I think, is that it knows you, right? It knows what you're watching and recommends things, and you're like, "Oh, I would like that, that's great." Who knows more about you than your mobile phone? Carry it everywhere you go, right? What you're watching, what you're doing, who you're calling, what time did you wake up? And right now all of that data we talked about a couple of days ago, it's trapped in siloed old systems. And like why do people think Google knows so much about you? Telco knows about you. And to start to use that to drive a great experience. >> And you've got a great relationship with Netflix. The relationship we have with our our carrier is to your admin, "can you call these guys? "I don't know, I lost the password, I can't get in". >> Right. >> It's like-- >> Or you get SIM hacked-- >> I don't have an hour and a half to call your call center 'cause you don't have a chat bot, right. >> I don't have time. >> Chat bot, right. I can't even do the chat bot because my problem is, you're like, I got to talk to someone. All of their systems are built with the intention of a human being on the other side, and there's all this awesome chat bot AI that works. >> Yeah. >> Set it free. >> Yeah, yeah, right. You almost rather go to the dentist, then calling your carrier. >> Well, we're going to wrap things up here on the keynote review. Did you achieve what you wanted to achieve? I mean, controversy, bold vision, leadership, also that came across, but people they know who you are now. You're out there and that's great news. >> Yeah. I think I rocked the Telco universe and I'm really, that was my goal, and I think I accomplish it so, very excited. >> Well, we love having you on theCUBE. It's great to have great conversations, not only are you dynamic and smart, you're causing a lot of controversy, in a good way and getting, waking people up. >> Making people talk, that's a start. >> And I think, the conversations are there. People are talking and having relationships on the ecosystem open, it's all there. Danielle Royston, you are a digital revolution, DR. Telco DR, thanks for coming to theCube. >> Thank you so much, always fun. >> Good to see you. >> Thanks. >> Of course, back to the Cloud City studios. Adam is going to take it from here and continue on day three of theCube. Adam in studio, thanks for having us and take it from here.

>> Narrator: Live, from San Diego, California, it's The Cube, covering Cisco Live, US, 2019. Brought to you by Cisco, and it's Ecosystem Partners. >> Welcome back to San Diego, everybody, you're watching The Cube, the leader in live tech coverage. My name is Dave Volante. I'm here with my co-host Stu Miniman, we're covering day two here of Cisco Live, 2019. Anand Oswal is here, he's the Senior Vice President of Enterprise Networking Engineering at Cisco, and John Apostolopoulos. The Italians and the Greeks, we have a lot in common. He is the VP and CTO of Enterprise Networking at Cisco. Gentlemen, welcome to The Cube. How did I do? >> You did awesome. >> Dave: Not too bad, right? Thank you. (chuckles) All right. Anand, let's start with you. You guys have had a bunch of news lately. You're really kind of re-thinking access to the network. >> Anand: Yeah. >> Can you explain what's behind that, to our audience? >> Yeah. If you think about it, the network is running more and more critical infrastructure. At the same time, it's increasing modern scale and complexity. What we expect, is that you always need wireless on. The workspace is on the move. You're working here, in your office, in the cafe, in the soccer field, everywhere. You want an uninterrupted, unplugged experience. For that, it's wireless first, it's cloud-driven, and it's data-optimized. So, we had to rethink how we do access. It's not just about your laptops and your phones on the wireless network, in the enterprise it's digital management systems. IOD devices, everything's connected wirelessly. And we need to rethink the access, on that part. >> So John, this obviously ties in to, you know, you hear all the buzz about 5G and WIFI 6. Can you explain the connection and, you know, what do we need to know about that? >> Okay, so 5G and WIFI 6 are two new wireless technologies, which are coming about now, and they're really awesome. So, WIFI 6 is the new version of WIFI. It's available today, and it's going to be available predominantely indoors. As we use WIFI indoors, in high-density environments, where we need a large database per square meter. And the new WIFI 6, the coverage indoors. 5G is going to be used predominately outdoors, in the cellular frequency. Replacing conventional 4G or LTE, and it'll provide you the broad coverage as you roam around, outdoors. And what happens though, is we need both. You need great coverage indoors, which WIFI 6 can provide, and you need great coverage outdoors, which 5G will provide. >> So, the 4G explosion kind of coincided with mobile-- >> Anand: Yep. >> Obviously, and that caused a huge social change-- >> Anand: Yep. >> And of course, social media took off. What should we expect with 5G, is it, you know, I know adoption is going to take a while, we'll talk about that, but it feels like it's more, sort of, B-to-B driven, but maybe not. Can you, sort of, give us your thoughts there. >> Well think about it, if you see WIFI 6 and 5G have actually been on some similar fundamental technology building blocks. You know, you've all been at a ball game. Or the Warriors game, like a few weeks ago, when they were winning. And, after a great play, you're trying to send that message, a video to your kid or something, and the WIFI is slow, latency. With WIFI 6, you won't have that problem. 'Cause WIFI 6 has four times the latency, sorry, four times the throughput and capacity as existing WIFI. Lower latency. And also, the battery life. You know, people say that batteries are the most important thing today, like in the Maslow Hierarchy Chart-- >> Dave: Yeah, yeah, yeah. >> Three times the battery life, for WIFI 6 endpoints. So, you're going to see a lot of use cases where you have inter-working with WIFI 6 and 5G. WIFI 6 for indoors, and 5G for outdoor, and there'll be some small overlap, but the whole idea is that, how do you ensure that these two disparate access networks are talking to each other? Exchanging security, policy, and there is some visibility. >> Okay, so, well, first of all, you're a Warriors fan, right? >> Anand: Yeah, I am. >> Awesome, we want to see this series keep going. >> Game six, baby! >> That was really exciting. Now of course, I'm a Bruins fan, so we're on the plane the other night, and the JetBlue TV shut down, you know, so I immediately went to the mobile. >> Yeah. >> But it was a terrible experience, I was going crazy. Texting my friends, what's happening? >> Anand: Yeah. >> You're saying that won't happen-- >> Anand: Yeah. >> With 5G and WIFI 6? >> Anand: Yeah. Exactly. >> Oh, awesome. >> So, John, help connect for us, Enterprise Networking. We've been talking about the new re-architectures, you know, there's ACI, there's now intent-based networking, how does this play into the 5G and WIFI 6 discussion that we're having today? >> Okay, so one of the things that really matters to our customers, and to everybody, basically, is that they want the sort of end-to-end capability. They have some devices, they want to talk through applications, they want access to data, they want to talk with other people, or to IoT things. So you need this sort of end-to-end capability, wherever the ends are. So one of the things we've been working on for a number of years now, is first of all intent-based networking, which we announced two and a half years ago. And then, multi-domain, where we try to connect across the different domains. Okay, across campus, and WAN, and data center, all the way to the cloud, and across the service finder network. And to add security, as foundational across all of these. This is something that Dave Goeckeler and Chuck Robbins talked about at their keynote yesterday. And this is a huge area for us, 'cause we're going to make this single-orchestrated capability for our customers, to connect end-to-end, no matter where the end devices are. >> All right, so Anand, I have to believe that it's not the poor, you know, administrator, saying, oh my God, I have all these pieces and I need to manage them. (laughing) Is this where machine learning and AI come in to help me with all these disparate systems? >> Absolutely. Our goal is very simple. Any user, on any device, should have access to any application. Whether it's sitting in a data center, in a cloud, or multiple clouds. Or any network. You want that securely and seamlessly. You also want to make sure that the whole network is orchestrated, automated, and you have the right visibilities. Visibilities for ID, and visibility for business insights. Talk of AI and ML, what's happening is that as the network is growing in complexity and scale, the number of alerts are growing up the wazoo. So you are not able to figure it out. That's where the power of AI and machine learning comes. Think about it. In the industrial revolution, the industrial revolution made sure that you don't have the limitations of what humans can do, right? You had machines. And now, we want to make sure that businesses can benefit in the digital revolution. You're not limited by what I can pass through the logs and scrolls. I want to automate everything. And that's the power of AI and machine learning. >> Are there use cases where you would want some human augmentation, where you don't necessarily want the machine taking over for you, or do you see this as a fully-automated type of scenario? >> Yeah, so what happens is, first of all, visibility is really, really important. The operator of a network wants to have visibility, and they want end-to-end across all these domains. So the first thing we do is we apply a lot of machine learning, to take that immense amount of data, as Anand mentioned, and to translate it into pieces of information, to insights into what's happening. So then we can share to the user and they can have visibility in terms of what's happening and how well it's happening, are they anomalies, or is there a security threat, so forth. And then, we can provide them additional feedback. Hey, this is ananomaly, this could be a problem. This is the root cause of the problem, and we believe these are the solutions for it. What do you want to do? Do you want to actuate one of these solutions? And then they get to choose. >> And if you think about the other way, our goal is really to take the bits and bites of data in the network, convert that data into information. That information into insights. That insights that lead to outcomes. Now, you want to also make sure that you can augment the power of AI and machine learning on those insights, so you can drill down exactly what's happening. So, for example, you want to first baseline your network. What's normal for your environment? And when you have deviations. That's anomalies. Then you narrow down exactly what the problem is. And then you want to automate the remediation of that problem. That's the power of AI and ML. >> When you guys, as engineers, when you think about, you know, applying machine intelligence, there's a lot of innovation going on there. Do you home-grow that? Do you open source it? Do you, you know, borrow? Explain the philosophy there, in terms of from a development standpoint. >> Yeah. From a development point of view it's a combination of all the other aspects. We will not reinvent what already exists, but there's always a lot of secret sauce that you need to apply, because everything flows to the network, right? If everything flows to the network, Cisco has a lot of information. It's not just a data lake. We're a data source as well. So taking this disparate source of information, normalizing it, harmonizing it, creating a language, applying the algorithm of AI and machine learning. For example, we do the model learning and training in the cloud. We do inference in the cloud, and you push the rules down. So it's a combination of all of the aspects we talked about. >> Right, and you use whatever cloud tooling is available. >> Yes. >> But it sounds like from a Cisco engineering standpoint, it's how you apply the machine intelligence, for the benefit of your customers and those outcomes-- >> Anand: Yeah. >> Versus us thinking of Cisco as this new AI company, right? >> Anand: Yeah. >> That's not the latter, it's the former, is that fair? >> So one of the things that's really important is as you know, Cisco's been making, we've been designing our A6 for many years, with really, really rich telemetry. And as you know, data is key to doing good machine learning and stuff. So we've been designing the A6, to do do real time at wire speed telemetry. And also to do various sorts of algorithmic work on the A6 to figure out, hey, what is the real data you want to send up? And then we've optimized the OS, IOS XE, to be able to perform various algorithms there, and also to host containers where you can do more machine learning at the switch, at the router, even in the future, maybe, at the AP. And then with DNA center, we've been able to gather all of the data together, in a single data lake, where we can perform machine learner on top. >> That's a very important point John mentioned, because you want layer one to layer some of the analytics. And that's why the Catalyst 9120 access point we launched has the Cisco RF ASIC, that provides things like clean air for spectrum, we've also got the analytics from layer one level, all the way to layer seven. >> Yeah, I really like the line actually, from Chuck Robbins yesterday, he said, the network sees everything and Cisco wants to you know, give you that visibility. Can you walk us through some of the new pieces, what people, either things that, they might not have been aware of, or new announcements this week. >> So, as part of the Cisco AI network analytics, we announced three things. The first thing is automated baselining. What that really means is that, what's normal for your environment, right? Because what's normal for your own environment might not be the same for my environment. Once I understand what that normal baseline is, then, as I have deviations, I can do anomaly detection. I can correlate and aggregate issues. I can really bring down apply AI and machine learning and narrow down the issues that are most critical for you to look at right now. Once I narrow down the exact issue, I go on to the next thing, and that is what we call machine reasoning. And machine reasoning is all about automating the workflow of all you need to do to debug and fix a problem. You want the network to become smarter and smarter, the more you use it. And all of this is done through model learning and training in the cloud, inference in the cloud, and pushing it down, the rules as we have devices online, on plan. >> So do you see the day, if you think about the roadmap for machine intelligence, do you see the day where the machine will actually do the remediation of that workflow? >> Absolutely. That's where we need to get to. >> When you talk about the automated baselining, I mean there's obviously a security, you know, use case there. Maybe talk about that a little bit, and are there others? Really, it depends on your objective, right? If my objective is to drive more efficiency-- >> Yeah. >> Lower costs, I presume a baseline is where you start, right? So... >> When I say, baseline, what I mean really is like, say if I tell you that on this laptop, to connect to the WIFI network, it took you three seconds. And I ask you is that good or bad? You'll say, I don't know. (laughs) >> What's the baseline for the environment? >> Dave: Yeah. >> What's normal? And next time, if you take eight seconds, and your baseline is three, something is wrong. But, what is wrong? Is it a laptop issue? Is it a version on there, on your device? Is it an application issue? A network issue? An RF issue? I don't know. That's where AI machine learning will determine exactly what the problem is. And then you use machine reasoning to fix the problem. >> Sorry, this is probably a stupid question, but, how much data do you actually need, and how much time do you need, to actually do a good job in that type of use case? >> Well, what happens is you need the right data, okay? And you're not sure where the right data is. (chuckles) >> So originally what we'd do, a lot of our expertise, that Cisco has for 20 years, is figuring out what the right data is. And also, with a lot of the machine learning we've done, as well as machine reasoning, where we put together templates and so forth, we've basically gathered the right data, for the customer, and we refined that over time. So over time, like, this venue here, the way this venue's network, what it is, how it operates and so forth, varies with time, and we need to refine that over time, keep it up to date, and so forth. >> And when we talk about data, we're talking about tons of metadata here, right? I mean, do you ever see the day where there'd be more metadata than data? (laughs) >> Yeah-- >> Rhetorical question. (laughs) >> All right, so-- >> It's true though, it's true. >> Right? (laughing) >> We're here in the DevNet zone, lots of people learning about building infrastructures, code, tell us how the developer angle fits into what we've been discussing here. >> Oh, yes. So what happens is, as part of intent-based networking, a key part's the automation, right? And another key part's the assurance. Well, it's what DevNet's trying to do right now, by working with engineering, with us, and various partners, other customers, is they're putting together, what are the key use cases that people have, and what is code that can help them get that done? And what they're also doing, is they're trying to, they're looking through the code, they're improving it, they're trying to instill best practice and stuff, so it's a reasonably good code, that people can use and start building off of. So we think this can be very valuable for our customers to help move into this more advanced automation, and so forth. >> So, architecture matters, we sort of touched upon it, but I want you to talk more about multi domain architecture. We heard Chuck Robbins, you know, talk about it. What is it, why is it such a big deal, and how does it give Cisco a competitive advantage? >> Think about it, I mean, multi domain architecture's nothing but all the components of a modern enterprise network behind the scenes. From giving access to a user or device, to access to an application, and everything in between. Now traditionally, each of these domains, like an access domain, the WAN domain, can have hundreds of thousands of network nodes and devices. Each of these are configured, generally manually, the the CLI. Multi domain architecture's all about stitching these various domains into one cohesive, data-driven, automated, programmable network. So, your campus, your branch, your WAN, your data center and cloud, with security as an integral part of it, if at all. >> So, it's really a customer view of an architecture, isn't it. >> Absolutely. Yeah. Absolutely. >> Okay. It's good, I like that answer. I thought you were going to come out with a bunch of Cisco-- >> Anand: No. >> Mumbo-jumbo and secret sauce-- >> No. >> But it really is, you guys thinking about, okay, how would our customers need to architect their network? >> Exactly. Because if you think about it, it's all about a customer use case. For example, like, we talked earlier, today we are working everywhere. Like, on the poolside, in the cafe, in the office, and always on the go. You're accessing your business-critical applications, whether that's Webex, salesforce.com, O365. At the same time, you're reading Facebook, and WhatsApp, and YouTube, and other applications. Cisco's SD-WAN domain will talk to Cisco's ACI domain, exchange SLAs and policies, so now you can prioritize that application that you want, which is business-critical. And place the right part, for the best experience for you. Because you want the best experience for that app, no matter where you are. >> Well, and the security implications too, I mean-- >> Anand: Absolutely. >> You're basically busting down the security silos-- >> Yeah. >> Dave: And sort of the intent here, right? >> Yeah. Absolutely. >> Great. All right, last thoughts on the show, San Diego, last year we were Orlando, we were in Barcelona earlier this year, your thoughts about that. >> I think it's been great so far. If you think about it, in the last two years we've filled out the entire portfolio for the new access network. On the Catalyst 9100 access points, with WIFI 6, the switches, next generation campus core, the wireless LAN controller, eyes for unified policy, DNA center for automation, analytics, DNA spaces for business insights, the whole access network has been reinvented, and it's a great time. >> Nice, strong summary, but John, we'll give you the last word. >> What happens here is also, everything Anand says, and we have 5000 engineers who've been doing this over multiple years, and we have a lot more in the pipe. So you're going to see more in six months from now, more in nine months, and so forth. It's a very exciting time. >> Excellent. Guys, it's clear you, like you say, completing the portfolio, positioning for the next wave of access, so congratulations on all the hard work, I know a lot goes into it >> Thank you. >> Thank you very much for coming on The Cube. >> Thank you so much. >> All right, keep right there, Dave Volante with Stu Miniman, Lisa Martin is also in the house. We'll be back with The Cube, Cisco Live 2019, from San Diego. (fast electronic music)

>> Live from San Diego, California It's the queue covering Sisqo live US 2019 Tio by Cisco and its ecosystem. Barker's >> Welcome back to San Diego. Everybody watching the Cube, the leader and live check coverage. My name is David Locke. I'm here with my co host student in recovering Day to hear Sisqo live. 2019 on. On On. On on. Oswald is here. Excuse me. Sees the senior vice president of enterprise networking Engineering at Cisco. And John A postal, a polis. Italians in the Greeks. We have a lot in common. He is the VP and CTO of Enterprise Network. And get Sisko. Gentlemen, welcome to the Cube. How'd I do? Do you know it? Also, that you're bad, right? Thank you. All right, Good. Deal it out. Let's start with you. You guys have had a bunch of news lately. Uh, you're really kind of rethinking access to the network. Can you explain what's behind that to our audience? >> Yeah, even think about it. The network is getting has running more and more critical. Infrastructure at the same time is increasing. Bottom scale and complexity. What? We expected that you'll only be obvious. Violence on workspace is on the move. Are you? You're working here in your office, in the cafe, The sock off everywhere you want. An uninterrupted unplugged experience for that is violence. First, it's cloud driven and is dead optimist. So we had to rethink our way to access. It's not just about your laptops and your fool on the wireless network. In the end of the digital management systems, Coyote devices, everything is going to provide us with means reaching the access on that. But >> so, John, this obviously ties into, you know, you hear all the buzz about five g and WiFi. Six. Can you explain the connection? And you know what? We need to know about that. >> Okay, it's so fine. Five. Jean WiFi 62 new wireless technologies coming about now, and they're really awesome. So y fi six is the new version. WiFi. It's available today, and it's going to be available for down predominately indoors as wi WiFi indoors and high density environments where you need a large number. Large data bait for square meter una WiFi. Once again, the new WiFi six fight in the coverage indoors uh, five is going to be used predominately outdoors in the cellular frequency. Replacing conventional for Geo lt will provide you The broad coverage is your roam around outdoors. And what happens, though, is we need both. You need great coverage indoors, which wife Isis can provide, and you need great coverage outdoors. Which five year cried >> for G explosion kind of coincided with mobile yet obviously, and that caused a huge social change. And, of course, social media took off. What should we expect with five G? Is it? You know, I know adoption is gonna take a while. I'll talk about that, but it feels like it's more sort of be to be driven, but but maybe not. Can you >> see why 5 65 gr actually billions Some similar fundamental technology building blocks? You know you will be in the ball game for the Warriors game like a few weeks ago when they were winning on DH. After a bit of time to send that message. Video your kid something on the WiFi slow laden Z with WiFi, 61 have a problem. The WiFi six has four times the late in C 14. The throughput and capacity has existing y find Lowell Agency and also the battery life. You know, people say that that is the most important thing today. Like in the mass Maharaj three times the battery life for WiFi, 16 points. So you're gonna see a lot of use cases where you have inter walking within 556 and five g WiFi six foot indoors and find you for outdoor and some small overlap. But the whole idea is how do you ensure that these two disparate access networks are talking to each other explaining security policy and it is invisibility. >> Okay, so first what? Your warriors fan, right? Yeah. Awesome way. Want to see the Siri's keep going, baby? That was really exciting. Because I'm a Bruins fan, sir, on the plane the other night and in the JetBlue TV. Shut down, you know, So I immediately went to the mobile, But it was terrible experience, and I was going crazy checks in my friends. What's happening? You say that won't happen? Yeah, with five Julia and WiFi sexy. Exactly. Awesome. >> So, John, help connect for us. Enterprise. Not working. We've been talking about the new re architectures. You know, there's a c I there now intent based networking. How does this play into the five G and WiFi six discussion that we're having today? >> So one of the things that really matters to our customers and for everybody, basically, they want these sort of entering capability. They had some device is they want to talk to applications. They want access to data. We want to talk with other people or try ot things. So you need this sort of end twin capability wherever the ends are. So one of the things I've been working on a number of years now it's first all intent Basin that working, which we announced two and 1/2 years ago. And then multi domain, we try to connect across the different domains. Okay, well across campus and when, and data center all the way to the cloud and across the Service Fighter network and trad security has foundational across all of these. This was something that David Buckler and Chuck Robbins talked about at their keynote yesterday, and this is a huge area for us because we're going to make this single orchestrated capability crop customers to connect and to and no matter where the end of ices are >> alright so sewn on I have to believe that it's not the port, you know, administrator saying, Oh my God, I have all these signs of them. Is this where machine learning in A I come in to help me with all these disparate system absolutely are going very simple. Any user on any device had access to any application. Sitting in a data center in a cloud of multiple clouds over any network, you want that securely and seamlessly. You also wanna have nature. Its whole network is orchestrator automated, and you're the right visibility's recipes for idea on with the business insights on the eye. An ML. What's happening is there for the next book is going in complexity and skill. The number of alerts are growing up, so you are not able to figure it out. That's where the power of a I and machine learning comes. Think about it in the industry revolution, the Industrial Revolution made sure that you are. You don't have limitations or what humans can do right, like machines. And now we want to make sure businesses can benefit in the digital revolution, you know, in limited by what I can pass through all the logs and scrolls on ornament. Everything and that's the power of air and machine learning >> are there use cases where you would want some human augmentation. We don't necessarily want the machine taking over for you or Or Do you see this as a fully automated type of scenario? >> Yeah, so what happens is first ball visibility is really, really important. The operator of an effort wants the visibility and they want entwined across all these domains. So the first thing we do is we apply a lot of machine learning to get to take that immense amount of data is an unmentioned and to translate it into piece of information to insights into what's happening so that we could share to the user. And they can have visibility in terms of what's happened, how well it's happening. Are they anomalies? Are is this security threat so forth? And then we can find them additional feedback. Hate. This is anomaly. This could be a problem. This is the root cause of the problem, and we believe these are the solutions for what do you want to do? You wantto Do you want actuate one of these solutions and then they get to choose. >> And if you think of any other way, our goal is really take the bits and bytes of data on a network. Convert that data into information that information into insights that inside that lead to outcomes. Now you want. Also make sure that you can augment the power of a machine. Learning on those insights, you can build on exactly what's happening. For example, you want first baseline, your network, what's normal for your environment and when you have deviations and that anomalies. Then, you know, I don't know exactly what the problem is. Anyone automated the mediation of the problem. That's the power of A and women you >> When you guys as engineers, when you think about, you know, applying machine intelligence, there's a lot of, you know, innovation going on there. Do you home grow that? Do you open source it? Do you borrow? Explain the philosophy there in terms of it. From a development standpoint, >> development point of it is a combination of off all the aspects, like we will not green when they leave it all the exists. But it's always a lot of secrets are that you need to apply because everything flows through the network, right? If everything first netbooks, this quarter of information is not just a data link, their data source as well. So taking this district's also information. Normalizing it, harmonizing it, getting a pretty language. Applying the Alberta and machine learning, for example. We do that model, model learning and training in the clouds. Way to infants in the cloud, and you pushed the rules down. There's a combination, all of all, of that >> right, and you use whatever cloud tooling is available. But it sounds like it's really from an interest from a Cisco engineering standpoint. It's how you apply the machine intelligence for the benefit of your customers and those outcomes versus us. Thinking of Sisko is this new way I company right. That's not the ladder. It's the former. Is that >> fair? One of the things that's really important is that, as you know, Cisco has been making, uh, we've been designing a six for many years with really, really rich telemetry and, as you know, Data's key to doing good machine learning and stuff. So I've been designing the A six to do really time at wire speed telemetry and also to do various sorts of algorithmic work on the A six. Figure out. Hey, what is the real data you want to send up? And then we have optimized the OS Iowa sexy to be able to perform various algorithms there and also post containers where you could do more more machine learning at the switch at the router, even in the future, maybe at the A P and then with DNA Center way, have been able to gather all the data together in a single data life where we could form a machine learning on top. >> That's important, Point John mentioned, because you want Leo want layers and analytics. And that's why the cattle's 91 191 20 access point we launch has Cisco are basic that provides things like cleaning for spectrum were also the analytic from layer one level are literally a seven. I really like the line, actually from Chuck Robbins, yesterday said. The network sees everything, and Cisco wants to give you that visibility. Can you walk us through some of the new pieces? What, what what people, Either things that they might not have been aware of our new announcements this week as part of the Sisko, a network analytics, announced three things. First thing is automated based lining. What it really means. Is that what's normal for your environment, right? Because what's normal for your own environment may not be the same for my environment. Once I understand what that normal baseline is, then, as I have deviations I canto anomaly detection, I can call it an aggregate issues I can really bring down. Apply here and machine learning and narrow down the issues that are most critical for you to look at right now. Once and Aragon exact issue. I wanted the next thing, and that is what we call machine. Reasoning on machine reasoning is all about ordering the workflow off what you need to do to debug and fix the problem. You want the network to become smarter and smarter, the more you use it on. All of this is done through model learning and putting in the clouds infants in the cloud and pushing it down the rules as way have devices on line on time. So, >> do you see the day? If you think about the roadmap for for machine intelligence, do you see the day where the machine will actually do the remediation of that workflow. >> Absolutely. That's what we need to get you >> when you talk about the automated base lining is obviously a security, you know, use case there. Uh, maybe talk about that a little bit. And are there others? It really depends on your objective, right? If my objective is to drive more efficiency, lower costs, I presume. A baseline is where you start, right? So >> when I say baseline what I mean really, like, say, if I tell you that from this laptop to connect on a WiFi network, it took you three seconds and ask, Is that good or bad? You know, I don't know what the baseline for his environment. What's normal next time? If you take eight seconds on your baseline street, something is wrong. But what is wrong isn't a laptop issue isn't a version on the on your device is an application issue on network issue and our issue I don't know. That's why I'm machine learning will do exactly what the problem is. And then you use machine reasoning to fix a problem. >> Sorry. This is probably a stupid question, but how much data do you actually need. And how much time do you need to actually do a good job in that? That type of use case? >> What happens is you need the right data, Okay? And you're not sure where the right data is originally, which we do a lot of our expertise. It's this grass for 20 years is figuring out what the right data is and also with a lot of machine learning. We've done as well as a machine reason where we put together templates and so forth. We've basically gathered the right made for the right cause for the customer. And we refined that over time. So over time, like this venue here, the way this venue network, what it is, how it operates and so forth varies with time. We need to weigh need to refine that over time, keep it up to date and so forth. >> And when we talk about data, we're talking about tons of metadata here, right? I mean, do you see the day where there'll be more metadata than data? Yeah, it's a rhetorical question. All right, so So it's true you were hearing >> the definite zone. Lots of people learning about a building infrastructure is code. Tell us how the developer angle fits into what we've been discussing. >> Here we ask. So what happens is is part of intent based on African key parts of automation, right? And another key parts. The assurance. Well, it's what Devon it's trying to do right now by working with engineering with us and various partners are customers is putting together one of the key use cases that people have and what is code that can help them get that done. And what they're also doing is trying to the looking through the code. They're improving it, trying to instill best practice and stuff. So it's recently good po'd people can use and start building off. So we think this could be very valuable for our customers to help move into this more advanced automation and so forth. >> So architecture matters. We've touched upon it. But I want you to talk more about multi domain architectures wear Chuck Robbins. You know, talk about it. What is it? Why is it such a big deal on DH? How does it give Sisko competitive advantage? >> Think about it. I mean, my dad go being architectures. Nothing but all the components of a modern enterprise that look behind the scenes from giving access to a user or device to access for application and everything in between. Traditionally, each of these domains, like an access domain, the land domain can have 100 thousands off network know that device is. Each of these are configured General Manual to see a live my domain architectures almost teaching these various domains into one cohesive, data driven, automated programmable network. Your campus, your branch, your ran. But he doesn't and cloud with security as an integral part of it if it all. >> So it's really a customer view of an architecture isn't? Yeah, absolutely. Okay, that's good. I like that answer. I thought you're going to come out with a bunch of Cisco No mumbo jumbo in secret sauce. Now it really is you guys thinking about Okay, how would our customers need to architect there? >> But if you think about it, it's all about customer use case, for example, like we talked earlier today, we were walking everywhere on the bull's eye, in the cafe, in office and always on the goal. You're accessing your business school applications, whether it's webex salesforce dot com, 40 65. At the same time you're doing Facebook and what's happened. YouTube and other applications. Cisco has the van Domain will talk to Sisko. The domains action escalates and policies. So now you can cry tears the application that you want, which is business critical and fixing the night watchers but miss experience for you. But you want the best experience for that matter, where you are well >> on the security implications to I mean, you're basically busting down the security silos. Sort of the intent here, right? Right. Last thoughts on the show. San Diego last year. Orlando. We're in Barcelona earlier this year. >> I think it's been great so far. If you think about it in the last two years, we fill out the entire portfolio for the new access network when the cattle is 90. 100. Access points with WiFi six Switches Makes emission Campus core. Waterston, Controller Eyes for Unified Policy Data Center for Automation Analytics. Delia Spaces Business Insights Whole Access Network has been reinvented on It's a great time. >> Nice, strong summary, but John will give you the last word. >> What happens here is also everything about It says that we have 5,000 engineers have been doing this a couple years and we have a lot more in the pipe. So you're going to Seymour in six months from now Morn. Nine months and so forth. It's a very exciting time. >> Excellent. Guys. It is clear you like you say, completing the portfolio positioning for the next wave of of access. So congratulations on all the hard work I know a lot goes into it is Thank you very much for coming. All right, Keep it right there. David. Dante was stupid. And Lisa Martin is also in the house. We'll get back with the Cube. Sisqo live 2019 from San Diego.

>> Voiceover: Live from Las Vegas it's The Cube, covering NAB 2017, brought to you by HGST. (lively music) >> Good morning, welcome to The Cube I'm Lisa Martin, and we are live at day three of the NAB Show in Las Vegas. Very excited to introduce you to our first guest this morning, Michael Harbin, the VP of Pac-12 Networks. Good morning Michael, welcome to the cube. >> Good morning, how are you today? >> Very good, very energized. >> Oh good (laughter) >> Day three. So Michael, tell us about Pac-12 Networks, The content arm of the Pac-12 Conference. >> Sure, we have a six regional sports networks in the western US, and then one national feed, we also have digital properties and some over-the-top services on Twitter and Facebook Live, so we're involved as we can be in all forms of distribution. We're located in San Francisco, the conference itself is over 100 years old; it was 100 last year. The networks launched four years ago, this will be our fifth season coming up in August. We're very proud, very happy of our distribution, and our student athletes, and our partnership schools, and it's a great place. >> So you are the first and only sports media company that is owned by its 12 universities. >> That's right, so the SEC is partnered with ESPN, and the Big 10 Networks are partnered with Fox, so we're on our own, we stand on our own, and we do the best we can with what we have. >> Give us an idea of the genesis of the network. >> It started with the new commissioner, Larry Scott on the Pac-12 side, he came in and had a vision for helping the Pac-12 realize what it could be, as opposed to... Being on the West Coast has its disadvantages; our audience size isn't that big, our games start when the East Coast is going to sleep sometimes, so he wanted to get rid of an East Coast bias that existed in collegiate sports, and really make Pac-12 what it should be. We have the best geography, we have the best schools, we have land in... Tech and entrainment, so we have a lot going for us, and I think he brought those things to the forefront, and helped position Pac-12 in a much stronger position than it had been. In the world of liscencing content, we leapfrogged at the time the rest of the conferences in our deal with ESPN and Fox for our football and basketball games. With the games that weren't sold to Fox and ESPN, commissioner Scott thought to create a media company that we would own and control, and that would distribute the rest of our collegiate and athletic events that we have that are controlled by the Pac-12. >> So you mentioned basketball, football, you do big events, but you also do small events. Give us an idea of what it's like to produce a big event in the fall; a big football event, versus some of the smaller Olympic sports like field hockey? >> Sure. We have our three seasons; fall, winter, and spring, so obviously winter, the mostly indoor sports, but in the fall we kickoff big with our football season, and there's 12 or 13 weeks, and we have a championship game in early December which is a big event. That's one of the reasons the Pac-10 went to the Pac-12; the NCA says if you have 12 football teams, you can have a championship game. >> Okay. >> If you have less than 12, whoever has the best record is the winner, so we added two schools, and we have a champ game; those media rights were sold to Fox and ESPN, so it was a nice deal for us. So we start off with football; those are more traditional productions that everybody's used to. Big 53-foot truck pulls up, we do our production compliment with seven, eight or nine cameras depending on the game, depending on the market, depending on the week, the time of broadcast. We usually get- we choose our games after Fox and ESPN chooses theirs, so sometimes we get good games, sometimes we don't. They're all good; they're all Pac-12 games, so they're all good. But those are very traditional productions that are done in very traditional methodologies that everyone would see. As we start getting into basketball, those two are typical productions, but the volume of basketball games is such that we found a new way to do those games a little bit less expensively than the others. >> So less resources? >> Yeah. And then of course the spring sports where you're into baseball and softball, track and field. Track and field is a very expensive sport to produce because there's a lot going on at any one time. In that way, we've gotten away from video as a means of transmission and done IP transmission, which saved us a lot of money, and as we've got that IP path between our schools and ourselves, we've learned to do new things with it. We're doing content sharing back and forth, advanced production techniques, multiple camera paths that we normally wouldn't have on a production of that size. All of our shows, no matter where they are or what sport they are are produced in surround sound 5.0, so we think we lend a lot to the smaller sports that get smaller audiences, but we think we put a lot of production value to them to do the athletes and the sport justice. >> Talk to us about the underlying technologies that are necessary to support going from video to IP so that you can really open up the types of content and where it's distributed. >> Right, so one of the difficulties- we have around 100 venues in the 12 schools that we have to be able to broadcast from. Depends on the university; at Standford, those soccer and lacrosse fields could be way out. They call the campus 'the farm' for a reason. There's a lot of acreage there to cover. And some of our venues aren't even on campus. UCLA football is at the Rose Bowl, USC is at the Coliseum, so we had to find a way to get away from video which is just a single path and costs a lot. We needed more bidirectional service, we needed something that was secure and had really low latency so that when we did our productions we did the coaches interviews afterwards, it's basically like a phone call. We also provided internet services to the production, which everybody needs internet connectivity. The Chyron people, whomever. The crew itself, just for checking in and their report times and things like that, and we also provide four-digit extension dialing for our in-house phone systems. It's a very efficient and cost-effective way for us to do our production out there, and provide this suite of services that if I was just using a video circuit, I wouldn't have access to unless I paid extra for it. >> So presumably, creating a ton of content, how do you maintain all this content and be able to retrieve things, be able to livestream, have things on demand, that's that underlying archival storage strategy? >> So we produce 850 events throughout a year, and that's just to give you an idea, I think Big 10 and SCC are around 400, 450. We have a lot of volume going on, and we do a very good job, I think, of archiving that, logging those games, adding metadata, as much metadata as we possibly can to it. Including repurposing the closed caption files, we attach that as data, we get articles, stills, whatever we can gather about that particular game, we add it as metadata, and then we archive that. We keep it on very fast, short-term storage in our building on spinning disk, and after it ages, after about the second season, we push it into Amazon Cloud. It goes right into Glacier if it's that old, but immediately when we do a game, we push it up to S3 in Amazon, where we share and monetize our content at that point, and then from there it just goes to Glacier, so we have, we think, a very efficient workflow, it's highly automated, we have a great media management department that does a terrific job with very few people, very scarce resources, they do what I think is one of the best jobs in the industry in terms of saving that content in an effort to monetize it in the future. So if you can find it and search through it and get clips from it, it's going to be that much more valuable for us. >> So one of the prevailing things that we've been hearing all week, and not just here, is the democratization of content. The audience, we're very much empowered, right? As a viewer of anything we want; we're binge-watching, we're streaming, we're time-shifting, we're sharing it on social media. What is the process that Pac-12 Networks goes through to understand your audience as well as you can to deliver them the experience that you think they want? >> We have the data that comes back from our TV Everywhere product, there are OTT platforms that we can gather up and sift through. We've undertaken a fan engagement project to work with our universities about the type of people and who attend their football games, or their sporting events, and a way of better understanding who our audience is and tailoring our program to that. Understanding who they are, what their preferences are, it will help us, I think, to fine-tune the kind of content we put in front of them. Everybody loves a winning team, and you have no problem filling seats or getting an audience when your team is winning, so we understand that; we just want to be better during those times where the team might not be undefeated, so we'd like to get people in there anyway. It's a challenge for us, it really is. >> What about this concept of original content? You're now producing original content. There are three shows? >> Yes. We have some anthology shows; The Drive, and All Access during football and basketball season that give a behind-the-scenes look akin to the HBO shows on the professional side that look at professional sports. We go behind the scenes, and the stories for some of our athletes and some of our teams are quite compelling, and it makes good television. That gets also supported by our shoulder programming for our live events; pre and post-game SportsCenter-type shows that we do, and we try to do live halftimes that are topical for every one of our sports events that are played, so that's a lot of volume, a lot of churn that goes through a small studio in a small facility. We think it helps the live events look better, I mean, live events are what people are tuning in to watch. You can't fast-forward through a sporting event which advertisers just love, you kind of have to consume it in the moment, unless you can keep yourself away from the internet or your phone for a few hours until you get a chance to watch the game. We think being in live sports is a really special place to be, because you can't fast-forward through it. Any support that we give those live events, that's really what the other original content is geared to, is to build interest in those teams and those events, and attract people to them. >> So you have this concept of TV everywhere. Original content, traditional content, how is the cloud helping the Pac-12 Network to really collaborate across all the content, all of the connected fans and wherever they are? >> Sure. Just to make a distinction, we have the TV Everywhere which is the authenticated platforms that our cable providers use, and we have our own digital properties as well that still need to be authenticated, and then there's the over the top platforms like Facebook Live that are everything but the 850 events that go on the air. So behind the scenes, sideline reporters in the locker rooms, whatever else we could produce, pep rallies, that we think could be compelling content for Facebook Live we do. On Twitter, we've licensed out the 851st event and beyond, so we do some very limited productions, but still quality, that gets distributed on Twitter. So that's kind of this thing. TV Everywhere is basically the high-end product, and then these kind of ancillary second-screen experience, whatever you want to call them that don't need to be authenticated, that anybody can pick up and watch. That's how we make that distinction. I'm sorry, what was the second part of that question? >> How does cloud help collaboration? >> So we were really early adopters of producing those streams ourselves, so with Elemental Technologies who is a wonderful vendor and partner of ours, they're now owned by AWS, I point over there, they're somewhere in the building. >> (laughs) >> We're a big early adopter of their technology, we've really tried to strive for a business partnership with our vendors, rather than just a check-writer, check-casher relationship, which doesn't do us well, we don't think. We developed this relationship with them, and they helped us deliver our mezzanine streams to Occami and distribute from there, but we do that encoding in-house on their equipment. Eventually I think we'll move that to the cloud and get it all virtualized, but for right now we run their servers in our house, and they understand that we would like to get it out as quickly as we can as some point, but we're working on emptying our CER as fast we can; I don't want any blinking lights in my CER if I could get there someday, but that's a dream. >> So last question, we just have about thirty seconds left, you're in San Fancisco, >> Yep. >> With a really cool opportunity; sports entertainment technology. When you're looking for young talent who could potentially be swayed by the big Googles of the world and Facebook, what is really unique and cool about working with Pac-12 Network? >> For us, it's a two-edged sword. We love being in San Francisco; it gives us access to young people, a new way of thinking, different technology companies that are more IP/IT centric than TV centric. So we think that gives us a real advantage. The other edge of the sword is that we lose a lot of network engineering especially, systems engineers to the tech companies; they would prefer to work at Uber or LinkedIn, something like that. TV's kind of a dying tech, you have to jazz it up a little bit to gain their interest. >> But it's evolving based on what you're talking about-- It is. It's very much that skillset for being an old-time TV engineer is becoming less and less important than network engineering or systems engineering skillsets; that's what we really look for. If somebody has a Cisco certification, he gets our- or she gets our interest, rather than just 'I've worked in television for 20 years,' because we know which direction we're going in. >> One of the things that you articulate as we wrap things up here is that every company this day and age is a tech company, so we wish you the best of luck. You've said you've been at this show for 30 years >> 30 years. >> I can't even imaging all the things that you've seen. Michael Harbin, thank you so much for joining us on The Cube. >> Thank you very much, it was a pleasure being here. >> We want to thank you for watching, we are live from NAB in Las Vegas. I'm Lisa Martin, stick around, we'll be right back. (techno music)