>>Welcome back to VMO 2022. We're in the home stretch. Now, Dave ante for Dave Nicholson, and we're excited to have drew Schlissel on he's the director of product marketing at wasabi, and he is joined by Dustin Albertson, the manager of cloud and application alliances, product, product management at Veeam software. Dustin, did I get that right? You got it right. All right. You're gonna explain all those little titles in a moment. So wasabi is a company cool name, but you may not know much about them drew. What does wasabi do? >>We do cloud storage, plain and simple. It is the one thing we do extremely well. It's S3 compatible, and it covers a broad range of use cases, right? Primarily we work with Veeam on backup and recovery, and >>We're gonna get into that. But when we, what there's a lot of people do cloud storage, a lot of people do object store. What makes you wasabi unique >>Simplicity, predictability performance security, right? Predictability. Let's talk about price, right? That's the thing that gets people's attention, right? Oh, sure. Okay. You can look at it. One of two ways. It's either one fit the price of all the hyperscalers, significant difference there, or right. For fundamentally the same price. You get five times more storage, which makes a huge difference, especially in the backup space. When you want to have a lot of backups, right. Folks would prefer to have months of backups as opposed to days or weeks. Right? >>How do you, how do you do that? Because, because there's, you know, maybe >>It sounds like magic, doesn't >>It? Yeah. Yeah. I mean, you know, look at us, we've all been around the block quite a few times and we know that the bits and the bites and the bolts are all basically the same. What are you doing to get that level of? >>I can't tell you >>Secret's secret. It's secret. >>Look, it, it doesn't have to be that expensive. Okay. Now granted, there's some things obviously we do that are proprietary and different from, >>Well, like stealing electricity from your neighbor or something. I mean, what, >>You just run a cord over a >>Absolutely that's one way to cut down on price. But because we are so focused on just the storage, right. And our founders, you know, the gentleman who founded Carbonite, no a thing or two about storage. Sure. Right. We have a very highly optimized stack, very efficient. You know, you guys know what raw to usable story is. Right? You've gone through that TCO analysis before, and we're highly efficient in how we use the raw storage. And we pass that price on to our customers. Right. We believe that a low price cloud storage, right? One tier always hot, always available. It gives our customers the ability to spend their money in other places. Right. >>Well, and, and there's a price umbrella that the public cloud guys have is kind of a gift that they've given you. Hey, look at Amazon's operating profits last quarter. It was 35%. Those are like Oracle operating margins. Not that I, we don't know what your operating margins are, but I I've followed David friend's career for a long, long time. He's got good nose for business. But so Dustin, when you, when you hear drew talk about the ability to retain that much data, what does that mean for Veeam customers? >>So the primary thing for Veeam customers is the ease of use. I would say, you know, the, the performance and things like that are all nice, right? They're, they're important. But primarily what I see is people say how easy it is to use and how easy it is to price. Now, the objective, you know, the alternative is you go to another cloud provider and you say, well, how much will this cost me per month? You really have to underst yes, you really have to understand object storage, how Veeam works, how we're moving data, all the API calls, all of that to really kind of correlate out a guesstimate of what your price would be per month. You know, with LASA it's, it's a flat fee it's per terabyte. You know what it is gonna be? That's it? There's no API charges. There's no egres. So the customers really love that. Ease of use this become one of the most popular endpoints for object storage for our customers. >>Imagine this, right? You go to best buy and you buy a refrigerator and you bring it home and you stock it with all your favorite drinks and snacks. Okay. You on game day, you go and you open the fridge and you hear a sound Bing. And it's your phone and it's your credit card company telling you that you've been charged a door opening fee. Okay. And then you grab a beer out of that fridge, Bing, Bing, and you hear another ring and now you're getting a beer extraction fee. Okay. Now I want to be fair to, you know, all the sponsors here, but okay. With wasabi, you can open that door. You could stand there. You can air condition, the whole house. You can take a beer out and put a beer back or whatever your favorite beverage is. And you're not gonna hear that noise. Okay. Very straightforward. Like in, in geometry class, right? The slope of a line Y equals MX plus B B equals zero. Okay. Well, >>Whoa. Well, you had me at free beer. You didn't, >>You don't, but you understand why? >>Why would you, you don't need to go see >>To open your fridge and take out a beverage, take out a snack. Okay. That's the predictable part of wasabi. That's what's resonating so strongly with folks where everything else is in this world. Unpredictable. >>So ease, simplicity. Maybe the answer to that is, well, there's all this other stuff in the cloud. I can just, it's convenient for me. It's right there. So how do you address that convenience factor? All these other services, you know, that I can get streaming and machine learning and all that other great stuff. How do you address that? >>Sometimes all you need is storage. Okay. That no, it that's yet put, okay. That's beauty of wasabi. We're not trying to be everything to everyone. We're trying to be one thing executed very well for a, a specific set of users and use cases. >>I may be a little objective here, but I, I, you know, I've grown up with you guys, right? You, you, you were one of the first partners that I started working with and, and, you know, I've seen you kind of grow, but one of the things I think that you've done a real good job at is, is like you say, sticking to your, your lanes, you know, just going after use cases that just need data. Right. I don't need to get into the AI or the analytics or all of this. We just do this and do it well. And, and people have resonated with that. Right? Yeah. >>So big topic here of course is ransomware. Yeah. 3, 2 11, 0. What is that? What are the threes? The twos, the ones >>That's you, you gotta explain that one. Okay. >>So forever we had the 3, 2, 1 rule, right? Like three copies of data, two different, two different copies, two different media types. Yeah. One offsite. And then one is, is testing. And then zero now is, is validation. BA basically reuse that data. Make sure that you're testing it because if you're not, if you're following through two one, and you're not actually testing your data, is it really good? You don't know. You're just, you may have bad copies spread out all over the place. So one of the things where wasabi shines is is that they don't have these E risk charges. They don't have these API charges. So you can test that data. You can, after you send a backup up there, restore it somewhere else and validate that it works and then get rid of it. And it's still sitting up there in BAA. >>So you're not trying to balance your activities and your operational requirements with your, with your bill. Correct. You're not getting yelled at, by the, the controller at the end of the month. >>You're unconstrained. Yeah. Right. And I think also imutability comes into play. Correct. As well. >>Talk about >>That. Right. So, you know, we heard this morning in the keynote, right? That backup data sets are, you know, one of the main attack vectors, right. For cyber criminals. And it makes sense, right. They take down your primary systems and they control your backup systems. They've got you. You have no choice, but to pay that ransom. Okay. So mutability, that means that your backups are untouchable, your root user, your admins, the folks at wasabi, the folks at Veeam, nobody can alter that data period. End of story. Okay. That saves you from yourself that saves you from the hackers, right? I mean the most disturbing story I've read about cyber warfare right now is that people are getting bribe offers from these cyber gangs. And they're just, you know, for a couple of Bitcoin handing over the keys to the kingdom with imutability, you're actually safe from that scenario. >>So that's a service, correct? >>No, it's a feature. >>Okay. So can I turn it off? >>Yeah. You don't have to use it. >>No. Can I, after I've, after I've turned it on, can I turn it off? >>Oh, it's up to you. I mean, why don't you talk about >>That? Yeah. Yeah. So it's, it's an API. So if let's say you send some backups up there today and you set it for two weeks and you decide today. Oh, I made a mistake. I wanna turn it off. You can't turn it off. Yeah. >>Okay. So as long as you set that policy, it's, it's a big warning, right? You can't undo this. Correct. Okay. So even if I come, come to jump to the admin with a bunch of Bitcoin yep. He or she can't undo, right? >>Nope. That's right. And you can set it for two weeks, two months, two years. Right. You can use it to secure your backups. Yep. Right. You can also use that same feature in compliance situations. Right. Regulatory environments, where you've gotta retain customer data for, you know, 5, 7, 10 years. Right. By using that imutability feature, you guarantee the integrity of that data for whatever period you set. >>And it's a feature it's not a paid for service. Is that right? >>It is included as part of the service. >>Okay. So I don't >>Free beer and free meat. >>I think I'm correct that some, some competitors you're paying for that service. So if you turn it off, there's a, if you don't stop paying, there's a, there's a theory. They could turn it off on you. They will warn you. >>Sure. But >>That says to me that somebody could be tempted by a few Bitcoin. >>That's not a mutable. Well's >>Notable. I agree. Yeah. Yeah. Yeah. >>Well, and, and there is a charge to use it in other places because it's an API request. Right. It's an action. It's opening the fridge. >>It's like texting. Yes. Maybe a charge. >>Yeah. I remember. I remember those days. Was it 10 cents? A 10 cents a message or something Telegraph. >>Yeah. >>Yeah. >>Yeah. You still get those messages. Right? Text, text fees may apply. I'm like really? Okay. So tell me more about, so you got me. I'm sold. Okay. I've I've David friends got good job. Got cred, got credibility. Okay. But I have some other questions. Like where's my data. You guys running your own data centers. What's your global footprint. How do you deal with data sovereignty? All that stuff. >>So right now, oh boy. Now I'm on the spot. I wanna say 11 locations around the world. It's our gear. We're running it in concert with folks who are helping us host that system. Right. But we have complete control of course, over our systems. We're everywhere. Right? Just open, let's see. Toronto Frankfurt, Paris, London, Sydney just spun up in the last week. We've got Singapore coming online. I think in the next two weeks. Two >>In Japan. >>Yep. Two in Japan, multiple locations in the United States. So in terms of sovereignty, right, as long as folks are keeping it within, you know, their, their physical boundaries, not a problem. And if folks want to use, you know, other locations in other countries, great. We can support that as well. >>So you got momentum as a business. I mean, that's pretty clear. Yeah. Just from the discussions I've had with, with folks like David, and obviously you you're excited about this, where's it coming from? Is it really that, that price factor that's driving people to you? Is it Dustin said simplicity. I mean, where are you seeing the momentum geographies? Where is it? Where's the action. >>I I'll say, you know, from my point of view, it's, it's been a combination of all that, right? It, it's simple. It's easy to use a, like a user can, any user who's not cloud friendly, right. Can log in and create one. It's a simple portal to create a bucket and then start sending stuff off site. But also they've, they've kind of, they reminded me of a younger Veeam, like when they first started, because they went after the channel and they went and started these partner programs and, and MSP programs and things like that that have been really successful as far as one of the key markets is MSPs. Right? Because they, you know, want a cheap place to put this data. They don't wanna have to buy appliances. They don't wanna have to go to AWS and things like that. So this has been really appealing to >>Them. You know, it's interesting. So I have a, we have a partnership with a data company down in New York called enterprise technology research. We write a breaking analysis every week and we use a lot of their data. One of the things that popped up recently, maybe a year ago, OpenStack I'm like OpenStack. So we dug in like where's OpenStack and what it was was MSPs didn't want pay the VTax. Right. So they were rolling their own with, with open source and open stack. It was red hat services, blah, blah, blah. But it sounds like a similar dynamic, especially with the MSPs. >>I, so I think we've, I, I hate to use the, the metaphor, but I will. Right. There's a perfect storm happening, right. Especially in the last, what, two years. All right. The cloud has been gaining traction, but we've been around long enough to see the pendulum swinging. Right. Some folks went crazy for the cloud and then they got their bill and then they went crazy to get back out of the cloud. But now, you know, with distributed workforces, with the, you know, the, the constant attacks on their, their on-prem systems, right. The growth in cloud across the board has been phenomenal. I know you're a market watcher. Right. I know you guys are keeping close eyes. I saw your recent analysis on the cybersecurity firms. Right. It continues to grow. There's no question about it. We're we're on that wave. Right. And I think we've, you know, we're not, we're, we're, I don't know if it's the long board or the short little snappy board. Yes. We actually identify and, and, and went after the opportunity to partner with Veeam very early on, because it's the perfect work case work, work load. >>How long can you sustain that? And still resist the temptation to come out with some new shiny object to distract people? >>I >>Mean, what, what, what does that, what does that look like in terms of, as you look out in this laser focused yeah. Addressable market that you're going after now. >>So, you know, the best part about being here this week is having great conversations and, and talking to folks about what they're seeing in the marketplace and the different verticals. I don't think we've even scratched the surface of any of the verticals that we are working in today. Right. First and foremost, when it comes to backup and recovery, there's so much more opportunity with Veeam, right? Whether it's healthcare, manufacturing, logistics, analytics, backup of IML, you know, analysis, I think it's almost limitless, right. Data's growing what, 40, 80% year, over year, depending on who you ask. Right. Then the other things that we do, which maybe folks don't even know about, we have a burgeoning business in video surveillance, right. We're working with all the top partners in that sector. And the takeup is phenomenal because they are tweaking their technology to maintain a relatively small cash, right. OnPrem or in the central office. And then they're just kind of, you know, tearing that off to the cloud to have essentially a bottomless backup or archive of that footage. And they can do it at 4k. Here's the best part, right. When AK comes out, guess what, you know, that data set doubles in size. >>Right. But that's right in your zone. That's not stepping out that that's not stepping after that's that's classic leveraging. Good >>Answer. In other words. Yeah. Yeah. Thank you. >>I mean, if >>You're, if you're, if you're hitting singles and doubles all day long, right. Do you have to switch to be a power hitter and go for the fences and drop your batting average down, but hope that your slugging percentage goes up. I think you keep hitting singles doubles, you know, in triples, >>A lot of people on Sandhill road or, you know, at the bar at the Rosewood would disagree with you. Wow. And so I, I appreciate the discipline. >>Yeah. And it's true. And, and as we know, the industry is littered with a lot of those names that just didn't didn't make it >>Let's stay positive, you know? >>Okay. No he's saying yeah, no, no. A lot of guys at sand hill road would say, no, you gotta go for it. Yeah. You gotta, you gotta forget these singles. We want, >>Yeah. We need home runs gotta be >>Shiny. Well, I mean, look at Vema as a, as a, as an example right. Of a disciplined approach. Right. Exactly. To, to a space that they have steadily grown. I mean, congratulations. Right. You guys have been identified by IDC, right. Is essentially, you know, co number ones. And I expect that to be the number one in the market. Right. I think, you know, David friend clearly has provided excellent guidance, right. To steer the company that way. And I'm just really happy >>To be about that. Oh. And the Tam is data. Right. And you're, you're just another node on the data universe. Right. Which is, that's what you want. You want, you don't necessarily wanna move it around. Yeah. If you don't have to. >>It is interesting though. I mean, we, we are seeing more and more analysts identifying with Sabi as like the fourth player. Yeah. Which is pretty cool. Right. And I also heard it from some good sources this week that let's say one of the hyperscalers has, you know, started to yeah. Have conversations about us. Let's just >>Leave it. That's good. It means you're bothering people. Yeah. Said, all right, guys, we gotta go. Thanks so much for coming on the queue. Thank you. Great to have you. That was easy. Thank you. Appreciate it. Very welcome. All right. Keep it right there. We'll be back to wrap up day one from VMO in 2022, right back.

>>Okay, welcome back everyone. To the cubes coverage here, coop con cloud native con 2021 in person. The Cuba's here. I'm John farrier hosted the queue with Dave Nicholson, my cohost and cloud analyst, man. It's great to be back, uh, in person. We also have a hybrid event. We've got two great guests here, the founders of deep fence, sham, Krista Swami, C co-founder and CTO, and said deep line founder. It's great to have you on. This is a super important topic. As cloud native is crossed over. Everyone's talking about it mainstream, blah, blah, blah. But security is driving the agenda. You guys are in the middle of it. Cutting edge approach and news >>Like, like we were talking about John, we had operating at the intersection of the awesome desk, right? Open source security and cloud cloud native, essentially. Absolutely. And today's a super exciting day for us. We're launching something called track pepper, Apache V2, completely open source. Think of it as an x-ray or MRI scan for your cloud scan, you know, visualize this cloud at scale, all of the modalities, essentially, we look at cloud as a continuum. It's not a single modality it's containers. It's communities, it's William to settle we'll list all of them. Co-exist side by side. That's how we look at it and threat map. It essentially allows you to visualize all of this in real time, think of fed map, but as something that you, that, that takes over the Baton from the CIS unit, when the lift shift left gets over, that's when the threat pepper comes into picture. So yeah, super excited. >>It's like really gives that developer and the teams ops teams visibility into kind of health statistics of the cloud. But also, as you said, it's not just software mechanisms. The cloud is evolving, new sources being turned on and off. No one even knows what's going on. Sometimes this is a really hidden problem, right? Yeah, >>Absolutely. The basic problem is, I mean, I would just talk to, you know, a gentleman 70 of this morning is two 70 billion. Plus public cloud spent John two 70 billion plus even 3 billion, 30 billion they're saying right. Uh, projected revenue. And there is not even a single community tool to visualize all the clouds and all the cloud modalities at scale, let's start there. That's what we sort of decided, you know what, let's start with utilizing everything else there. And then look for known badness, which is the vulnerabilities, which still remains the biggest attack vector. >>Sure. Tell us about some of the hood. How does this all work cloud scale? Is it a cloud service managed service it's code? Take us out, take us through product. Absolutely. >>So, so, but before that, right, there's one small point that Sandeep mentioned. And Richard, I'd like to elaborate here, right? He spoke about the whole cloud spending such a large volume, right? If you look at the way people look at applications today, it's not just single clone anymore. It's multicloud multi regions across diverse plants, right? What does the solution to look at what my interests are to this point? That is a missing piece here. And that is what we're trying to tackle. And that is where we are going as open source. Coming back to your question, right? How does this whole thing work? So we have a completely on-prem model, right? Where customers can download the code today, install it. It can bill, we give binary stool and Shockley just as the exciting announcement that came out today, you're going to see somewhat exciting entrepreneurs. That's going to make a lot more easy for folks out there all day. Yeah, that's fine. >>So how does this, how does this all fit into security as a micro service and your, your vision of that? >>Absolutely. Absolutely. You know, I'll tell you, this has to do with the one of the continual conferences I would sort of when I was trying to get an idea, trying to shape the whole vision really? Right. Hey, what about syncretism? Microservice? I would go and ask people. They mentioned that sounds, that makes sense. Everything is becoming a microservice. Really. So what you're saying is you're going to deploy one more microservice, just like I deploy all of my other microservices. And that's going to look after my microservices. That compute back makes logical sense, essentially. That was the Genesis of that terminology. So defense essentially is deployed as a microservice. You go to scale, it's deployed, operated just like you to your microservices. So no code changes, no other tool chain changes. It just is yet another microservice. That's going to look after you talk about >>The, >>So there's one point I would like to add here, which is something very interesting, right? The whole concept of microservice came from, if you remember the memo from Jeff Bezos, that everybody's going to go, Microsoft would be fired. That gave rise to a very conventional unconditionally of thinking about their applications. Our deep friends, we believe that security should be. Now. You should bring the same unconventional way of thinking to security. Your security is all bottom up. No, it has to start popping up. So your applications on microservice, your security should also be a micro. >>So you need a microservice for a microservice security for the security. You're starting to get into a paradigm shift where you starting to see the API economy that bayzos and Amazon philosophy and their approach go Beanstream. So when I got to ask you, because this is a trend we've been watching and reporting on the actual application development processes, changing from the old school, you know, life cycle, software defined life cycle to now you've got machine learning and bots. You have AI. Now you have people are building apps differently. And the speed of which they want to code is high. And then other teams are slowing them down. So I've heard security teams just screw people over a couple of days. Oh my God, I can wait five days. No, it used to be five weeks. Now it's five days. They think that's progress. They want five minutes, the developers in real time. So this is a real deal optimum. >>Well, you know what? Shift left was a good thing. Instill a good thing. It helps you sort of figure out the issues early on in the development life cycle, essentially. Right? And so you started weaving in security early on and it stays with you. The problem is we are hydrating. So frequently you end up with a few hundred vulnerabilities every time you scan oftentimes few thousand and then you go to runtime and you can't really fix all these thousand one. You know? So this is where, so there is a little bit of a gap there. If you're saying, if look at the CIC cycle, the in financial cycle that they show you, right. You've got the far left, which is where you have the SAS tools, snake and all of that. And then you've got the center where, which is where you hand off this to ops. >>And then on the right side, you've got tech ops defense essentially starts in the middle and says, look, I know you've had thousand one abilities. Okay. But at run time, I see only one of those packages is loaded in memory. And only that is getting traffic. You go and fix that one because that's going to heart. You see what I'm saying? So that gap is what we're doing. So you start with the left, we come in in the middle and stay with you throughout, you know, till the whole, uh, she asks me. Yeah, well that >>Th that, that touches on a subject. What are the, what are the changes that we're seeing? What are the new threats that are associated with containerization and kind of coupled with that, look back on traditional security methods and how are our traditional security methods failing us with those new requirements that come out of the microservices and containerized world. And so, >>So having, having been at FireEye, I'll tell you I've worked on their windows products and Juniper, >>And very, very deeply involved in. >>And in fact, you know what I mean, at the company, we even sold a product to Palo Alto. So having been around the space, really, I think it's, it's, it's a, it's a foregone conclusion to say that attackers have become more sophisticated. Of course they have. Yeah. It's not a single attack vector, which gets you down anymore. It's not a script getting somewhere shooting who just sending one malicious HTP request exploiting, no, these are multi-vector multi-stage attacks. They, they evolve over time in space, you know? And then what happens is I could have shot a revolving with time and space, one notable cause of piling up. Right? And on the other side, you've got the infrastructure, which is getting fragmented. What I mean by fragmented is it's not one data center where everything would look and feel and smell similar it's containers and tuberosities and several lessons. All of that stuff is hackable, right? So you've got that big shift happening there. You've got attackers, how do you build visibility? So, in fact, initially we used to, we would go and speak with, uh, DevSecOps practitioner say, Hey, what is the coalition? Is it that you don't have enough scanners to scan? Is it that at runtime? What is the main problem? It's the lack of visibility, lack of observability throughout the life cycle, as well as through outage, it was an issue with allegation. >>And the fact that the attackers know that too, they're exploiting the fact that they can't see they're blind. And it's like, you know what? Trying to land a plane that flew yesterday and you think it's landing tomorrow. It's all like lagging. Right? Exactly. So I got to ask you, because this has comes up a lot, because remember when we're in our 11th season with the cube, and I remember conversations going back to 2010, a cloud's not secure. You know, this is before everyone realized shit, the club's better than on premises if you have it. Right. So a trend is emerged. I want to get your thoughts on this. What percentage of the hacks are because the attackers are lazier than the more sophisticated ones, because you see two buckets I'm going to get, I'm going to work hard to get this, or I'm going to go for the easy low-hanging fruit. Most people have just a setup that's just low hanging fruit for the hackers versus some sort of complex or thought through programmatic cloud system, because now is actually better if you do it. Right. So the more sophisticated the environment, the harder it is for the hackers, AK Bob wire, whatever you wanna call it, what level do we cross over? >>When does it go from the script periods to the, the, >>Katie's kind of like, okay, I want to go get the S3 bucket or whatever. There's like levels of like laziness. Yeah. Okay. I, yeah. Versus I'm really going to orchestrate Spearfish social engineer, the more sophisticated economy driven ones. Yeah. >>I think, you know what, this attackers, the hacks aren't being conducted the way they worked in the 10, five years ago, isn't saying that they been outsourced, there are sophisticated teams for building exploiters. This is the whole industry up there. Even the nation, it's an economy really. Right. So, um, the known badness or the known attacks, I think we have had tools. We have had their own tools, signature based tools, which would know, look for certain payloads and say, this is that I know it. Right. You get the stuff really starts sort of, uh, getting out of control when you have so many sort of different modalities running side by side. So much, so much moving attack surfaces, they will evolve. And you never know that you've scanned enough because you never happened because we just pushed the code. >>Yeah. So we've been covering the iron debt. Kim retired general, Keith Alexander, his company. They have this iron dome concept where there's more collective sharing. Um, how do you see that trend? Because I can almost imagine that the open-source man is going to love what you guys got. You're going to probably feed on it, like it's nobody's business, but then you start thinking, okay, we're going to be open. And you have a platform approach, not so much a tool based approach. So just give me tools. We all know that when does it, we cross over to the Nirvana of like real security sharing. Real-time telemetry data. >>And I want to answer this in two parts. The first part is really a lot of this wisdom is only in the community. It's a tribal knowledge. It's their informal feeds in from get up tickets. And you know, a lot of these things, what we're really doing with threat map, but as we are consolidating that and giving it out as a sort of platform that you can use, I like to go for free. This is the part you will never go to monetize this. And we are certain about disaster. What we are monetizing instead is you have, like I said, the x-ray or MRI scan of the cloud, which tells you what the pain points are. This is feel free. This is public collective good. This is a Patrick reader. This is for free. It's shocking. >>I took this long to get to that point, by the way, in this discussion. >>Yeah, >>This is this timing's perfect. >>Security is collective good. Right? And if you're doing open source, community-based, you know, programs like this is for the collector group. What we do look, this whole other set map is going to be open source. We going to make it a platform and our commercial version, which is called fetch Stryker, which is where we have our core IP, which is basically think about this way, right? If you figured out all the pain points and using tech map, or this was a free, and now you wanted the remedy for that pain feed to target a defense, we targeted quarantining of those statin workloads and all that stuff. And that's what our IP is. What we really do there is we said, look, you figured out the attack surface using tech fabric. Now I'm going to use threat Stryker to protect their attacks and stress >>Free. Not free to, or is that going to be Fort bang? >>Oh, that's for, okay. >>That's awesome. So you bring the goodness to the party, the goods to the party, again, share that collective, see where that goes. And the Stryker on top is how you guys monetize. >>And that's where we do some uniquely normal things. I would want to talk about that. If, if, if, if you know public probably for 30 seconds or so unique things we do in industry, which is basically being able to monitor what comes in, what goes out and what changes across time and space, because look, most of the modern attacks evolve over time and space, right? So you go to be able to see things like this. Here's a party structure, which has a vulnerability threats. Mapper told you that to strike. And what it does is it tells you a bunch of stress has a vulnerable again, know that somebody is sending a Melissa's HTP request, which has a malicious payload. And you know what, tomorrow there's a file system change. And there is outbound connection going to some funny place. That is the part that we're wanting this. >>Yeah. And you give away the tool to identify the threats and sell the hammer. >>That's giving you protection. >>Yeah. Yeah. Awesome. I love you guys love this product. I love how you're doing it. I got to ask you to define what is security as a microservice. >>So security is a microservice is a deployment modality for us. So defense, what defense has is one console. So defense is currently self posted by the customers within the infrastructure going forward. We'll also be launching a SAS version, the cloud version of it. But what happens as part of this deployment is they're running the management console, which is the gooey, and then a tiny sensor, which is collecting telemetric that is deployed as a microservice is what I'm saying. So you've got 10 containers running defenses level of container. That's, that's an eight or the Microsoft risk. And it utilizes, uh, EDP F you know, for tracing and all that stuff. Yeah. >>Awesome. Well, I think this is the beginning of a shift in the industry. You start to see dev ops and cloud native technologies become the operating model, not just dev dev ops are now in play and infrastructure as code, which is the ethos of a cloud generation is security is code. That's true. That's what you guys are doing. Thanks for coming on. Really appreciate it. Absolutely breaking news here in the queue, obviously great stuff. Open source continues to grow and win in the new model. Collaboration is the cube bringing you all the cover day one, the three days. I'm Jennifer, your host with Dave Nicholson. Thanks for watching.

>> Announcer: Live from Las Vegas. It's theCube, covering NAB 2017. Brought to you by HGST. (techno music) >> Welcome back to NAB, live from Las Vegas. I'm Lisa Martin with theCube. Join me in welcoming our next guest, Rich Welsh CEO of Sundog Media Toolkit. Hey Rich welcome to theCube. >> Hi, thank you for having me. >> Great to have you. So, first and foremost, now that I got all my tongue twitches out of the way, I have to ask you, what is a sundog? >> A sundog is actually a weather affect. It's an optical illusion caused by ice crystals in cirrus clouds. And the crystals are hexagonal and they diffract the light and you get these two, they're called mock suns, or parhelians, and the aboriginal word for that is a sundog. And so, that's where that comes from. And because we're in the cloud and we're like hexagons, we have a hexagonal user inter-face in our system. So we thought this was a perfect name for the company. >> Very unique. So tell us a little bit more. Sundog is a cloud-native solution for post-production in the cloud. >> Yes. >> You were founded in 2013. Give us a little bit more of an understanding of what you're doing for post-production in the cloud. >> Okay, so the system is built around running the kind of processes that require a lot of heavy-lifting and need to scale, such as very complex image manipulation processes, restoration, format conversions, working with uncompressed content, high-dynamic range, 4K, high frame rate. These are things that become much easier in a cloud environment and you scale up and down with the workload, and how peaky demand of a production. Obviously productions come along, they do a load of work and then they shut down again. So it's really built around that kind of ability to scale in a very peaky environment. >> So given that, you mentioned 4K. There was the live stream from The International Space Station today via 4K here to Las Vegas, amazing. 4K, HG, UHG, AK, massive opportunities, generating massive content that requires agility, speed, et cetera, et cetera. Talk to us about really what the genesis was for Sundog. What opportunity did you see in the market to create this company? >> So my background is operations in post-production distribution. I worked for Dolby and then Technicolor, and while I was doing that work, I found that there was often issues again with the kind of workloads where the formats were constantly increasing, I mean, we see that now, more formats than ever in terms of not just the things people might think of in terms of downstream tablets, mobile, and so on, but even in the cinema, we have massive amounts of different picture formats, sound formats, and so on. And it makes that whole content creation process so much more complex. We felt, Chris Ralph, who is my business partner and the co-founder of Sundog, and we'd worked together in that environment, but we always had machines in a machine room in the basement. And that really was a big limiting factor to what you could do and how quickly you could adapt to new formats and new requirements for the customers, and just the workflows they may want to suddenly adopt. So we felt that building something in the cloud gave us a lot of flexibility to be able to adapt to those different workflows, to new formats very quickly because you don't worry so much about the actual difficulty of doing the processing, you're not buying boxes anymore, so speed of processing becomes a function of how much of the cloud you want to use. So it's very simple to be able to go well, if for a 4K show we have way more compute power just to keep us going at the same speed as we would have for an HD, when then as we move into things like AK, high-dynamic range, high frame rate, these things are all coming along. You can just adapt more or less instantaneously to those things as they happen without having the burden of capital expenditure and limitations of whatever you already have installed. >> So give us an idea, you mentioned cinema and I know that you work with Hollywood-level cinema organizations. You talked about the speed, the flexibility, the agility, that they get. Walk us through an example of a film studio. What's the transition like for them moving post-production to the cloud? Is it a straightforward process, multiple steps involved? >> No, there are definitely multiple steps involved. I wouldn't say it's straightforward. It's maybe not quite as difficult as people would think, but there are a lot of factors that you need to consider when you're moving to the cloud. I mean, the first obvious one is you have to move the data in. So traditionally, a broadband infrastructure is going to be something that you have to invest in over a fairly long period of time to get good cost-effective bandwidth when you're moving uncompressed data and particularly if you're now moving up and down to the cloud, but we're seeing telecoms providers moving to much more flexible business models basically. So they're installing very high bandwidth fiber, but then you have the actual amount of data that you want to move on-demand. These kind of models are enabling people to move their post-production to the cloud. And the next thing, obviously, is security. People do have concerns about security. But with that said, actually the really big cloud providers have worked very hard to lock down that element. And in fact, there are many other industries whose security requirements are very stringent. You know, military applications, pharmaceuticals, banking, oil and gas. You can imagine all these very high-value industries that require really good security. And the big public clouds are geared towards that, so actually, you can have a lot of confidence as a studio or a broadcaster that if you implement it correctly, you can have really good, I would argue better than facility security, in a cloud environment, because they're actually dealing with stuff that cannot be lost. >> Right. We were actually, theCube, just at the Amazon Web Services Summit in San Francisco last week, and that was kind of a recurring theme that the security concerns really have been quite mitigated in the public cloud. Give us an idea in terms of maybe reducing the time from shot to post-production to actually showing a cinema in the theaters. How much reduction can a cinema, or film studio expect by moving to the cloud? >> Well, I mean, you can get incredible amounts of reduction because now if you can scale to that workload, let's say a big international release feature film might have three, 400 versions that will go out to cinemas, those versions in their current kind of paradigm have to be made manually in boxes, and with operators and then they have to be watched and qualified to make sure they're going to work, and then they get shipped to the theater. If you imagine moving that workflow wholesale to the cloud and we have done that work with some of the studios, now if you can get all of the elements together up front instead of having several weeks of work to get that out of the door and into theaters, you can literally do it in hours. There's no real limitation to the amount of compute resource that you would use in that scenario, certainly not going to trouble a really big data provider like Amazon, AWS. So you can get the assets out very quickly, but then you're actually able to leverage other features of the cloud such as content delivery networks to push those files to the cinemas. So in a real like joined up workflow in that way, I mean, we're not doing all of those things yet, but we will get there I'm absolutely certain and these things can take the release cycle from weeks down to days or hours. >> So dramatic, dramatic savings. Talk to us about, before we talk about the underlying infrastructure of Sundog, walk us through where Sundog is in that entire production pipeline. >> Okay, well actually Sundog's quite a broad platform in terms of the feature set, so we find the systems used by different productions at various different stages and that can be upfront in terms of dailies, and visual effects approvals, it can be right back at the distribution end when you're making all your foreign language versions, dubbed subtitles, and so on. And then we have a lot of processes which would typically take place in the middle of the post-production phase with things like image clean-up, de-noisers, we have super resolution converters, and actually a lot of tools that aren't available in hardware, simply because it's been very difficult to get a hardware platform that could reasonably process those elements in any amount of time. Again, we're finding that the cloud is becoming an environment for productizing those really complex algorithms and image processing techniques that just have not been available to creatives up till now. >> So with the customer journey, this transition that we talked about, what does, under the hood of Sundog in the cloud, compute, storage, networking, tell us about this ecosystem? >> So we took the approach from the start that we didn't want to deal with the storage element, that was for two reasons. The one is that customers really want to control their content themselves. So we felt if we could simply point the system to their storage, then that would be a much easier way for them to have to confidence that they know where their assets are and they're in control of them. So we work in a hybrid setup where you can have your assets stored anywhere you want. In a cloud, it will have to be a cloud environment, and then our system authenticates to it. Now the system itself is in Amazon, so all the compute, and data-base resource, and then all the kind of dynamic features around automation and so on, are built on the Amazon AWS platform, but the data may exist elsewhere so it might be in Amazon, it might be in Amazon S3 storage, but it could equally be somewhere else in the world in a different data center, it be on-prem in a cloud store that you've built yourself. So our architecture really is to provision and orchestrate that resource and scale, to provide the tools, so we have all these workflows with different manufacturers tools in there that you can call on-demand. But then when it comes to actually processing it, the data starts and finishes where you want it to go and gives you complete control. So it's quite a different architecture to a lot of solutions that are currently out there where you really have a box in the cloud with the storage attached to the box, and that's kind of it. >> Well not only do you have a very unique name with a great meaning, but you also seem to have quite differentiated technology. We thank you so much for stopping by theCube, we wish you the best of luck with Sundog, and have a great rest of your day three at NAB. >> Thank you very much. >> We want to thank you for watching. Again we are live at NAB in Las Vegas. I'm Lisa Martin, stick around we'll be right back. (techno music)