>> live from Orlando, Florida It's the que covering accelerate nineteen. By important, >> Welcome back to the cubes. Continuing coverage of Fortinet Accelerate twenty nineteen. Live from Orlando, Florida Lisa Martin with Peter Births and we're pleased to welcome back to the Cube. One of our alumni. John Madison, the executive vice president of Products and Solutions from Fortinet. John, It's great to have you back on The Cube >> is great to be here again. >> Lots of momentum. That fourteen that is coming into twenty nineteen with I can't believe we're in April. Already, lots of growth in revenue product revenue was up. You guys talked about the expansion of the partner network with some of your fabric ready partners on already today. You talked about this third generation and security. How fortunate is uniquely delivering that for our viewers who you weren't didn't have the opportunity to attend. Your keynote kind of talked to us about that in this hybrid world. How is supporting that delivering this third generation? What makes you guys difference? >> Yeah, so we talk about the third generation now. Everyone has different generations. That's fine. We call it the security driven networking, and it's really the Genesis ofthe forty nine for a long time in bringing together networking and security into one place. I think these days or in the past, people have built out the networks, the network layer. Then they try and connect users and applications. And they go, Wait a minute, this person security over here in a bit, over here and over there in our mind, start with both. Start with a security driven networking concept. Make sure it works end to end, and that will be the most sophisticated, most secure application and network you can have. >> And what enable supporting that to deliver this unique. Because a number of times today and Ken's key nodes, I think Patrice as well. I can't recall if yours competition came up where the audience was shown the strength in numbers that fourteen that has what makes us unique and what you're delivering. One of >> the key differentiators from the start is being making sure we can run a routing stacks. Sometimes today he referred to as ehs tea. When Stax or so security stacks in a very small footprint, and to do that, you need to spend a lot of money on what we call security processes which go inside our appliances, but to make sure that runs very fast. But having said that, I definitely think customer is going to be in a hybrid world forever for a very long time, at least anyway, where not only appliances but also virtual machines and FBI security. We also talk about this fabric concept that ables to cover the incomplete digital attack surface. So there's a very important point, and we find a lot of customers now agreed that they want to consolidate. They want to make it simpler. They need to move faster to this digital world, and anyway, you have to do that is through a consolidated >> approach. So let's build on this. They want to consolidate. They want to make it simpler, more common, and how the policies and management now along comes. Yet what's the dynamic there? >> But what's happening is that all the people referred to the perimeter disappearing. Okay, that's happening to a certain extent because data's moving into cloud. You've got different one implementations, but what's happening when you do that is to creating New Edge is a really good example, a zesty wherein which used to be very closed off. The one used to be something that connects branch offices back to the data center, but nobody got involved in that. Well, now you're opening up that when two different types of transport mechanism you're creating an edge I always refer to these edges is being created by different trust levels. There is a maybe a secure trust level here, less trust here. It creates an edge, and you absolutely need to protect all those edges. >> Would give us an example that So, for example, when you say differentiated trust levels, my edge might be at a customer location. Is that kind of what versus my edge might be in a branch office? Is that what you mean by different trust level? Push that concept for >> you know, It's more, for example, if I got a branch office and I've got one connective ity going back to my data center that's encrypted and secure. But I've also opened up connected to the Internet, the trust level between that encrypted link on my connection to the to the Internet's very different Internets open. Anyone can see they're so that trust level between those two is very different. and that's what creates the edge. >> And so, therefore, that becomes a key feature in how we design different edge implementations. It >> is. It's also a key requirement on what type of deployment Mody use have appliances have virtual machines. We have clouds, containers. AP eyes going forward. I'm finding that customers are still very reluctant to put software implementations of firewalls against the Internet. Appliances are hardened. They run faster. Having said that, inside the cloud, obviously, and inside software defined data centers virtual fine. >> Where some of those customer concerns that you're hearing >> well, I think what happens is, you know, if you putting a piece of software against the Internet, it's open to all sorts of attack. It's the same as giving I P addresses to anything. It's like a factory that creates an edge as well, and you need to harm that age against that. >> And how can Estevez When How Why is this such a crucial component of digital transformation? >> You know, sometimes markets are over hyped. I remember the Casby marketplace a few years ago. It just was a feature. To be honest, I think sd one extremely important. The reason is important is the SD one controller. That controller eventually tells users and devices how to get to the applications. And so I tell customers that investment for you is extremely important. You need to own it. You need to make sure it's flexible. Need to make sure it's secure. And so I think the SD, where marketplace or one edge is the kind of larger term for it is extremely important investment for customers. Do >> you anticipate that? I mean, you guys invested. You guys put forward a lot of products, made a number of different announcements again, going back to that notion of simplicity, that notion of consolidation. What is the breaking point for your typical group in terms of the complexity of that they can accommodate and absorbed? When we start adding additional function within the overall network, especially from a security standpoint, >> well, I think it's a bit broken already. They're really struggling to keep up from our perspective. No, today we announced our forty or sixty twos are major operating system, and what we try and do is consolidate functionality as much as possible. Inside our fabric through a single console, there was single operations capability, so it's easier for the operations people. For this critique people to implement things and find information. Ross implementing order made in mechanisms like security ratings. We should do a background run off best practices, for example, that make it again easier for those those teams to run a full analysis. What's going on? >> So was it about three hundred features roughly roughly >> accountable individually? >> Okay, good. We'LL do a recount of that, but a tremendous amount of feature addition to forty OS announced today. What are some of the things business outcomes? Peter and I were talking about outcomes with several of our guests earlier. Business outcomes, New revenue streams New product's going to market faster, the also being able to become less reactive, maybe more proactive in terms of security codes. Can you walk us through some of the outcomes that fourteen customers can expect to achieve from some of the O. S announcement in the handsome? It's already >> talked about one, which was the consolidation, which means they can do multiple things with single platform us, an important one for them. Also, some of the some of the cost savings around that's on the operational cost savings. I think also for our partners. For example, they like the fact that we're keeping that we keep adding services on top of that fabric. They can take those services, then apply them to their customers and make sure they can add value inside as well. So there's two angles to it. The one is making sure our customers are better protected. They can consolidate, save money, invest better training and then to our partners so that they can provide more value to their customers. >> So one of the things we're talking about is the fact that you have invested in a six it's and security processing units and content processing units, etcetera, that are capable of accelerating the rate at which these crucial security algorithms run. That opens up That creates additional capacity to add more function both for you as well as your partners. Are you starting to see some of your ecosystem grow faster as they better exploit that inherent power and performance that you have within your appliances and devices? >> Definitely. I think we're seeing new partners come from new areas. It also fragments of it, and that's why we announced this new partner initiative going forward, which is a bit more customizable, but but I, you know, I do think that going forward, both our customers and our partners are looking for more of an architecture approach again. If you go back five years, here's a box and off you go and install it, and we're good on again When you saw the security threats. Yes, we produce a point solution to fix the normal way. Keep moving on. They're now looking at architectures over the next five years, known only just cybersecurity architectures but Network Inc architectures, storage architectures and all coming together. So we definitely need to train our partners. I think here we had over fifty of are what we call Network's network security expert. Eight. It's the highest level of architecture and half of the partners, But going forward, we see much more partner involvement in architecture approach on. Our customers want that because they don't want to have a point solution that's out of date in a year's time or a new threat comes along and makes it redundant. >> So how are you? You mentioned you mentioned network security and storage. What other things are starting to inform that architectural approach that you're taking. >> It's everything now. So we know the factories now a completely automated all that. If utilities of I P addresses are running almost all the way down to the end point, just everything has more flexibility and more open eso. Definitely All that information's bouncing around inside I ot devices inside the wire inside data centers on all that data needs protecting. That's the key of protecting the data. And to do that again, we keep saying you need tohave. An integrated approach to networking and security >> Has the customer work with forty Net and your partner ecosystem to achieve that integrated approach. Assuming that there is a, you know, an enterprise out there that's got a spectrum of hybrid multiplied environment with the spectrum of Security point Solutions pointed it in a different components of an infrastructure. How do you help them on that journey of taking the many disparate security solutions and leveraging the power of fourteen and your partners to get that integrated, truly integrated, consolidate consolidated view? It's a couple >> of steps, maybe, maybe many steps. The first one is, oh, customers don't want to throw everything else straightaway. So what they want to do is build to integrating Connect. So we have some of our partners. Here, for example, are fabric ready partners way have connectors. We build into their platforms and orchestration systems, and that's their first step. Once they get there, they start looking across to see what they can to consolidate. So can they take a specific solution from this and I'm bringing inside? And then eventually they start to look at the long term architecture if they're moving APS to the cloud or they want to open up their wear or the one who provide kind of SD functionality inside their branch, So it's definitely a phase approached. I don't see many customers. Some customers would take an application and created from scratch inside the cloud. They can't do that with their infrastructure, the kind just completely wipe it clean. Start again. It's definitely more of a phase approach. >> So if you think about the face approach on you, talk way heard from, uh, we heard from the sales of sport side the notion that the S P s the service providers want greater customization. The enterprise wants a different level of access to the core technologies, so that they could do not customization. Not exactly remember Jack with the term was what What degree will customers retain control over how that architecture gets implemented versus what degree is going to get baked into the stack itself? A >> bit of >> both, I think, you know, for most customers, they're running towards a digital platform on. They need to own the digital powerful. If they give up complete control, how do they control that destiny going forward? So they want to own the digital platform, but they haven't got the resources to do everything. So that allows saw some to service providers and carriers. Some of the partners, for example. But I'm going to keep coming back to this. They want to get to a point in five years time, but they've got a digital footprint, is very flexible, but they also want to make sure it's very secure because as you open up that digital footprint, you opening up all these different edges. Inside the network, >> it's coherent, which is the are contested approach. Yes, because if they don't have a coherent approach to doing it, they don't know what interfaces are or are not competent, and that includes interfaces with partners. >> Yeah, they have to look forward and say I'm gonna implement X amount in the cloud. Arnot gonna have some edge compute going on here. I want to shake. Make sure my branches have the best quality of service for these certain applications that go back to this. So they would look at all those parameters and an architect, something from there. >> So we know that security network, security app, security info, security cloud security is our imperatives for every industry. But I didn't notice that the breakouts today feature. I think there's a couple of vertical features healthcare, financial services, retail. I was just curious. Are theirs just great use cases that show the potential power of forty nets technologies? Or are those industries that are either early adopters or maybe more leading edge? Because they have such a tremendous amount of data that needs to be secured as their ecosystem does this? >> Yeah. So the industry verticals, I think I think for the very large ones, they're very similar. All of them have I ot this expanding order and wanna have a flexible land system. Almost got something. Some computer power in the cloud and the edge going forward. So I know there's differences and industries. For the very large enterprises, it's the problem. Seems the same. This huge organizations, and they have all of these things going on in the right corner at you. Calm down, Toa mid enterprise. I think there's more reason to consolidate. But you seymour differences in the way the approach, things like health care that really, really focused on that healthcare kind of security of devices inside hospitals, et cetera. Education. Oh, they need to connect in these big data banks. Transfer the research information. So big organizations, I say pretty much the same problem. Midsize organizations become more relevant to the specific industry. >> Well, John, thank you so much for carving out some time to speak with Peter and need Today. We appreciate that. And it's exciting to see and feel the mo mentum the forty Niners bringing into twenty nineteen. >> Well, thanks for inviting me. >> Our pleasure. We want to thank you for your time is well for Peter. Boris. I'm Lisa Martin. You're watching the Cube