(gentle music) >> From theCUBE Studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Hi, I'm Stu Miniman. And this is a special CUBE conversation. We've been talking a lot, of course for many years about the ascendancy of cloud. And today in 2020, multicloud is a big piece of the discussion. And we're really happy to help unveil coming out of stealth Alkira, which is helping the networking challenges when it comes to multicloud and I have the two co-founders, they are brothers. I have Amir, who is the CEO and Atif, who is the CTO, the Khan brothers, thank you so much for joining us, and congratulation on the launch of the company. >> Thank you Stu for having us on the Show. It's a pleasure to see you again. >> All right, so Amir, we've had you on the program. Your previous company that you've done was of course Viptela, the two of you have worked together at, I believe, five companies, a successful companies. Acquired the most recent one into Cisco. So, Amir, obviously, strong networking team, your brother, the CTO is going to talk to us about the engineering but give us just the story of Alkira, what you've been building and now ready to unveil to the world. >> Certainly, Stu, so when around 2018 timeframe, we started looking into the next big problem to solve in the industry, which was not only a substantial from the market size perspective, but also from the customers perspective was solving a major pain point. So when we started looking into the cloud customers and started talking to our customers, they were struggling from the cloud networking perspective, even in a single cloud, and it was a new environment for them and they had to understand all the nitty gritty details of each one of these clouds and when you go to multicloud environment, it becomes exponentially complicated to address not only connectivity, but how to deploy services like firewall and other services, including load balancers and IP address management, et cetera, and remote access. So we started digging deeper into this problem and started working with the customers and took a clean sheet of paper and came up with a very comprehensive approach to offering a solution which is as-a Service. This time, we are not shipping any hardware software it is just like any other SaaS application, you just come to our portal just drag and drop, literally draw out your network and click on provision. And come back after 40 minutes or so your whole global cloud infrastructure is up and running. >> All right, Atif your brother laid out a pretty broad vision there, any of us from the networking world, we know there's a lot of complexity there. And therefore it takes a lot of work, when I want to do things simply, as-a Service is a huge growth area bring us inside the engineering challenges that you and the team have been working on to build this solution. >> Certainly, Stu, so we've been working both Amir and myself in the networking industry for more than 25 years now. And the way we have worked and what we have believed in is that we need to solve customer problems. We never believe in doing a science project. So here also we started working with customers as we have always done in the past. We understood the customers pain points, the challenges they were facing, especially in this case and in cloud networking space, multicloud networking space, based on the user requirements, users, or the customers use cases, we started building our service. And here what we have built as a complete network as-a Service. It's a multicloud network as-a service, which not only provides connectivity to multiple clouds, but also addresses the needs for bringing in networking services, as well as security services, making sure that you have a full policy based infrastructure on top of it, you have deep visibility into the clouds as well as into on-premise end to end visibility, end to end monitoring, troubleshooting. And all of it is delivered to you as-a service. So that's what we have been doing here at Alkira. >> Excellent! So when we've looked at multicloud, of course, every cloud, they have some similar things, they have some different things. They all tend to do things a little bit differently. One of the secret sauces that have been talked about for the last few years is the SD-WAN space, like you had built with the tele to help really enable those environments. So Atif we've got a diagram here, which I think will help explain a little bit as to where out here and how it plugs into these different environments, walk us through a little bit what we're seeing here, and what you're actually doing at Alkira. >> So here we are building a global unified, multicloud network. It's consumed as a service. Think of it as consuming it just like you would consume any other SaaS, like our SaaS application. So you come to Alkira's portal, you register. And then there you go, and you start building your global multicloud unified network with integrated services. So here what you see is a Alkira's cloud services exchange which comprises of the cloud exchange points. You can bring these up these cloud exchange points up anywhere on the globe. You can decide like what networking services security services you need in these cloud exchange points, you can connect to multiple clouds. From there, you can bring your existing on-prem connectivity into the CXPs. All these CXPs have a full mesh of overlay, high speed, low latency connectivity among each other. So there is a full network which comes up between these CXPs. And the whole infrastructure scales with customers as our customers scale. So it's a horizontally scalable, very highly redundant and resilient infrastructure, which we had built. >> All right, so, Amir now that we understand the basics of the technology, you've got some strong investors including Sequoia, Kleiner Perkins, give us what is being announced that you're coming out of stealth, where are you with the product? How many employees you have? And where are you with the discussion of customer adoption. >> So Stu we are obviously, bringing this to the market, and we will be announcing it on April 15. It's available for the customers to consume our solution as a service on that day. So they are welcome to reach out to us and we'll be happy to help them. And as a matter of fact, just come to our website and register for the service. And yeah, I mean you rightly said that we have a superstar team of not only the venture capital companies, but also the board members representing those companies, the Bill Coffin and Mamun Ahmed, who the leading VCs are on the board of our company, including myself and Atif. >> All right, Amir I'd love to actually bring up the second slide that we have here. Walk us through you said the service, how do people get started? How do they understand, walk us through what they do. >> So the biggest challenge when we started looking into these problems, Stu was that it was very complicated. You had to piecemeal bring up instances in the cloud and stitch them together. And when you try to integrate the services, that was a different challenge for the customers. So we want to make sure that it was so simple and clean, that the customer didn't even have to think about any underlying construct on any of the clouds, they should not have to worry about learning each individual part from the networking perspective. So here's your portal, you just come, step one is come to our portal register. Step two is you start drawing your network based on your intent, what on-prem connectivity you want to bring into this service, what type of services you need, like a lot of firewalls and then what pilots you need to connect and everything happens seamlessly, from on-prem, prem through services into the cloud, across multiple clouds. It's a seamless service that we have created and with full analytics capabilities and full governance built in. >> All right, so Atif bring us into what this means for customers, how do they manage it? Is this the networking team? Is it the cloud architects? What API's are there? How does this fit into kind of what customers are doing today? And solve some of those challenges that we laid out earlier in the discussion. >> Yes, from the customer's perspective, as I said, it's completely delivered as a service. Customers come to our portal, they draw out the network, they select the services, they click on provision and the whole network comes up within minutes. So the main thing here is that from a customer's point of view, if they are connecting to different clouds, they don't need to understand any of the underlying specifics or underlying constructs of any of the cloud in order to bring up connectivity. So what we are doing here is we are abstracting the cloud chair. So we are building a virtual cloud network. So if you think of, if you compare with what we did in the previous life, we virtualized the WAN. So here what we are doing is we are virtualizing the cloud network, so underlying doesn't matter which cloud you sit on which cloud you need to connect to, which networking services, whether a cloud native services or whether you want to consume Alkira services, or we also support like customer bringing in third party services as well. So it's all offered from our platform all offered is service to the customer. Again, no expertise required in any of the underlying networking constructs of any of these clouds. >> Give us what we should be looking at from a technology roadmap from Alkira, through the rest of 2020. >> Good question, Stu. So as I mentioned earlier, our roadmap is dictated by customer requirements, so we prioritize what customers need from us. So we have come out with a scalable platform, we have come out with a marketplace for networking services in there. In the near term, we'll be expanding our marketplace with more services. We will be addressing more use cases and when I talk about use cases, I can give you some examples. Like there's, you not just only need connectivity into cloud, you might have different requirements from throughput perspective or bandwidth perspective or different services that you need to contend your cloud when you may have certain applications such as Internet facing application where you need like traffic coming in from the internet, inbound to those applications, you might need services like a load balancer, like an external load balancer in our services exchange. You might also need like a firewall, you might need traffic engineering, or sorry, service chaining capabilities where you chain service through multiple traffic through multiple of these services like a firewall and a load balancer. So we built a platform which gives you all those capabilities going forward, we will be adding more services more use cases to it. We have a long ways ahead of us and we will be putting a lot of effort in delivering a roadmap as we go. >> All right, so Amir your technical team definitely has their hands full and robust roadmap to work on. Give us the high level, what we should be looking for Alkira, for people that are out there, multicloud and networking tends to get talked a lot. There's many big companies and small ones. What will separate Alkira from the rest of the market today? And what should we be looking to see the company's progression through 2020? >> Yeah, thanks for asking that. Yeah, certainly. I mean, from the solution perspective, Atif said that it's so fundamentally important to have a very strong basis. And that's what we have done. We are bringing out a certain number of services and now we will continue to grow on that we'll create a big marketplace. We will continue to improve on which clouds we connect to and how and we will building our own services in certain cases as well. Now, building a technology is just one piece of it, we have to go out to market with a company that the customers can trust every single department in that company, whether it's sales or how they do business with us all the business back end pieces, after we sorted out and that's what we've been working with. And then go to market partners, that is very, very important, support is very important. So let me spend a little bit of time on go to market strategy. We have been working with the service providers so that we can extend our reach not only to the large customers, but also to mid-size customers across the globe. So you will see us in the future announcing major service provider, partnerships, as well as we've been working with large SIS, WAAS and system integration partners. And also we have taking a slightly different approach this time because it's a service. So we are going with telecom master agents, which have been working with the service providers, the cloud providers, the cable providers, as a channel, and they have a huge reach into the customer base. So we have a very comprehensive strategy not only from the go to market perspective and the technology perspective, but also how we are going to support our customers and continue to build our relationship to build a lasting company. >> Yeah, Amir super important point there. Absolutely, we've seen the maturation and change in the service providers, as today they are working with many of the public cloud providers and they're, as you said, the close touch point and a trusted partner for customers. All right, so before I let you go, you two are brothers, everybody in today's day and age is spending even more time with family but your situation you've worked together for a long time. What keeps bringing the two of you together, working together and talk about that bond? >> So I mean we're a very close knit family, we have four brothers and one sister, and obviously Atif and I have been the closest because we have been working together for the longest, we've at least work in five different companies together, our families traveled together, we have three daughters each, we live about five minutes, walk from each other. And we just have this bond where we not only have the family close, but also very close knit friends circle, which we both hang out with, and we obviously have common interests in the sports as well. We play squash and tennis and workout. So Atif if you want to take a stab at that also. >> Yeah, so we've always been very close. In fact, we've been together for the last like, ever since I can remember like even college days, we were roommates for some time also, we have our circle of friends, is the same old source. So, again, we are very close. And we worked well together so we complement each other's skills. And it's worked out in the past. Hopefully it will work out again. And I look forward to working with them for many, many more years to come. >> Amir and Atif thank you so much for sharing the coming out of stealth. After all, Alkira we definitely look forward to watching your progress and seeing how you're helping customers in this multicloud world. Thank you for joining us. >> Stu thank you so much. >> Thank you for having us. >> All right, I'm Stu Miniman. And thank you so much for watching this special CUBE conversation on theCUBE. (gentle music)

>>mhm Yes. >>Hello and welcome back to the cubes coverage of dr khan 2021 virtual. I'm john Kerry hosted the Q got a great cube segment here. Simon Maple Field C T Oh it's technique. Great company security shifting left great to have you on Simon. Thanks for thanks for stopping by >>absolute pleasure. Thank you very much for having me. >>So you guys were on last year the big partnership with DR Conn remember that interview vividly because it was really the beginning at the beginning but really come to me the mainstream of shifting left as devops. It's not been it's been around for a while. But as a matter of practice as containers have been going super mainstream. Super ballistic in the developer community then you're seeing what's happening. It's containers everywhere. Security Now dev sec apps is the standard. So devops great infrastructure as code. We all know that but now it's def sec ops is standard. This is the real deal. Give us the update on what's going on with sneak. >>Absolutely, yeah. And you know, we're still tireless in our approach of trying to get make sure developers don't just have the visibility of security but are very much empowered in terms of actually fixing issues and secure development is what we're really striving for. So yeah, the update, we're still very, very deep into a partnership with DACA. We have updates on DR desktop which allows developers to scan the containers on the command line, providing developers that really fast feedback as as early as possible. We also have uh, you know, new updates and support for running Docker scan on Lennox. Um, and yeah, you know, we're still there on the Docker hub and providing that security insights um, to, to users who are going to Docker hub to grab their images. >>Well, for the folks watching maybe for the first time, the sneak Docker partnership, we went in great detail last year was the big reveal why Docker and sneak partnership, what is the evolution of that partnership over the year? They speak highly of you guys as a developer partner. Why Doctor? What's the evolution looked like? >>It's a it's a really great question. And I think, you know, when you look at the combination of DACA and sneak well actually let's take let's take each as an individual. Both companies are very, very developer focused. First of all, right, so our goals and will be strife or what we what we tirelessly spend their time doing is creating features and creating, creating an environment in which a developer you can do what they need to do as easily as possible. And that, you know, everyone says they want to be developer friendly, They want to be developer focused. But very few companies can achieve. And you look at a company like doctor, you're a company like sneak it really, really provides that developer with the developer experience that they need to actually get things done. Um, and it's not just about being in a place that a developer exists. It's not enough to do that. You need to provide a developer with that experience. So what we wanted to do was when we saw doctor and extremely developer friendly environment and a developer friendly company, when we saw the opportunity there to partner with Yoko, we wanted to provide our security developer friendliness and developer experience into an already developed a friendly tool. So what the partnership provides is the ease of, you know, deploying code in a container combined with the ease of testing your code for security issues and fixing security issues in your code and your container and pulling it together in one place. Now, one of the things which we as a as a security company um pride ourselves on is actually not necessarily saying we provide security tools. One of what our favorite way of saying is we're a developer tooling company. So we provide tools that are four developers now in doing that. It's important you go to where the developers are and developers on DACA are obviously in places like the Docker hub or the Docker Cli. And so it's important for us to embed that behavior and that ease of use inside Dhaka for us to have that uh that that flow. So the developer doesn't need to leave the Docker Cli developer that doesn't need to leave Docker hub in order to see that data. If you want to go deeper, then there are probably easier ways to find that data perhaps with sneak or on the sneak site or something like that. But the core is to get that insight to get that visibility and to get that remediation, you can see that directly in in the in the Dhaka environment. And so that's what makes the relationship so so powerful. The fact that you combine everything together and you do it at source >>and doing it at the point of code. >>Writing >>code is one of the big things I've always liked about the value proposition is simple shift left. Um So let's just step back for a second. I got to ask you this question because this I wanted to make sure we get this on the table. What are the main challenges uh and needs to, developers have with container security? What are you seeing as the main top uh A few things that they need to have right now for the challenges uh with container security? >>Yeah, it's a it's a very good question. And I think to answer that, I think we need to um we need to think of it in a couple of ways. First of all, you've just got developers security uh in general, across containers. Um And the that in itself is there are different levels at which developers engage with containers. Um In some organizations, you have security teams that are very stringent in terms of what developers can and can't do in other organizations. It's very much the developer that that chooses their environment, chooses their parent image, et cetera. And so there when a developer has many, many choices in which they need to need to decide on, some of those choices will lead to more issues, more risk. And when we look at a cloud native environment, um uh Let's take let's take a node uh image as an example, the number of different uh images tags you can choose from as a developer. It's you know, there are hundreds, probably thousands. That you can actually you can actually choose. What is the developer gonna do? Well, are they going to just copy paste from another doctor file, for example, most likely. What if there are issues in that docker file? They're just gonna copy paste that across mis configurations that exist. Not because the developer is making the wrong decision, but because the developer very often doesn't necessarily know that they need to add a specific directive in. Uh So it's not necessarily what you add in a conflict file, but it's very often what you admit. So there are a couple of things I would say from a developer point of view that are important when we think about cloud security, the first one is just that knowledge that understanding what they need to do, why they need to do it. Secure development doesn't need to be, doesn't mean they need to be deep in security. It means they need to understand how they can develop securely and what what the best decisions that could come from guard rails, from the security team that they provide the development team to offer. But that's the that's an important error of secure development. The second thing and I think one of the most important things is understanding or not understanding necessarily, but having the information to get an act on those things early. So we know the length of time that developers are uh working on a branch or working on um some some code changes that is reducing more and more and more so that we can push to production very, very quickly. Um What we need to do is make sure that as a developer is making their changes, they can make the right decision at the right time and they have the right information at that time. And a lot of this could be getting information from tools, could be getting information from your team where it could be getting information from your production environments and having that information early is extremely important to make. That decision. May be in isolation with your team in an autonomous way or with advice from the security team. But I would say those are the two things having that information that will allow you to make that action, that positive change. Um uh and and yeah, understanding and having that knowledge about how you can develop security. >>All right. So I have a security thing. So I'm a development team and by the way, this whole team's thing is a huge deal. I think we'll get to that. I want to come back to that in a second but just throw this out there. Got containers, got some security, it's out there and you got kubernetes clusters where containers are coming and going. Sometimes containers could have malware in them. Um and and this is, I've heard this out and about how do how that happens off container or off process? How do you know about it? Is that infected by someone else? I mean is it gonna be protected? How does the development team once it's released into the wild, so to speak. Not to be like that, but you get the idea, it's like, okay, I'm concerned off process this containers flying around. What is it How do you track all >>and you know, there's a there's a few things here that are kind of like potential potential areas that, you know, we can trip up when we think about malware that's running um there are certain things that we need to that we need to consider and what we're really looking at here are kind of, what do we have in place in the runtime that can kind of detect these issues are happening? How do we block that? And how do you provide that information back to the developer? The area that I think is, and that is very, very important in order to in order to be able to identify monitor that those environments and then feed that back. So that that that's the kind of thing that can be that can be fixed. Another aspect is, is the static issues and the static issues whether that's in your os in your OS packages, for example, that could be key binaries that exist in your in your in your docker container out the box as well or of course in your application, these are again, areas that are extremely important to detect and they can be detected very very early. So some things, you know, if it's malware in a package that has been identified as malware then absolutely. That can be that can be tracked very very early. Sometimes these things need to be detected a little bit later as well. But yeah, different tools for different for different environments and wear sneak is really focused. Is this static analysis as early as possible. >>Great, great insight there. Thanks for sharing that certainly. Certainly important. And you know, some companies classes are locked down and all of sudden incomes, you know, some some malware from a container, people worried about that. So I want to bring that up. Uh The other thing I want to ask you is this idea of end to end security um and this is a team formation thing we're seeing where modern teams have essentially visibility of their workload and to end. So this is a huge topic. And then by the way it might integrate their their app might integrate with other processes to that's great for containers as well and observe ability and microservices. So this is the trend. What's in it for the developer? If I work with sneak and docker, what benefits do I get if I want to go down that road of having these teams began to end, but I want the security built in. >>Mhm. Yeah, really, really important. And I think what's what's most important there is if we don't look end to end, there are component views and there are applications. If we don't look into end, we could have our development team fixing things that realistically aren't in production anyway or aren't the key risks that are potentially hurting us in our production environment. So it's important to have that end to end of you so that we have the right insights and can prioritize what we need to identify and look at early. Um, so I think, I think that visibility into end is extremely important. If we think about who, who is re fixing uh certain issues, again, this is gonna depend from dog to walk, but what we're seeing more and more is this becoming a developer lead initiative to not just find or be given that information, but ultimately fixed. They're getting more and more responsible for DR files for for I see for for their application code as well. So one of the areas which we've looked into as well is identifying and actually running in cuba Netease workloads to identify where the most important areas that a developer needs to look at and this is all about prioritization. So, you know, if the developer has just a component view and they have 100 different images, 100 different kubernetes conflicts, you know, et cetera. Where do they prioritize, where do they spend their time? They shouldn't consider everything equal. So this identification of where the workloads are running and what um is causing you the most risk as a business and as an organization, that is the data. That can be directly fed back into your, your your vulnerability data and then you can prioritize based on the kubernetes workloads that are in your production and that can be fed directly into the results in the dashboards. That's neat. Can provide you as well. So that end to end story really provides the context you need in order to not just develop securely, but act and action issues in a proper way. >>That's a great point. Context matters here because making it easy to do the right thing as early as possible, the right time is totally an efficiency productivity gain, you see in that that's clearly what people want. It's a great formula, success, reduce the time it takes to do something, reduced the steps and make it easy. Right, come on, that's a that's a formula. Okay, so I gotta bring that to the next level. When I ask you specifically around automation, this is one the hot topic and def sec ops, automation is part of it. You got scale, you got speed, you've got a I machine learning, you go out of all these new things. Microservices, how do you guys fit into the automation story? >>It's a great question. And you know, one of the recent reports that we that we did based on a survey data this year called the state of a state of cloud, native applications security. We we asked the question how automated our people in their in their deployment pipelines and we found some really strong correlations between value from a security point of view um in terms of in terms of having that automation in it, if I can take you through a couple of them and then I'll address that question about how we can be automated in that. So what we found is a really strong correlation as you would expect with security testing in ci in your source code repositories and all the way through the deployment ci and source code were the two of the most most well tested areas across the pipeline. However the most automated teams were twice as likely to test in I. D. S. And testing your CLS in local development. And now those are areas that are really hard to automate if at all because it's developers running running their cli developers running and testing in their I. D. So the having a full automation and full uh proper testing throughout the sclc actually encourages and and makes developers test more in their development environment. I'm not saying there's causation there but there's definite correlation. A couple of other things that this pushes is um Much much more likely to test daily or continuously being automated as you would expect because it's part of the bills as part of your monitoring. But crucially uh 73% of our respondents were able to fix a critical issue in less than a week as opposed to just over 30% of people that were not automated, so almost double people are More likely to fix within a week. 36% of people who are automated can fix a critical security issue in less than a day as opposed to 8% of people who aren't automated. So really strong data that correlates being automated with being able to react now. If you look at something like Sneak what if our um goals of obviously being developer friendly developer first and being able to integrate where developers are and throughout the pipeline we want to test everywhere and often. Okay, so we start as far left as we can um integrating into, you know, CLS integrating into Docker hub, integrating into into doctors can so at the command line you type in doctors can you get sneak embedded in DHAKA desktop to provide you those results so as early as possible, you get that data then all the way through to to uh get reposed providing that testing and automatically testing and importing results from there as well as as well as other repositories, container repositories, being at a poor from there and test then going into ci being able to run container tests in C I to make sure we're not regressing and to choose what we want to do their whether we break, whether we continue with with raising an issue or something like that, and then continuing beyond that into production. So we can monitor tests and automatically send pull requests, etcetera. As and when new issues or new fixes occur. So it's about integrating at every single stage, but providing some kind of action. So, for example, in our ui we provide the ability to say this is the base level you should be or could be at, it will reduce your number of vulnerabilities by X and as a result you're going to be that much more secure that action ability across the pipeline. >>That's a great, great data dump, that's a masterclass right there on automation. Thanks for sharing that sign. I appreciate it. I gotta ask you the next question that comes to my mind because I think this is kind of the dots connect for the customer is okay. I love this kind of hyper focus on containers and security. You guys are all over it, shift left as far as possible, be there all the time, test, test, test all through the life cycle of the code. Well, the one thing that is popping up as a huge growth areas, obviously hybrid cloud devops across both environments and the edge, whether it's five G industrial or intelligent edge, you're gonna have kubernetes clusters at the edge now. So you've got containers. The relationship to kubernetes and then ultimately cloud native work clothes at, say, the edge, which has data has containers. So there's a lot of stuff going on all over the place. What's your, what's your comment there for customer says, Hey, you know, I got, this is my architecture that's happening to me now. I'm building it out. We're comfortable with kubernetes put in containers everywhere, even on the edge how to sneak fit into that story. >>Yeah, really, really great question. And I think, you know, a lot of what we're doing right now is looking at a developer platform. So we care about, we care about everything that a developer can check in. Okay, so we care about get, we care about the repositories, we care about the artifact. So um, if you look at the expansion of our platform today, we've gone from code that people uh, third party libraries that people test. We added containers. We've also added infrastructure as code. So Cuban eighties conflicts, Terror form scripts and things like that. We're we're able to look at everything that the developer touches from their code with sneak code all the way through to your to your container. And I see, so I think, you know, as we see more and more of this pushing out into the edge, cuba Nitties conflict that that, you know, controls a lot of that. So much of this is now going to be or not going to be, but so much of the environment that we need to look at is in the configurations or the MIS configurations in that in those deployment scripts, um, these are some of the areas which which we care a lot about in terms of trying to identify those vulnerabilities, those miS configurations that exist within within those scripts. So I can see yeah more and more of this and there's a potential shift like that across to the edge. I think it's actually really exciting to be able to see, to be able to see those uh, those pushing across. I don't necessarily see any other, any, you know, different security threats or the threat landscape changing as a result of that. Um there could be differences in terms of configurations, in terms of miS configurations that that that could increase as a result, but, you know, a lot of this and it just needs to be dealt with in the appropriate way through tooling through, through education of of of of how that's done. >>Well, obviously threat vectors are all gonna look devops like there's no perimeter. So they're everywhere right? Looking at I think like a hacker to be being there. Great stuff. Quick question on the future relationship with DR. Obviously you're betting a lot here on that container relationship, a good place to start. A lot of benefits there. They have dependencies, they're going to have implications. People love them, they love to use them, helps old run with the new and helps the new run better. Certainly with kubernetes, everything gets better together. What's the future with the DACA relationship? Take us through how you see it. >>So yeah, I mean it's been an absolute blast the doctor and you know, even from looking at some of the internal internal chats, it's been it's been truly wonderful to see the, the way in which both the doctor and sneak from everything from an engineering point of view from a marketing, from a product team. It's been a pleasure to, it's been a pleasure to see that relationship grow and flourish. And, and I think there's two things, first of all, I think it's great that as companies, we, we both worked very, very well together. I think as as as users um seeing, you know, doctor and and and sneak work so so seamlessly and integrated a couple of things. I would love to see. Um, I think what we're gonna see more and more and this is one of the areas that I think, um you know, looking at the way sneak is going to be viewing security in general. We see a lot of components scanning a lot, a lot of people looking at a components can and seeing vulnerabilities in your components. Can I think what we need to, to to look more upon is consolidating a lot of the a lot of the data which we have in and around different scans. What I would love to see is perhaps, you know, if you're running something through doctors can how can you how can you view that data through through sneak perhaps how can we get that closer integration through the data that we that we see. So I would love to see a lot more of that occur, you know, within that relationship and these are kind of like, you know, we're getting to that at that stage where we see integration, it just various levels. So we have the integration where we have we are embedded but how can we make that better for say a sneak user who also comes to the sneak pages and wants to see that data through sneak. So I would love to see at that level uh more there where as I mentioned, we have we have some some additional support as well. So you can run doctors can from from Lenox as well. So I can see more and more of that support rolling out but but yeah, in terms of the future, that's where I would love to see us uh to grow more >>and I'll see in the landscape side on the industry side, um, security is going beyond the multiple control planes out there. Kubernetes surveillance service matches, etcetera, continues to be the horizontally scalable cloud world. I mean, and you got you mentioned the edge. So a lot more complexity to rein in and make easier. >>Yeah, I mean there's a lot more complexity, you know, from a security point of view, the technology is the ability to move quickly and react fast in production actually help security a lot because you know, being able to spin a container and make changes and and bring a container down. These things just weren't possible, you know, 10 years ago, 20 years ago. Pre that it's like it was it's insanely hard compared trying to trying to do that compared to just re spinning a container up. However, the issue I see from a security point of view, the concerns I see is more around a culture and an education point of view of we've got all this great tech and it's it's awesome but we need to do it correctly. So making sure that as you mentioned with making the right decision, what we want to make sure is that right decision is also the easy decision and the clear decision. So we just need to make sure that as we as we go down this journey and we're going down it fast and it's not gonna, I don't see it slowing down, we're going fast down that journey. How do we make, how do we prepare ourselves for that? We're already seeing, you know, miss configurations left, right and center in the news, I am roles as three buckets, etcetera. These are they're they're simpler fixes than we than we believe, right? We just need to identify them and and make those changes as needed. So we just need to make sure that that is in place as we go forward. But it's exciting times for sure. >>It's really exciting. And you got the scanning and right at the point of coding automation to help take that basic mis configuration, take that off the table. Not a lot of manual work, but ultimately get to that cloud scale cool stuff. >>Simon, thank you >>for coming on the cube dr khan coverage. Really appreciate your time. Drop some nice commentary there. Really appreciate it. Thank you. >>My pleasure. Thank you very much. >>Simon Maple Field C T. O. A sneak hot startup. Big partner with Docker Security, actually built in deVOPS, is now dead. Say cops. This is dr khan cube 2021 virtual coverage. I'm sean for your host. Thanks for watching. Mm.