>>Okay, welcome back everyone to the cubes coverage here in San Francisco, California of AWS summit, 2022. I'm John Farry host of the cube AWS summit in New York city. Coming up in the summer. We'll be there as well for live interviews there. Events are back and we're excited. I have a great guest here y'all you of CEO and co-founder and Juna security based outta Palo Alto. Great to have you coming on the queue. Appreciate it. Yeah. >>Thanks. >>Thanks for having, so tell us about what you guys are doing. You guys have a really cool cost of confidential computing. Take a minute to explain what the company does. >>Sure. So, uh, at high level confidential computing is the ability to take any workload, any piece of data, regardless of sensitive, it is and run it completely isolated, completely private, completely protected, essentially on any infrastructure, uh, and that enables organizations to take any, any workload and move it to UN you know, um, sensitive, potential sensitive locations, like the public cloud, where somebody else is managing your infrastructure. >>So basically the problem you solve is you provide security layer for workloads. >>Exactly. >>Exactly's also govern in security issues, but also just general hacking, >>Right? Oh, ex exactly. Essentially any, any organization having any type of sensitive information, think about, you know, financial services, think about healthcare, think about, you know, oil and gas that need to protect the data where they're gonna drill next. Any, any kind of organization that has sensitive information has that issue and needs to protect data in any environment they run in. >>So Amazon would be like, wait a minute. We're secure. What come on. >>Uh, actually AWS is, uh, is one of our partners and we we're actually building on top of, uh, a new technology that AWS, uh, built called, uh, nitro enclaves. And actually all the public clouds have built a technology like this. Uh, the reason why they've done this is to security and privacy are the number one. And number two reasons why people don't move more workloads to the public cloud. Mm-hmm <affirmative>. So what the public clouds have done is added this technology to be able to tell their customers one is we don't have any access to your data running on top of our infrastructure. And number two, be able to turn to the government and tell them, uh, during the case with the iPhone and, uh, the FBI or the FBI to apple asked him for data on the iPhone. Yeah. And apple said, we just can't, we don't have access to that data. This is exactly what the public clouds want to be able to do, turn to the government and tell them we just don't have access to our customer's data. >>Wow. That's gonna put a lot of pressure. So talk about the surface area of attacks. How has that changed? What do you guys, what's your role in that obviously this no perimeter anymore in the cloud, the security is dead. That's a huge issue. >>Yeah, of course. So, so I guess what we fit into this, as I mentioned, all the clouds added, uh, this technology, uh, what we fit in is very similar to what VMware did for virtualization, right? Virtualization was this extremely powerful technology that everybody knew was going to change the world. You wouldn't have the public cloud without virtualization. Uh, the problem was, it was very difficult to use very, very low level because it was a hardware technology. And then every, uh, vendor built a different technology. This is exactly the case now with confidential computing, every cloud added, uh, uh, a hardware level technology to go support this. But one it's very low level. It's very, very difficult to use. And every cloud added the different technology, which makes it even harder for organizations to go use. We added a softer stack exactly like VE VMware did for virtualization to make it super simple, to use and ubiquitous across the different clouds. >>How did you come up with the idea? What did this all come from? Were you scratching and inch and security? Did you have one of those things like, Hey, I can solve this problem. What's the origination story? Where did this all start? >>Yeah, it's actually, so I I've been in security for, you know, over 20 years now. Um, and I kept running into that same problem. Right. I, I was in the, I was actually in, um, unit 8,200, which is the really equivalent of the NSA. Uh, I was then, uh, in the private sector and I was, uh, a bunch of companies open DNS, Cisco, and, and I kept running into that same issue. And when you kind of peeled the layers of the onion of what the core security problem was, it always came back to how do you protect data while it's being used, which is essentially the core, the same sort of core problem, the confidential computing solves. Um, but there was never a solution. There was never a way to solve this. Uh, and, uh, above four years ago, my co-founder, uh, just finished his PhD at Stanford and he ran into, there's finally a way to do this. Finally, the CPU vendors have built something in, uh, the clouds are going to adopt this. This is going to allow you to one finally solve that huge problem that always existed. And, and number two, this allows you to kind of rearchitect security the right way, uh, because this has always been the core problem that people try to somehow mitigate never having a good solution. >>It's like putting a rapper around it, an envelope and saying secure. >>Exactly. So was this >>PhD working at Stanford in parallel to industry momentum at the same time Sarah Diply? Or was it kind of like, was he working with partners already in his program? >>Yeah, so he just, uh, this was something was happening and this is, uh, this has been going on for, well over a decade. It, it actually funny enough, it started with the, uh, with cell phones. I dunno if you ever thought, you know, what happens if you lose your phone, you have the biometric data, right? Your fingerprint or your face ID. Can somebody get that information out the phone if you lose it? And what the, the phone vendors have done is basically put techn, confidential computing technology to make sure that even if somebody gets physical access to your device, they're not going to be able to get access to that data. And what the, the evolution was is that the Intel AMD, the CPU vendors have realized, wait, this is a really, really great idea. Yeah, you should put it on the server side as well. >>And that started with Intel in 2015. So this has been an evolution, uh, and now essentially every, every one of the CPU vendors is now supporting this. You have Intel and R and AMD and video just announced, uh, their confidential, uh, uh, GPU solution, uh, all the clouds and I've adopted this. Uh, so my, my co-founder when he ran into this, this was as this was, uh, starting to, to happen. He got extremely excited, but he has noticed a big problem of everyone is coming up with different solutions. We're gonna need to build a layer, a software layer on top of this, uh, to, so >>You have, you have to get this to be de facto >>Exactly standard. >>Oh, how's that going? So Amazon's a partner, >>Amazon's a partner. Aw. Uh, Azure is a partner. Uh, we can run on top of essentially any, any one of the clouds out there >>They're enabling you to do that. Cuz they're they want to buy into security. >>Exactly. They want the benefit. Exactly. They want tell their customers, you can move anything to the cloud because we don't have any access to your data. This helps us, them essentially sell cloud >>A couple things around. Um, I want to ask about performance, but before I get to that, yep. It seems like this whole protective data thing has always been like a database thing. Not so much low level re resetting, if you will, it's almost a reset. It's not like just protect your data in the database. >>Oh yeah. Yes. It's different. Yes, exactly. It's funny because uh, you bring sort of the right exact right point. Really. You kind of think about where data can reside. There're essentially three locations. There's data at rest, which is essentially data in a database or file system. There's data in transit, which is data on the, you know, in the network. Yep. Uh, and then there's data use and the data and use piece is essentially when an application needs to process data, it has to decry it and load it completely in the clear, in memory in order to process it. Got it. And at that point, the data is not decade. This is why it's so hard for organizations to move data to the cloud or to run data and geographies where they're not, you know, they don't trust the government or don't trust the, the admins. >>So injecting some malware or vulnerability or attack in the workload while it's running is just another attack, vector. >>Exactly. Or just, or just stealing the data. If you, if you have access to the infrastructure, if you can run code, you can then just basically look in the memory and get all the data out of it. And, and to some extent, even the, the, the encryption keys you use for data, rest those keys, leaving the clear in memory. So even that hasn't been completely solved. Got it. Now that you have this component, you can finally solve, you know, solved our problem and protect the data regardless of where it resides. >>All right. So I gotta a performance question cause remember going, even back to the earlier encryption. Yeah. There's always overhead penalty. Yes. But cloud's a beautiful thing you can spend compute up and you're talking about now, the, the CPU vendors are kind of getting involved. >>Yes. Talk >>About the security, uh, how you mitigate that. Is it an issue? No issue. Why? Yeah, >>Actually, actually, uh, you talk about performance because I think this is a really, really great point. What's nice about this. Uh, and uh, this is why the, the, the, the sort of the benefit of the CPU vendors doing this performance has always essentially had two underlying issues. One is performance, as you mentioned. And the other one is ease of use. This is, this is sort of the, the piece we add to that. We make it super simple to use when you can take essentially any workload and run it securely on top of any, any one of these solutions and the performing thing, the, the heavy lifting is done by the hardware vendors themselves, which means there's a another, uh, chip next to the CPU that does all the heavy lifting encryption, which is very similar. I don't know if you remember the, uh, um, uh, the TLS, you know, the SL acceleration cards. Yeah. This was exactly the same thing. It was this, you know, chip outside the CPU. So it's not, uh, in the sort of the critical path that does all the heavy lifting. And this is what allowed, uh, TLS or HTB TTP HTTPS to become the default where you now protect every website. And this is sort of when security becomes transparent and there's no performance impact, like why, why would you use it for everything? >>It becomes a no brainer unless there's legacy baggage, right. >>In >>Dogma around use this approach, culture issue, or technical, right. Unwind those two, two things. So what's your a take on that? What's your react. Culture's easy. Just like, I think that's easy to fix. We want better security get on board or see you later. Exactly. Technical architecture could be an inhibitor. How do you see that is the blocker? How do you unwind that? How do you get that to >>Reset? So it's exactly the value that we bring to the table. We build a software stack to make it super simple. You don't need to, you know, you don't need to rewrite the application. You don't need to recompile, it's essentially security becoming a part of the infrastructure. You essentially have security as just a piece of the infrastructure that makes it super simple to get a no brainer. Yeah, exactly. The way, you know, TLS was it's. Yeah. We're a software vendor. >>All right. So how do I see it integrating with Amazon? It's gonna get into the chip level. They're enabling hooks for you. Exactly. That's how it works. >>So there's essentially the, uh, all the cloud vendors have enabled these technologies for Amazon it's yeah. It's essentially this hardware capability. We, we have access to it and we're a software layer on top of it to make it simple, similar to, again, what M VMware did for virtualization and what, um, some extent, this is what, uh, Microsoft has done for the CPU, what windows is right. Every time there's a new, really amazing hardware, hardware, uh, feature. You need a software sec on top of it to make it simple use. >>What's great about the cloud is, is that you kind of have that whole operating system mindset now being democratized across everything. Right. I mean, it's a systems thinking in software, right. With all the cap X of the cloud. Yes. And you're decoupled from it and you're riding on top of >>It. Exactly. >>It's an amazing opportunity as a co-founder or just if, if there was no cloud, how hard were this to be the two <laugh>, I mean, like almost impossible. Yep. So very cool. All right. Take a minute to explain what you guys are working on. How big is the company, what you guys are doing right now, you're hiring, you're looking for people funding, give a, give some, uh, give, give some, give a plug to the company. >>Sure. So, uh, we're, uh, we're a series B company, uh, lost, uh, raised 30 million from insight in the last round. Um, we're, uh, we're about 80 people right now. We're growing extremely aggressively. Um, mostly on the salsa and the cells go to market side just because of the demand that we're seeing in the market, but we're also growing on the engineering side. So again, if, uh, we're always happy to talk to >>Side about Palo Alto probably have remote teams, >>Uh, we're based in Palo Alto. So the, the, the, the sort of headquarters and most of the team is in Palo Alto, but yeah, we're very open to remote. We have now engineers in all across the us, and also outside the us as well, just because COVID made it sort of very easy to, to do >>That. Right. I mean, you got a good product, great idea, and a great opportunity. I mean, this is, you know, Dave LAN and I had at a VM world, I think it was like 2013. Now we're dating ourselves. <laugh> this is when we started covering AWS. Yep. He asked pat Gelsinger, it might have been 2015. Cause the CEO of VMware at the time. Yeah. Is security a Doover. Yep. And he's like, absolutely. And this is now happening. This is a security Mulligan, a redo over, this is what we need. Right. >>Exactly. And this is why, so, uh, we're part of a, uh, something called the confidential computing consortium, which essentially has all the large, all the, you know, the cloud vendors, the CPU vendors, VMware is a part of this as well. Basically the, this is sort of too big of a shift for these large organizations to ignore the, and uh, yeah. VMware is definitely going to have a, a part of >>This. Awesome. Well, congratulations. You guys are gonna probably be really huge or get bought out pretty quickly. <laugh> we're I think >>This, this is a huge, this is just a huge opportunity. We can become the VMware of security. So I think this is, you know, I'm hoping to stay independent. >>Yeah. Congratulations on a great venture. Love the idea. And again, every application should run this way. It's no, uh, if you can get that security built in yep. You gotta shield. Right. You wrap it up, probe it anywhere exactly made the best cloud >>Win. Exactly. Right. Exactly. >>And that's, what's gonna happen. That's >>That's >>Why I love the Silicon angle of Amazon Silicon play. Yes. As that Silicon gets better. >>Yes. >>It only helps this, these kinds of use cases. Right? >>Exactly. We, we, again, we, we leverage, we leverage these technologies and to some extent, this is, this is actually part of the, the value we talk to customers about, because this is sort of the cutting edge of technology and security. And this keeps evolving. As, as I mentioned in video, just announced their confidential GPS. We provide this layer on top of it where organizations don't have to go and kind of rebuild every application as this evolves and just use our people >>Who know me in the cube know I'm a Hawk when it comes to cybersecurity. I think the red line is people operating below the red line. And, and why should companies have to provision their own militia? Exactly. This is essentially the shield they can put up. Exactly. And not rely on the government who just know what they're doing. Exactly. >>So get exactly security should be easy. Should be, should be us everywhere. I >>Should you get a lot of banking customers, FinTech customers coming on board. Exactly. Right. Outta the gate. Yeah. Thanks for coming on the queue. Yeah. Appreciate. Thank you. Live coverage here. San Francisco, California. I'm John farrier with the cube. We'll be right back with more after this short break.