>>welcome to the session. Long live swarm with containers and kubernetes everywhere we have this increasing cloud complexity at the same time that we're facing economic uncertainty and, of course, to navigate this. For most companies, it's a matter of focusing on speed and on shipping and iterating their code faster. Now. For many, Marantz is customers. That means using docker swarm rather than kubernetes to handle container orchestration. We really believe that the best way to increase your speed to production is choice, simplicity and security. So we wanted to bring you a couple of experts to talk about the state of swarm and Docker enterprise and how you can make best use of both of you. So let's get to it. Well, good afternoon or good morning, depending on where you are on and welcome to today's session. Long live swarm. I am Nick Chase. I'm head of content here at Mantis and I would like to introduce you to our two Panelists today eight of Manzini. Why don't you introduce yourself? >>I am a van CNI. I'm a solutions architect here at Moran Tous on work primarily with Docker Enterprise System. I have a long history of working with support team. Um, at what used to be Ah Docker Enterprise, part of Docker Inc. >>Yeah, Okay. Great. And Don Power. >>I, um Yeah, I'm Don Power on the docker. Captain Docker, community leader. Right now I run our Dev Ops team for Citizens Bank out of Nashville, Tennessee, and happy to be here. >>All right, Excellent. So All right, so thank you both for coming. Now, before we say anything else, I want to go ahead and kind of name the elephant in the room. There's been a lot of talk about the >>future. Yeah, that's right. Um, swarm as it stands right now, um, we have, ah, very vested interest in keeping our customers on who want to continue using swarm, functional and keeping swarm a viable alternative or complement to kubernetes. However you see the orchestration war playing out as it were. >>Okay? It's hardly a war at this point, but they do work together, and so that's >>absolutely Yeah, I I definitely consider them more of like, complimentary services, um, using the right tool for the job. Sort of sense. They both have different design goals when they were originally created and set out so I definitely don't see it as a completely one or the other kind of decision and that they could both be used in the same environment and similar clusters to run whatever workload that you have. >>Excellent. And we'll get into the details of all that as we go along. So that's terrific. So I have not really been involved in in the sort of swarm area. So set the stage for us where we kind of start out with all of this. Don I know that you were involved and so guys said, set the stage for us. >>Sure, Um I mean so I've been a heavy user of swarm in my past few roles. Professionally, we've been running containers in production with Swarm for coming up on about four years. Now, Um, in our case, we you know, we looked at what was available at the time, and of course you had. Kubernetes is your biggest contender out there, but like I just mentioned, the one of the things that really led us to swarm is it's design goals were very different than kubernetes. So Kubernetes tries to have an answer for absolutely every scenario where swarm tries to have an answer for, like, the 80% of problems or challenges will say that you might come across 80% of the workloads. Um, I had a better way of saying that, but I think I got my point across >>E Yeah, I think I think you hit the nail on the head. Um, Kubernetes in particular with the way that kubernetes itself is an a P I I believe that kubernetes was, um, you know, written as a toolkit. It wasn't really intended to be used by end users directly. It was really a way to build platforms that run containers. And because it's this really, really extensible ap I you can extend it to manage all sorts of resource is swarm doesn't have that X sensibility aspect, but what it was designed to do, it does very, very well and very easily in a very, very simple sort of way. Um, it's highly opinionated about the way that you should use the product, but it works very effectively. It's very easy to use. It's very low. Um, not low effort, but low. Ah, low barrier to entry. >>Yes. Yes. Absolutely. I was gonna touch on the same thing. It's very easy for someone to come in. Pick up swarm. You know they don't They don't have to know anything about the orchestrator on day one. Most people that are getting into this space are very familiar with Docker. Compose um, and entering from Docker compose into swarm is changing one command that you would run on the command line. >>Yeah, very, very trivial to if you are already used to building docker files using composed, organize your deployment into stacks of related components. It's trivial to turn on swarm mode and then deploy your container set to a cluster. >>Well, excellent. So answer this question for me. Is the swarm of today the same as the swarm of, you know, the original swarm. So, like when swim first started is that the same is what we have now >>it's kind of ah, complicated story with the storm project because it's changed names and forms a few times. Originally in is really somewhere around 2014 in the first version, and it was a component that you really had to configure and set up separately from Docker Ah, the way that it was structured. Ah, you would just have docker installed on a number of servers are machines in your cluster. And then you would organize them into a swarm by bringing your own database and some of the tooling to get those nodes talking to each other and to organize your containers across all of your docker engines. Ah, few years later, the swarm project was retooled and baked into the docker engine. And, um, this is where we sort of get the name change from. So originally it was a feature that we called swarm. Ah. Then the Swarm Kit project was released on Get Hub and baked directly into the engine, where they renamed it as swarm mode. Because now it is a motile option that you just turn on as a button in the docker engine and because it's already there the, um, the tuning knobs that you haven't swarm kit with regard to how what my time outs are and some of these other sort of performance settings there locked there, they're there. It's part of the opinionated set of components that builds up the docker engine is that we bring in the Swarm Kit project with a certain set of defaults and settings. And that is how it operates in today's version of Docker engine. >>Uh, okay for that, that makes sense. That makes sense. So ah, so don, I know you have pretty strong feelings about this topic, but it is swarm still viable in a world that's sort of increasingly dominated by Kubernetes. >>Absolutely. And you were right. I'm very passionate about this topic where I work. We're we're doing almost all of our production work lives on swarm we only have out of Ah, we've got something like 600 different services between three and 4000 containers. At any given point in time. Out of all of those projects, all of those services we've only run into two or three that don't kind of fit into the opinionated model of swarm. So we are running those on KUBERNETES in the same cluster using Moranis is Docker enterprise offering. But, um, no, that's a very, very small percentage of services that we didn't have an answer for in swarm with one. The one case that really gets us just about every time is scaling state full services. But you're gonna have very few staple services in most environments for things like micro service architecture, which is predominantly what we build out. Swarm is perfect. It's simple. It's easy to use you, don't you? Don't end up going for miles of yamma files trying to figure out the one setting that you didn't get exactly right? Um yeah, the other Thea the other big piece of it that way really led us to adopting it so heavily in the beginning is, you know, the overlay network. So your networks don't have to span the whole cluster like they do with kubernetes. So we could we could set up a network isolation between service A and service B, just by use using the built in overlay networks. That was a huge component that, like I said, let us Teoh adopting it so heavily when we first got started. >>Excellent. You look like you're about to say something in a >>Yeah, I think that speaks to the design goals for each piece of software. On the way that I've heard this described before is with regard to the networking piece the ah, the docker networking under the hood, um, feels like it was written by a network engineer. The way that the docker engine overlay networks communicate uses ah, VX lan under the hood, which creates pseudo V lands for your containers. And if two containers aren't on the same Dylan, there's no way they can communicate with each other as opposed to the design of kubernetes networking, which is really left to the C and I implementation but still has the design philosophy of one big, flat sub net where every I p could reach every other i p and you control what is allowed to access, what by policy. So it's more of an application focused Ah design. Whereas in Docker swarm on the overlay networking side, it's really of a network engineering sort of focus. Right? >>Okay, got it. Well, so now how does all this fit in with Docker enterprise now? So I understand there's been some changes on how swarm is handled within Docker Enterprise. Coming with this new release, >>Docker s O swarm Inside Docker Enterprise is represented as both the swarm classic legacy system that we shift way back in 2014 on and then also the swarm mode that is curly used in the docker engine. Um, the Swarm Classic back end gives us legacy support for being able to run unmanaged plane containers onto a cluster. If you were to take Docker ce right now, you would find that you wouldn't be able to just do a very basic docker run against a whole cluster of machines. You can create services using the swarms services, a p I but, um, that that legacy plane container support is something that you have to set up external swarm in order to provide. So right now, the architecture of Docker Enterprise UCP is based on some of that legacy code from about five or six years ago. Okay. Ah, that gives us ability to deploy plane containers for use cases that require it as well as swarm services for those kinds of workloads that might be better served by the built in load balancing and h A and scaling features that swarm provides. >>Okay, so now I know that at one point kubernetes was deployed within Docker Enterprise as you create a swarm cluster and then deploy kubernetes on top of swarm. >>Correct? That is how the current architecture works. >>Okay. All right. And then, um what is what is where we're going with this like, Are we supposed to? Are we going to running Swarm on top of kubernetes? What's >>the the design goals for the future of swarm within branches? Stocker Enterprise are that we will start the employing Ah, like kubernetes cluster features as the base and a swarm kit on top of kubernetes. So it is like you mentioned just a reversal of the roles. I think we're finding that, um, the ability to extend kubernetes a p I to manage resource is is valuable at an infrastructure and platform level in a way that we can't do with swarm. We still want to be able to run swarm workloads. So we're going to keep the swarm kit code the swarm kit orchestration features to run swarm services as a part of the platform to keep the >>got it. Okay, so, uh, if I'm a developer and I want to run swarm, but my company's running kubernetes what? What are my one of my options there? Well, I think >>eight touched on it pretty well already where you know, it depends on your design goals, and you know, one of the other things that's come up a few times is Thea. The level of entry for for swarm is much, much simpler than kubernetes. So I mean, it's it's kind of hard to introduce anything new. So I mean, a company, a company that's got most of their stuff in kubernetes and production is gonna have a hard time maybe looking at a swarm. I mean, this is gonna be, you know, higher, higher up, not the boots on the ground. But, um, you know, the the upper management, that's at some point, you have to pay for all their support, all of it. What we did in our approach. Because there was one team already using kubernetes. We went ahead and stood up a small cluster ah, small swarm cluster and taught the developers how to use it and how to deploy code to it. And they loved it. They thought it was super simple. A time went on, the other teams took notice and saw how fast these guys were getting getting code deployed, getting services up, getting things usable, and they would look over at what the innovation team was doing and say, Hey, I I want to do that to, uh, you know, so there's there's a bunch of different approaches. That's the approach we took and it worked out very well. It looks like you wanted to say something too. >>Yeah, I think that if you if you're if you're having to make this kind of decision, there isn't There isn't a wrong choice. Ah, it's never a swarm of its role and your organization, right? Right. If you're if you're an individual and you're using docker on your workstation on your laptop but your organization wants to standardize on kubernetes there, there are still some two rules that Mike over Ah, pose. And he's manifest if you need to deploy. Coop resource is, um if you are running Docker Enterprise Swarm kit code will still be there. And you can run swarm services as regular swarm workloads on that component. So I I don't want to I don't want people to think that they're going to be like, locked into one or the other orchestration system. Ah, there the way we want to enable developer choice so that however the developer wants to do their work, they can get it done. Um Docker desktop. Ah, ships with that kubernetes distribution bundled in it. So if you're using a Mac or Windows and that's your development, uh, system, you can run docker debt, turn on your mode and run the kubernetes bits. So you have the choices. You have the tools to deploy to either system. >>And that's one of the things that we were super excited about when they introduced Q. Burnett ease into the Docker Enterprise offering. So we were able to run both, so we didn't have to have that. I don't want to call it a battle or argument, but we didn't have to make anybody choose one or the other. We, you know, we gave them both options just by having Docker enterprise so >>excellent. So speaking of having both options, let's just say for developers who need to make a decision while should I go swarm, or should I go kubernetes when it sort of some of the things that they should think about? >>So I think that certain certain elements of, um, certain elements of containers are going to be agnostic right now. So the the the designing a docker file and building a container image, you're going to need to know that skill for either system that you choose to operate on. Ah, the swarm value. Some of the storm advantage comes in that you don't have to know anything beyond that. So you don't have to learn a whole new A p I a whole new domain specific language using Gamel to define your deployment. Um, chances are that if you've been using docker for any length of time, you probably have a whole stack of composed files that are related to things that you've worked on. And, um, again, the barrier to entry to getting those running on swarm is very low. You just turn it on docker stack, deploy, and you're good to go. So I think that if you're trying to make that choice, if you I have a use case that doesn't require you to manage new resource is if you don't need the Extensible researchers part, Ah, swarm is a great great, great viable option. >>Absolutely. Yeah, the the recommendation I've always made to people that are just getting started is start with swarm and then move into kubernetes and going through the the two of them, you're gonna figure out what fits your design principles. What fits your goals. Which one? You know which ones gonna work best for you. And there's no harm in choosing one or the other using both each one of you know, very tailor fit for very various types of use cases. And like I said, kubernetes is great at some things, but for a lot of other stuff, I still want to use swarm and vice versa. So >>on my home lab, for all my personal like services that I run in my, uh, my home network, I used storm, um, for things that I might deploy onto, you know, a bit this environment, a lot of the ones that I'm using right now are mainly tailored for kubernetes eso. I think especially some of the tools that are out there in the open source community as well as in docker Enterprise helped to bridge that gap like there's a translator that can take your compose file, turn it into kubernetes. Yeah, Mel's, um, if if you're trying to decide, like on the business side, should we standardize on former kubernetes? I think like your what? What functionality are you looking at? Out of getting out of your system? If you need things like tight integration into a ah infrastructure vendor such as AWS Azure or VM ware that might have, like plug ins for kubernetes. You're now you're getting into that area where you're managing Resource is of the infrastructure with your orchestration. AP I with kube so things like persistent volumes can talk to your storage device and carve off chunks of storage and assign those two pods if you don't have that need or that use case. Um, you know, KUBERNETES is bringing in a lot of these features that you maybe you're just not taking advantage of. Um, similarly, if you want to take advantage of things like auto scaling to scale horizontally, let's say you have a message queue system and then a number of workers, and you want to start scaling up on your workers. When your CPU hits a certain a metric. That is something that Kubernetes has built right into it. And so, if you want that, I would probably suggest that you look at kubernetes if you don't need that, or if you want to write some of that tooling yourself. Swarm doesn't have an object built into it that will do automatic horizontal scaling based on some kind of metric. So I always consider this decision as a what features are the most I available to you and your business that you need to Yep. >>All right. Excellent. Well, and, ah, fortunately, of course, they're both available on Docker Enterprise. So aren't we lucky? All right, so I am going to wrap this up. I want to thank Don Bauer Docker captain, for coming here and spending some time with us and eight of Manzini. I would like to thank you. I know that the the, uh, circumstances are less than ideal here for your recording today, but we appreciate you joining us. Um and ah, both of you. Thank you very much. And I want to invite all of you. First of all, thank you for joining us. We know your time is valuable and I want to invite you all Teoh to take a look at Docker Enterprise. Ah, follow the link that's on your screen and we'll see you in the next session. Thank you all so much. Thank you. >>Thank you, Nick.

>> Narrator: From the CUBE studios in Palo Alto in Boston, connecting with thought leaders all around the world, this is The CUBE Conversation. >> Everyone, welcome to the special CUBE Conversation here. In the CUBES Palo Alto studios, I'm John Furrier, your host with a great story here to tell and a great story with Bob Russell, the CEO of the CTA group, also known as the Community Technology Alliance. Great story, very relevant in this time and has to involve data and technologies for good. So, Bob, thanks for spending the time to join me today. Thanks for remote dialing in or internetting in thank you. >> My pleasure, great to be with you. >> You guys have a really great mission with the Community Technology Alliance. Also known as the CTA group, which is you guys go by, take a minute to explain the firm and what you guys do coz I think this is a high impact story for this community just in general, but now more than ever, it's great story. Can you take a minute to explain? >> Thank you. We're a San Jose based nonprofit and we were founded in 1991 to provide the technology needed to support the work to end homelessness in a number of California communities and counties, primarily by providing data collection and reporting tools for agencies that were receiving federal funding to house the homeless. Several years ago, as we were looking at the data, we realized that we needed to expand our focus to not only include the homeless, but to include what's called homeless prevention. And homeless prevention is providing services to those who are not homeless, but who are at risk of becoming homeless, or those that are living in poverty and do not have enough money to pay the mortgage or pay their rent and so they too are at risk of becoming homeless. Because what the data is showing is that once you become homeless, it can be difficult, it can be time consuming, and it can take a long time for you to secure new housing. So if you can help people who are on the cusp of becoming homeless, that is, that's a wonderful thing. Keeping people from becoming homeless in the first place is one of the most effective tools in fighting homelessness in the Bay Area and throughout the United States. That expanded focus meant we really, we needed to rethink how best to leverage technology in order to help agencies communities, both in homelessness and homeless prevention. And so we focused on three different components or three tools. The first one was creating data integration tool, so that agencies that are using multiple systems, can integrate their data into a single source of truth, they can quickly communicate and exchange data with one another in order to identify how best to help people in need in their communities. The second thing that we did was we created a mobile app so that you could collect data out of your closed or your proprietary system, upload that data later to your system, or to this, to a central data warehouse. And then also, you could use this data that once we pulled your data in from multiple data systems and created a single source of truth, you could actually view that unified data. And the third tool we developed was a reporting and analytics tool, so that you could quickly visualize your data, look at overall trends and determine what measures are most effective in helping people to remain housed or to help people who are homeless to secure housing as quickly as possible. So that's our story in a nutshell, John. >> Yeah, one of the famous CUBE alumni Jeff Hammerbacher, founder of Cloudera, one said in the CUBE. This is 10 years ago, and he came from Facebook and then he said, our bright minds in the industry are working on data science so that people click on and add. And that really kind of became a rallying point in the computer science industry, because this is really a data driven strategy, you guys are taking this proactive, it's not reactive, which is still got it's own challenges. So, you know, using data for good, there's some reality there. It's like collective intelligence or predictive analytics or a recommendation engine for services to be delivered. So Love it. Love this story, I think is super important. It's not going to go away it's only going to get stronger and better. But I got to ask you with that, what are some of the challenges with the current environment for social services? Because, you mentioned legacy, legacy systems. Well, this legacy a process too. I can only imagine the challenges, what are some of those challenges in the current environment? >> Yes, yeah, there are many challenges, but I'd like to focus in on two. The first is agencies aren't network, their systems are not network. And so agency A cannot exchange and communicate with agency B. And so what happens in most communities is that if someone's in need, whether it's an individual or a family, odds are they're going to multiple agencies to secure all the different services that they need. And because agencies are not networked, it can be very difficult to secure services. If you're a need, you can end up spending a lot of time going from agency to agency, asking what's available, and seeing that if you're eligible for services. So one of the challenges that we were asked to overcome by, you know, talking to various agencies and communities is can you allow us to continue to use our current systems, but can you figure out a way for our systems to communicate and exchange critical data with one another, and the second reason or challenge is tied to first, most agencies have multiple funding sources in order to provide the services that they provide. And many of those funding sources will say to an agency in exchange for us giving you funding, you must use this system to collect data and to report out. And so what happens is a single agency can have multiple data systems that either, that just simply cannot communicate with one another. And so this creates inefficiencies. And this means that resources that would be going to a client, a family and an individual has to be redirected to doing multiple data entry and administering multiple systems. And so before we built any of our tools, we spent a good chunk of time talking to these various stakeholders in the homeless and poverty arena going, what are your primary pain points? These were the two that stood out for us. In how we could use technology to help these agencies get a more unified view of what's going on in their community and what works. >> How has any of the systematic changes affected you coz the networking piece is huge. When we see this play out in data driven businesses, obvious ones are cybersecurity, the more data the better, coz you got a machine learning is a lot of things there. The other problem I want to get your thoughts on is just the idea of not just not being networked, but the data silos. So the data silos are out there, and sometimes they're not talking to each other, even if they are connected. >> So if you're homeless or at risk of becoming homeless, odds are you're going to need multiple services to help you. It's very rare that an agency has all the services that you need so that you end up being helped by multiple services. Each one of those service, each one of those agencies, ends up being a data silo. And so you do not get a complete picture of in your community of how what are the various services that you are providing this client, and which services are most rapidly helping that client move either into housing or into self sufficiency. So agencies are very much aware that they have data silos out there, but they simply do not have the expertise or the time or the resources to manually take all of that data and try to come up with a single spreadsheet that tells 'em everything. >> On the role of data, I've seen you mentioned the users, you mentioned an app, can you just share some anecdotal examples of kind of where it's working and challenges and opportunities you guys are doubling down on because, I mean, this is a really important point, because if you look at our society at large today, the ability to deliver services, whether it's education, homelessness, poverty, it's all kind of interconnected, all has the same almost systematic kind of functional role, right you got to, identify services, needs, match them to funding and or people and move in real time or as contextually relevant as possible. If you do that, right, you're on the front end, not the back end of reacting to it. Can you give some examples? >> Yeah, I'm thinking of a young woman. I mean, this is, for me, this has been a powerful story for our organization in helping us to understand the human impact that data silos can have. So this is, in one of our communities there was a young woman with, who was recently divorced with a young son who became sick. And so she went to the hospital to secure treatment for her child, the hospital, the clinic was able to help her. But when she asked about are there agencies out there are there services out there that can help me with financial assistance can help me with getting food and finding a stable housing? They told her no, we can't help you we're clinic, but we can point you to a shelter. Well, by the time she got to that shelter, they were full for the night. So she had no place for her and her son to stay. And so what happens is she ended up spending the night out on the street. And then she spent the next week looking for, you know food bank, so she'd get food. Going to various agencies to find out, you know do you have any available housing, do you have any financial assistance and she was coming up against, you know obstacle, one obstacle over another. So if you're homeless and you don't have a car, and you know, think about anyone in the Bay Area, how difficult it is to get around if you don't have a vehicle or someone who can provide you with it, with a transportation. Her life changed and I yeah, her life changed when she ended up at a homeless encampment. And a what's called an outreach worker, went to that outreach, that encampment with our tools, with our mobile app. And this outreach worker met up with this young woman and said, how can I help you? And she, this woman explained, look, I need a place to stay for the night. I need food for my child, can you helped me? But what she did was she took her tablet open, opened up our mobile app and found yes, there is a nearby shelter that has space available. Let me get you into that shelter as soon as possible. She also alerted the case managers at that shelter that this is what the woman needs. Can you provide that assistance to her as soon as we get her to the shelter? And so what happened was instead of wandering around the community, trying to find help, because of this timely encounter between this young woman and his outreach worker, this outreach worker was able to get this woman and her child into a temporary shelter an emergency shelter for the night. And then over time, helped her secure her own apartment with financial assistance, and also the other services that she needed. And for me, that is the essence of what we're trying to do here is simply remove the barriers for you to.. The essence, what happened here was this woman was able to quickly determine through the help of an agency, what's currently available, and then connect her to those appropriate agencies to get the services that she needed. And so I have told this story many times it still gets me that it's, this is the beauty of technology. This is how you can leverage technology and help someone in need. For me it's just amazing what you can do with the right. Yes, with the right technology. >> It's such a powerful story coz it also not only illustrates the personal needs that they were met. But it also illustrates the scale of how data and the contextually relevant need at that time having the right thing happen at the right time, when it needs to happen, can scale. So it's not, it's not a one off. This is how technology can work. So I think this is a great indicator of things to come. And I think this is going to be playing out more and that is the role of data and people. This has been a fundamental dynamics, not just about machines anymore. It's the human and the data interaction. This is becoming a huge thing. Can you share your thoughts on the role of people because audiences want to get involved you seeing a much more mission driven, culture evolving quickly. People want to have an impact. >> Right. Oh, yeah, data plays a fundamental role. Best way, what helps me to understand just how fundamental that role is that what data does is it creates a narrative on the past and current experiences of people in need. In other words, data tells a story. And whether that person is homeless or at risk of becoming homeless or living in poverty, that narrative becomes a powerful tool for agencies. And it, when you take that narrative because you've been able to harness technology, create that narrative. What you can do with that narrative, is you can coordinate available services to those in need. And as, you know the story of this young woman, you can also rightly reduce the wait times and the time that someone says I have this need until you connect them with that available service. That narrative also helps you to improve your programs and services. You can look at what's working, what's not working, and make the necessary changes so that you can end up helping more people. It improves access to programs and services, instead of someone going by bus, or however I'm trying to go from one end of town to the other. Imagine if you could go to a public library, for example. And as a person in need, you could log in and go, you could tell your story, interesting data and say, help me to find the services that I need. >> Yeah. >> The other thing is that it reduces inefficiencies. Many agencies are spending considerable amount of time in duplicate data entry in order to make sure that they're collecting the data and all the different systems that they need. And then I think another key thing that data plays a fundamental role is that you can take your data as an agency, as a community and you can tell your story to policy leaders and to funders and say look, if there is how you can support us in order to provide effective homeless and poverty alleviation solutions, so again the idea that-- >> Yeah that's a key point right there, that's I mean, the key point is, you look at people process technology, which is like the, overused cliche of digital transformation very relevant by the way, the process piece is kind of taking that same track as you saw the internet technologies, change marketing and advertising, performance based, show me the clicks. If you think about what you just said, that's really what's going on here is you can actually have performance based programs with specific deliverables, if I can do this, would you do more? And the answer is you can measure it with data. This is really the magic of this. It's a new way of doing things. And again, this is not going to go away. And I think stakeholders can hold people's feet to the fire for performance based results, because the data is there if you strive to do a good mission. If the systems are in place, you can measure it. >> Thanks for that question John. Three (background noise drowns out other sounds) come to mind. First, many organizations now financially match the donations made by their employees that they make to nonprofit. So I would say that check with your HR department and see if they have a matching program. And if they do, what happens then is that for every dollar that you give to that agency, your organization, the company that you work for, will match that, and so your money will go further. These same pro... These same Corporate Social Responsibility programs, not only will match your donations, but the other thing that they will do is they will sometime arrange, sometimes workout opportunities to volunteer at very various nonprofits. And so you can also check with your organization to see if they do that. A second possibility is that you connect with groups such as the Full Circle Fund. There are other groups out there, but I'm most familiar with the Full Circle Fund. And it is a San Francisco based nonprofit that leverages your time and your resources and intellectual capital to help out with nonprofits throughout the Bay Area. So whether it is that you're looking to volunteer coding or development skills, or you're looking for some way to find out what's going on in the Bay Community, and how can I help. Full Circle Fund would be a great resource. And again, there are other nonprofits like them out there as well. The third thing is, if you know of an agency in your area, a goodwill, united way, a habitat for humanity, give them a call or check on their website to see what volunteer, positions they have available or what they're looking for. And if it looks like a good match, give them a call and have that conversation. Those are three things that immediately came to mind for me John about if he wanted to help out, how could you? >> Well, certainly it's important mission. I really appreciate, Bob, what you're doing and your team, Bob Russell, the CEO of CTA group, also known as the Community Technology Alliance. Really putting technology into practice, to help the services get to the folks that matter, the homelessness and the folks in poverty, on the edge of poverty. It really is an example of how you can solve some of these systematic problems with performance base. If you follow the data, follow the money, follow the services, it all can work in real time. And that's a good example. So thank you so much for what you do. And great mission. Thank you for your time. >> Thank you, and thank you for having me. >> Okay I'm the CUBE. I'm John Furrier, covering all the stories here while we're still programming here in the CUBE studios with our quarantine crew. Bob Russell, the CEO of CTA group, out with a great story. Check it out and get involved. I'm John Furrier, The CUBE. Thanks for watching (bright upbeat music)

>>Live from Las Vegas. It's theCUBE. Covering Fortinet Accelerate 18. Brought to you by Fortinet. >> Welcome to Fortinet Accelerate 2018. I'm Lisa Martin with theCUBE and we're excited to be here doing our second year of coverage of this longstanding event. My cohost for the day is Peter Burris; excited to be co-hosting with Peter again, and we're very excited to be joined by the CEO, Founder, and Chief Chairman of Fortinet, Ken Xie, Ken welcome back to theCUBE. >> Thank you, Lisa, thank you, Peter. Happy to be here. >> It's great to be here for us as well, and the title of your Keynote was Leading the Change in Security Transformation, but something as a marketer I geeked out on before that, was the tagline of the event, Strength in Numbers. You shared some fantastic numbers that I'm sure you're quite proud of. In 2017, $1.8 in billing, huge growth in customer acquisitions 17.8 thousand new customers acquired in 2017 alone, and you also shared that Forinet protects around 90% of the Global S&P 100. Great brands and logos you shared Apple, Coca Cola, Oracle. Tell us a little bit more and kind of as an extension of your Keynote, this strength in numbers that you must be very proud of. >> Yeah, I'm an engineer background, always liked the number, and not only we become much bigger company, we actually has 25 to 30% global employment in a network security space. That give a huge customer base and last year sales grow 19% and we keeping leading the space with a new product we just announced today. The FortiGate 6000 and also the FortiOS 6.0. So all this changing the landscape and like I said last year we believe the space is in a transition now, they've got a new generation infrastructure security, so we want to lead again. We started the company 18 years ago to get into we called a UTM network firewall space. We feel infrastructure security is very important now. And that we want to lead in the transition and lead in the change. >> So growth was a big theme or is a big theme. Some of the things that we're also interesting is another theme of really this evolution, this landscape I think you and Peter will probably get into more the technology, but give our viewers a little bit of an extension of what you shared in your keynote about the evolution. These three generations of internet and network security. >> Yeah, when I first start my network security career the first company I was study at Stanford University, I was in the 20s. It was very exciting is that a space keeping changing and grow very fast, that makes me keeping have to learning everyday and that I like. And then we start a company call Net Screen when it was early 30s, that's my second company. We call the first generation network security which secured a connection into the trust company environment and the Net Screens a leader, later being sold for $4 billion. Then starting in 2000, we see the space changing. Basically you only secure the connection, no longer enough. Just like a today you only validate yourself go to travel with a ticket no longer enough, they need to see what you carry, what's the what's the luggage has, right. So that's where we call them in application and content security they call the UTM firewall, that's how Fortinet started. That's the second generation starting replacing the first generation. But compared to 18 years ago, since change it again and nowadays the data no longer stay inside company, they go to the mobile device, they go to the cloud, they call auditive application go to the IoT is everywhere. So that's where the security also need to be changed and follow the important data secure the whole infrastructure. That's why keeping talking from last year this year is really the infrastructure security that secure fabric the starting get very important and we want to lead in this space again like we did 18 years ago starting Fortinet. >> Ken, I'd like to tie that, what you just talked about, back to this notion of strength in numbers. Clearly the bad guys that would do a company harm are many and varied and sometimes they actually work together. There's danger in numbers Fortinet is trying to pull together utilizing advanced technologies, new ways of using data and AI and pattern recognition and a lot of other things to counter effect that. What does that say about the nature of the relationships that Fortinet is going to have to have with its customers going forward? How is that evolving, the idea of a deeper sharing? What do you think? >> Actually, the good guy also started working together now. We formed the they call it the Cyber Threat Alliance, the CTA, and Fortinet is one of the founding company with the five other company including Palo Alto Network, Check Point and McAfee and also feel a Cisco, there's a few other company all working together now. We also have, we call, the Fabric-Ready Program which has 42 big partners including like IBM, Microsoft, Amazon, Google, all this bigger company because to defend the latest newest Fabric threat you have to be working together and that also protect the whole infrastructure. You also need a few company working together and it's a because on average every big enterprise they deploy 20 to 30 different products from different company. Management cost is number one, the highest cost in the big enterprise security space because you have to learn so many different products from so many different vendor, most of them competitor and now even working together, now communicate together. So that's where we want to change the landscape. We want to provide how infrastructure security can work better and not only partner together but also share the data, share the information, share the intelligence. >> So fundamentally there is the relationship is changing very dramatically as a way of countering the bad actors by having the good actors work more closely together and that drives a degree of collaboration coordination and a new sense of trust. But you also mentioned that the average enterprise is 20 to 30 fraud based security products. Every time you introduce a new product, you introduce some benefits you introduce some costs, potentially some new threat surfaces. How should enterprises think about what is too many, what is not enough when they start thinking about the partnerships that needed put together to sustain that secure profile? >> In order to have the best protection today you need to secure the whole infrastructure, the whole cyberspace. Network security still the biggest and also grow very fast and then there's the endpoint and there's a like a cloud security, there's a whole different application, email, web and all the other cloud all the other IoT. You really need to make sure all these different piece working together, communicate together and the best way is really, they have to have a single panel of our management service. They can look at them, they can make it integrate together they can automate together, because today's attack can happen within seconds when they get in the company network. It's very difficult for human to react on that. That's where how to integrate, how to automate, this different piece, that is so important. That's where the Fabric approach, the infrastructure approach get very important. Otherwise, you cannot react quick enough, in fact, to defend yourself in a current environment. On the other side for your question, how many vendor do you have, I feel the less the better. At least they have to work together. If they're not working together, will make it even more difficult to defend because each part they not communicate and not react and not automate will make the job very, very difficult and that's where all this working together and the less vendor they can all responsible for all your security it's better. So that's where we see some consolidation in the space. They do still have a lot of new company come up, like you mentioned, there's close to 2,000 separate security company. A lot of them try to address the point solution. I mentioned there's a four different level engineer after engineer work there because I see 90% company they do the detection. There's a certain application you can detect the intrusion and then the next level is where they after you attack what are going to do about it. Is it really the prevention setting kick in automatic pull out the bad actor. After that, then you need to go to the integration because there's so many different products, so many different piece you need to working together, that's the integration. Eventually the performance and cost. Because security on average still cost 100 times more expensive under same traffic and also much slower compared to the routing switch in networking device. That's what the performance cost. Also starting in the highest level, that's also very difficult to handle. >> So, we're just enough to start with the idea of data integration, secure data integration amongst the security platform, so enough to do as little as possible, as few as possible to do that, but enough to cover all the infrastructure. >> Yes, because the data is all a whole different structure. You no longer does have to trust environment. Because even inside the company, there's so many different way you can access to the outside, whether it by your mobile device so there's a multiple way you can connect on the internet and today in the enterprise 90% connection goes to Wi-Fi now it's not goes to a wired network, that's also difficult to manage. So that's where we will hide it together and make it all working together it's very important. >> So, in the spirit of collaboration, collaborating with vendors. When you're talking with enterprises that have this myriad security solutions in place now, how are they helping to guide and really impact Fortinet's technologies to help them succeed. What's that kind of customer collaboration like, I know you meet with a lot of customers, how are they helping to influence the leading security technologies you deliver? >> We always want to listen the customer. They have the highest priority, they gave us the best feedback. Like the presentation they talked about there's a case from Olerica which is where they have a lot of branch office and they want to use in the latest technology and networking technology, SD-WAN. Are working together with security, that's ready the new trend and how to make sure they have all the availability, they have the flexibility software-defined networking there and also make sure to security also there to handle the customer data, that's all very important so that's what we work very closely with customer to response what they need. That's where I'm still very proud to be no longer kind of engineer anymore but will still try to build in an engineer technology company. Listen to the customer react quick because to handle security space, cyber security, internet security, you have to work to quickly react for the change, on internet, on application. So that's where follow the customer and give them the quick best solution it's very very important. >> On the customer side in Anaemia we talked about that was talked a little bit about this morning with GDPR are is around the corner, May 2018. Do you see your work coordinates work with customers in Anaemia as potentially being, kind of, leading-edge to help customers in the Americas and Asia-Pacific be more prepared for different types of compliance regulations? >> We see the GDPR as an additional opportunity, as a additional complement solution compared to all the new product technology would come up. They definitely gave us an additional business rate, additional opportunity, to really help customer protect the data, make the data stay in their own environment and the same time, internet is a very global thing, and how to make sure different country, different region, working together is also very important. I think it's a GDPR is a great opportunity to keeping expanding a security space and make it safer for the consumer for the end-user. >> So Ken as CEO Fortinet or a CEO was tough act, but as CEO you have to be worried about the security of your business and as a security company you're as much attacked, if not more attacked than a lot of other people because getting to your stuff would allow folks to get to a lot of other stuff. How do you regard the Fortinet capabilities inside Fortinet capability as providing you a source of differentiation in the technology industry? >> Yeah we keep security in mind as the highest priority within a company. That's where we develop a lot of product, we also internally use tests first. You can see from endpoint, the network side, the email, to the web, to the Wi-Fi access, to the cloud, to the IoT, it's all developing internally, it tests internally so the infrastructure security actually give you multiple layer protection. No longer just have one single firewall, you pass the fire were all open up. It's really multiple layer, like a rather the ransomware or something they had to pass multiple layer protection in order to really reach the data there. So that's where we see the infrastructure security with all different products and developed together, engineer working together is very important. And we also have were strong engineer and also we call the IT security team lead by Phil Cauld, I think you are being interview him later and he has a great team and a great experience in NSA for about 30 years, secure country. And that's where we leverage the best people, the best technology to provide the best security. Not only the portal side, also our own the internal security in this space. >> So, in the last minute or so that we have here, one of the things that Patrice Perce your global sales leader said during his keynote this morning was that security transformation, this is the year for it. So, in a minute or so, kind of what are some of the things besides fueling security transformation for your customers do you see as priorities and an exciting futures this year for Fortinet, including you talked about IoT, that's a $9 billion opportunity. You mentioned the securing the connected car to a very cool car in there, what are some of the things that are exciting to you as the leader of this company in 2018? >> We host some basic technology, not another company has. Like a built in security for a single chip. I also mentioned like some other bigger company, like a Google started building a TPU for the cloud computing and Nvidia the GPU. So we actually saw this vision 18 years ago when we start a company and the combine the best hardware and best technology with solve for all this service together. So, long term you will see the huge benefit and that's also like translate into today you can see all these technology enable us to really provide a better service to the customer to the partner and we all starting benefit for all this investment right now. >> Well Ken, thank you so much for joining us back on theCUBE. It's our pleasure to be here at the 16th year of the event, our second time here. Thanks for sharing your insight and we're looking forward to a great show. >> Thank you, great questions, it's the best platform to really promoting the technology, promoting the infrastructure security, thank you very much. >> Likewise, we like to hear that. For my co-host Peter Burris, I'm Lisa Martin, we are coming to you from Fortinet Accelerate 2018. Thanks for watching, stick around we have great content coming up.

>> (Narrator) Live from Las Vegas. It's theCUBE. Covering Fortinet Accelerate 18. Brought to you by Fortinet. >> Welcome to Fortinet Accelerate 2018. I'm Lisa Martin with theCUBE and we're excited to be here doing our second year of coverage of this longstanding event. My cohost for the day is Peter Burris; excited to be co-hosting with Peter again, and we're very excited to be joined by the CEO, Founder, and Chief Chairman of Fortinet, Ken Xie, Ken welcome back to theCUBE. >> Thank you, Lisa, thank you, Peter. Happy to be here. >> It's great to be here for us as well, and the title of your Keynote was Leading the Change in Security Transformation, but something as a marketer I geeked out on before that, was the tagline of the event, Strength in Numbers. You shared some fantastic numbers that I'm sure you're quite proud of. In 207, $1.8 in billing, huge growth in customer acquisitions 17.8 thousand new customers acquired in 2017 alone, and you also shared that Forinet protects around 90% of the Global S&P 100. Great brands and logos you shared Apple, Coca Cola, Oracle. Tell us a little bit more and kind of as an extension of your Keynote, this strength in numbers that you must be very proud of. >> Yeah, I'm an engineer background, always liked the number, and not only we become much bigger company, we actually has 25 to 30% global employment in a network security space. That give a huge customer base and last year sales grow 19% and we keeping leading the space with a new port out we just announced today. The FortiGate 6000 and also the FortiOS 6.0. So all this changing in the landscape and like I said last year we believe the space is in a transition now, they've got a new generation infrastructure security, so we want to lead again. We started the company 18 years ago to get into we called a UTM network firewall space. We feel infrastructure security is very important now. And that we want to lead in the transition and lead in the change. >> So growth was a big theme or is a big theme. Some of the things that we're also interesting is another theme of really this evolution, this landscape I think you and Peter will probably get into more the technology, but give our viewers a little bit of an extension of what you shared in your keynote about the evolution. These three generations of internet and network security. >> Yeah, when I first start my network security career the first company I was study at Stanford University, I was in the 20s. It was very exciting is that a space keeping changing and grow very fast, that makes me keeping have to learning everyday and that I like. And then we start a company call Net Screen when it was early 30s, that's my second company. We call the first generation network security which secured a connection into the trust company environment and the Net Screens a leader, later being sold for $4 billion. Then starting in 2000, we see the space changing. Basically you only secure the connection, no longer enough. Just like a today you only validate yourself go to travel with a ticket no longer enough, they need to see what you carry, what's the what's the luggage has, right. So that's where we call them in application and content security they call the UTM firewall, that's how Fortinet started. That's the second generation starting replacing the first generation. But compared to 18 years ago, since change it again and nowadays the data no longer stay inside company, they go to the mobile device, they go to the cloud, they call auditive application go to the IoT is everywhere. So that's where the security also need to be changed and follow the important data secure the whole infrastructure. That's why keeping talking from last year this year is really the infrastructure security that secure fabric the starting get very important and we want to lead in this space again like we did 18 years ago starting Fortinet. >> Ken, I'd like to tie that, what you just talked about, back to this notion of strength in numbers. Clearly the bad guys that would do a company harm are many and varied and sometimes they actually work together. There's danger in numbers Fortinet is trying to pull together utilizing advanced technologies, new ways of using data and AI and pattern recognition and a lot of other things to counter effect that. What does that say about the nature of the relationships that Fortinet is going to have to have with its customers going forward? How is that evolving, the idea of a deeper sharing? What do you think? >> Actually, the good guy also started working together now. We formed the they call it the Cyber Threat Alliance, the CTA, and Fortinet is one of the founding company with the five other company including Palo Alto Network, Check Point and McAfee and also feel a Cisco, there's a few other company all working together now. We also have, we call, the Fabric-Ready Program which has a 42 bigger partner including like IBM, Microsoft, Amazon, Google, all this bigger company because to defend the latest newest Fabric threat you have to be working together and that also protect the whole infrastructure. You also need a few company working together and it's a because on average every big enterprise they deploy 20 to 30 different products from different company. Management cost is number one, the highest cost in the big enterprise security space because you have to learn so many different products from so many different vendor, most of them competitor and now even working together, now communicate together. So that's where we want to change the landscape. We want to provide how infrastructure security can work better and not only partner together but also share the data, share the information, share the intelligence. >> So fundamentally there is the relationship is changing very dramatically as a way of countering the bad actors by having the good actors work more closely together and that drives a degree of collaboration coordination and a new sense of trust. But you also mentioned that the average enterprise is 20 to 30 fraud based security products. Every time you introduce a new product, you introduce some benefits you introduce some costs, potentially some new threat surfaces. How should enterprises think about what is too many, what is not enough when they start thinking about the partnerships that needed put together to sustain that secure profile? >> In order to have the best protection today you need to secure the whole infrastructure, the whole cyberspace. Network security still the biggest and also grow very fast and then there's the endpoint and there's a like a cloud security, there's a whole different application, email, web and all the other cloud all the other IoT. You really need to make sure all these different piece working together, communicate together and the best way is really, they have to have a single panel of our management service. They can look at them, they can make it integrate together they can automate together, because today's attack can happen within seconds when they get in the company network. It's very difficult for human to react on that. That's where how to integrate, how to automate, this different piece, that is so important. That's where the Fabric approach, the infrastructure approach get very important. Otherwise, you cannot react quick enough, in fact, to defend yourself in a current environment. On the other side for your question, how many vendor do you have, I feel the less the better. At least they have to work together. If they're not working together, will make it even more difficult to defend because each part they not communicate and not react and not automate will make the job very, very difficult and that's where all this working together and the less vendor they can all responsible for all your security it's better. So that's where we see some consolidation in the space. They do still have a lot of new company come up, like you mentioned, there's close to 2,000 separate security company. A lot of them try to address the point solution. I mentioned there's a four different level engineer after engineer work there because I see 90% company they do the detection. There's a certain application you can detect the intrusion and then the next level is where they after you attack what are going to do about it. Is it really the prevention setting kick in automatic pull out the bad actor. After that, then you need to go to the integration because there's so many different products, so many different piece you need to working together, that's the integration. Eventually the performance and cost. Because security on average still cost 100 times more expensive under same traffic and also much slower compared to the routing switch in networking device. That's what the performance cost. Also starting in the highest level, that's also very difficult to handle. >> So, we're just enough to start with the idea of data integration, secure data integration amongst the security platform, so enough to do as little as possible, as few as possible to do that, but enough to cover all the infrastructure. >> Yes, because the data is all a whole different structure. You no longer does have to trust environment. Because even inside the company, there's so many different way you can access to the outside, whether it by your mobile device so there's a multiple way you can connect on the internet and today in the enterprise 90% connection goes to Wi-Fi now it's not goes to a wired network, that's also difficult to manage. So that's where we will hide it together and make it all working together it's very important. >> So, in the spirit of collaboration, collaborating with vendors. When you're talking with enterprises that have this myriad security solutions in place now, how are they helping to guide and really impact Fortinet's technologies to help them succeed. What's that kind of customer collaboration like, I know you meet with a lot of customers, how are they helping to influence the leading security technologies you deliver? >> We always want to listen the customer. They have the highest priority, they gave us the best feedback. Like the presentation they talked about there's a case from Olerica which is where they have a lot of branch office and they want to use in the latest technology and networking technology. I see when I'm working together with security, that's ready the new trend and how to make sure they have all the availability, they have the flexibility software-defined networking there and also make sure to security also there to handle the customer data, that's all very important so that's what we work very closely with customer to response what they need. That's where I'm still very proud to be no longer kind of engineer anymore but will still try to build in an engineer technology company. Lesson to the customer react quick because to handle security space, cyber security, internet security, you have to be work quickly react for the change, on internet, on application. So that's where follow the customer and give them the quick best solution it's very very important. On the customer side in Anaemia we talked about that was talked a little bit about this morning with GDPR are is around the corner, May 2018. Do you see your work coordinates work with customers in Anaemia as potentially being, kind of, leading-edge to help customers in the Americas and Asia-Pacific be more prepared for different types of compliance regulations? >> We see the GDPR as an additional opportunity, as a additional complement solution compared to all the new product technology would come up. They definitely gave us an additional business rate, additional opportunity, to really help customer protect the data, make the data stay in their own environment and the same time, internet is a very global thing, and how to make sure different country, different region, working together is also very important. I think it's a GDPR is a great opportunity to keeping expanding a security space and make it safer for the consumer for the end-user. >> So Ken as CEO Fortinet or a CEO was tough act, but as CEO you have to be worried about the security of your business and as a security company you're as much attacked, if not more attacked than a lot of other people because getting to your stuff would allow folks to get to a lot of other stuff. How do you regard the Fortinet capabilities inside Fortinet capability as providing you a source of differentiation in the technology industry? >> Yeah we keep security in mind as the highest priority within a company. That's where we develop a lot of product, we also internally use tests first. You can see from endpoint, the network side, the email, to the web, to the Wi-Fi access, to the cloud, to the IoT, it's all developing internally, it tests internally so the infrastructure security actually give you multiple layer protection. No longer just have one single firewall, you pass the fire were all open up. It's really multiple layer, like a rather the ransomware or something they had to pass multiple layer protection in order to really reach the data there. So that's where we see the infrastructure security with all different products and developed together, engineer working together is very important. And we also have were strong engineer and also we call the IT security team lead by Phil Cauld, I think you are being interview him later and he has a great team and a great experience in NSA for about 30 years, secure country. And that's where we leverage the best people, the best technology to provide the best security. Not only the portal side, also our own the internal security in this space. >> So, in the last minute or so that we have here, one of the things that Patrice Perce your global sales leader said during his keynote this morning was that security transformation, this is the year for it. So, in a minute or so, kind of what are some of the things besides fueling security transformation for your customers do you see as priorities and an exciting futures this year for Fortinet, including you talked about IoT, that's a $9 billion opportunity. You mentioned the securing the connected car to a very cool car in there, what are some of the things that are exciting to you as the leader of this company in 2018? >> We host some basic technology, not another company has. Like a built in security for a single chip. I also mentioned like some other bigger company, like a Google started building a TPU for the cloud computing and Nvidia the GPU. So we actually saw this vision 18 years ago when we start a company and the combine the best hardware and best technology with solve for all this service together. So, long term you will see the huge benefit and that's also like translate into today you can see all these technology enable us to really provide a better service to the customer to the partner and we all starting benefit for all this investment right now. >> Well Ken, thank you so much for joining us back on theCUBE. It's our pleasure to be here at the 16th year of the event, our second time here. Thanks for sharing your insight and we're looking forward to a great show. >> Thank you, great questions, it's the best platform to really promoting the technology, promoting the infrastructure security, thank you very much. >> Likewise, we like to hear that. For my co-host Peter Burris, I'm Lisa Martin, we are coming to you from Fortinet Accelerate 2018. Thanks for watching, stick around we have great content coming up.

(upbeat instrumental music) >> Hey welcome back everybody. Jeff Frick here with the Cube. We're at the RSA Conference in downtown San Francisco. 40,000 security professionals here talking about how to keep us all safe, especially when we're in autonomous vehicles, especially when we have connected nest devices. It's a crazy wild world. We're excited to be joined by Derek Manky, the global security strategist for Fortinet. Welcome. >> Hey thanks, pleasure to be here. >> Absolutely. >> We'll talk security right? >> Well I hope so. So for folks that aren't familiar with Fortinet, give us kind of the overview of what you guys are doing. >> Sure I mean tons of different things. So, you know, my department, I work directly with our global threat intelligence team and our labs. So for over 15 years now, we've been building up our labs. We have over 200 threat analysts and researchers worldwide combing through data at any given minute. But the problem is, the data. We live in a big data world now. There's so much, it's very easy to become overwhelmed with data. So we've taken an approach where we have a very intelligent human expertise team, but we've invested a lot into automation, machine learning, artificial intelligence, that you're going to find that's a very important thing moving forward because we need to be able to stay on par with the bad guys. >> Right right. >> The bad guys are very good at automation. They don't have anything holding them down. They're flying full-force, so we're trying to keep up to them. And, you know there's a lot of great initiatives like cyber threat alliance, of course, so we made a big announcement this week on that too. >> Right. So really as things have evolved over those 10 years, I mean the bad news is the amount of data that you guys have to keep track of is growing exponentially. The good news is the tools like machine learning and AI and Spark and Hadoop and, you know the tools that you have to use are much more sophisticated as well. It kind of works both sides of the coin at the same time. >> Yeah but you know what? One thing that we found is that there is a lot of information here, there is a lot of data being thrown out there. You have to make sense of the data. So a big theme and a big focus of ours is making data actionable. So threat intelligence actionable. How do you cross what we call the last mile? How do you take data and information and put it into transparent security controls so the end users, like all of our customers, don't have to do that manually. The manual work is what's killing a lot of people out there. There's a huge gap in cyber security professionals out there. People like network administrators, by the time they receive, say, a PDF document or something manual that they have to plug in an IP address or an update, it's often too late. A lot of this information is very perishable, very fluid. So, we're trying to automate that into the security controls. That comes from a lot of that big data, analytics on the back end. We call it a security fabric. So this is where we can weave in that information into all of our different products. End point, from end point all the way up to the cloud. And the cyber threat alliance is a very big initiative. So we're a founding member of that along with the other founding members I mentioned this week. We're working together to share information. And the goal of that is to share information on a platform and then as a member of the CTA founding member take that information in and push that out into those controls in near real time. That's the big thing. >> That was the big thing right? Because people have shared data before. But it's really kind of this real time emphasis to get it in real time. You know using things like Spark and streaming data. So that you're not reacting after the fact. In the old stat they used to quote us, you know people didn't even know for like 250 days. >> Derek: Yeah. >> Or whatever it was. >> We're bringing a lot of illumination to intelligence as well. Visibility's a big thing. Speed is a very big thing right? How can we get that information out very quickly because like I said the bad guys are moving a million miles a minute. So it's a really important initiative what we're doing with that. The other thing is the quality of information. A lot of information is too hastily shared and I think humans we're at that tipping point right now. Where humans can't fully trust automation. It's like autonomous vehicles. >> Right right. >> You're not going to put it fully in control right? You have to start getting a trust exercise with it and that's what we're trying to do, a lot of this intelligence. >> What was interesting in the keynote this morning one of the new threads they highlighted is people actually feeding the algorithms bad information. >> Poisoning yeah, yeah. Absolutely, yeah, yeah. >> Salting the algorithm is what they call it. To send it down a different path than it should be going. >> I mean the bad guys will put all this thought throughout and evasion techniques. But that's another really nice thing about the cyber threat alliance. Is that we're all collaborating. So we're giving confidence ratings to this. So it's also a quality of sharing system which the industry very badly needs in my opinion too. >> So what's next? Looking at 2017, we're getting started this February. Oh it's Valentine's Day February 14. >> Happy Valentine's Day. >> Happy Valentine's. So a year from now and we talk, what's the top of my priorities? What are you working on for the next little while? >> Yeah absolutely. Again we're going down the CMO automation. You're going to see a lot on the security fabric that we have. So this is how we can have machines automatically learning about environments. Automatically adapting to environments. You look at a lot of security problems out there a lot of the times it's security 101. It's people misconfiguring firewalls, misconfiguring policies and devices. Not having a proper security device in front of their crown jewels or their asset, their digital asset. So that is a big theme that we're doing, it's taking that intelligence and starting to empower our products and solutions to make intelligence decisions on their own. >> Right. >> That's a very big leap forward and we've made significant progress with that. >> It's interesting that you mention that. There's still a lot of 101 work that people aren't doing to the degree that they should. There was a great line in the keynote this morning that every company has at least one person that will click on anything. >> Weakest link in the chain right? Yeah. >> Absolutely. Alright well Derek thanks for stopping by. And congrats on a great show. And really some exciting stuff with that cyber threat alliance. >> Great yeah thanks, a pleasure. >> Alright he's Derek Manky I'm Jeff Frick. You're watching the Cube from RSA in downtown San Francisco. Thanks for watching. (instrumental music)