(gentle music) >> Good morning, fellow cloud nerds, and welcome back to day four of AWS re:Invent. We are here in fabulous Las Vegas, Nevada. I'm joined by my cohost Paul Gillin. I'm Savannah Peterson. We're on theCUBE. Paul, how you doing? You doing well? >> We're staggering to the conclusion. >> (laughing) It's almost the end then. >> And I say that only talking about my feet. This event is still going strong. The great keynote this morning by Werner Vogels about system architecture and really teaching 70,000 people how to design systems. AWS really taking advantage of this event to educate its customer base and- >> So much education here. >> Yeah, and that was a fantastic sort of cap to the keynotes we've seen this week. >> Yeah, I'm impressed Paul, our first AWS re:Invent. I think we're doing pretty good all things considered. >> Well, we're still alive. >> And our next guest actually looks like he's been sleeping this week, which is remarkable. Please welcome Ayal to the show. Ayal, how you doing today? >> I'm good, I'm good. Thank you for having me. >> It's our pleasure. You're with Anjuna. >> Yes. >> Just in case the audience isn't familiar, what's Anjuna? >> Anjuna is an enterprise security company. We focus in the space of confidential computing. And essentially we enable people to run anything they want in any environment with complete security and privacy. >> Which is a top priority for pretty much every single person here. >> Ayal: That is true. >> Now, confidential computing, I keep hearing that term. >> Yeah, let's go there. >> Is it, I mean, is there a trademark associated with it? Is there a certification? Is the concept or is it actually a set of principles and frameworks? >> Savannah: Give us the scoop. >> Yeah, so confidential computing is essentially a set of technologies that were added to the hardware itself, to the CPU, and now to GPUs by the hardware vendors. So Intel, AMD, Arm, Nvidia AWS with their own hardware solution for this. And essentially what it allows you to do is to run workloads on top of the CPU and the GPU in a way that even if somebody gets full access to the infrastructure, you know, root access, physical access, they're not going to have any access to the data and the code running on top of it. And as you can imagine in cloud environments, this is extremely, extremely (indistinct). >> And this done through encryption? >> It involves encryption. If you go one step deeper, it involves protecting the data while it's running, data and memory, when the application is processing it. Which is always been the missing piece in terms of where you protect data. >> So I got excited when I looked at the show notes because you are serving some of the most notoriously security strict customers in the market. Can you tell us about the Israeli Ministry of Defense? >> Sure. So essentially what we do with the Israel Ministry of Defense and other customers, especially on the on the government side, one of the challenges government has is that they have to, if they want security and privacy in the cloud, they have to use something like a gov cloud. And sometimes that makes sense, but sometimes either the gov cloud is not ready because of legal battles or just it takes time to set it up. In some countries, it's just not going to make financial sense for the clouds to create a gov cloud. So what we do is we enable them to run in the commercial cloud with the security and privacy of a gov cloud. >> Was that, I can imagine, so you took them to the public cloud, correct? >> Ayal: Yes. >> Was that a challenging process? When I think of national security, I can imagine a business transformation like that would be a little nerve-wracking. >> Oh, definitely. It was a long process and they went like, "This is probably one of the best security experts on the planet." And they went extremely deep in making sure that this aligns with what they would be able to do to actually move sensitive data to the commercial cloud. Which, obviously, that the requirements are higher than anything I've ever seen from anybody else. And the fact that they were willing to publicly talk about this and be a public reference for us shows the level of confidence that they have in the underlying technology, in the security and privacy that this allows them to achieve. >> We still hear reservations, particularly from heavily regulated industries, about moving into the cloud. Concerns about security, data ownership, shared responsibility. >> Ayal: Yes. >> Are those real, are those valid? Or is the technology foundation now strong enough that they should not be worried about those things? >> Yeah, this is an excellent question, because the the shared responsibility model, is exactly sort of the core of what this is about. The shared responsibility model essentially means the cloud's, sort of by definition, the cloud is somebody else managing the infrastructure for you, right? And if somebody's managing the infrastructure for you they have full access to what you do on top of that infrastructure. That's almost the definition. And that's always been sort of one of the core security problems that was never solved. Confidential computing solves this. It means that you can use the cloud without the clouds having any access to what you do on top of their infrastructure. And that means that if the clouds get hacked, your data is safe. If an employee of the cloud decides to get access to your data, they can't. They just don't have any access. Or if the government comes to the cloud with a subpoena, the clouds can't give them access to your data, which is obviously very important for European customers and other customers outside of the US. So this is essentially what confidential computing does and it allows to break that shared responsibility model, where you as the customer get full control of your data back. >> Now, do you need the hardware foundation to do that? Or are you solving this problem in software? >> No. So we do need a hardware foundation for this which is now available in every cloud. And it's part of every server CPU that Intel ship, that AMD ship. This is part of almost every data center in AWS. But what we bring to the table at Anjuna, is every time there was a fundamental shift in computer architecture, you needed a software stack on top of it to essentially make it usable. And I think the best last example was VMware, right? But virtualization was extremely powerful technology that nobody was using until VMware built a software stack to make it super simple to virtualize anything. And to some extent that was the birth of the public cloud. We would never have a public cloud without virtualization. We're seeing the same level of shift now with confidential computing on the hardware side. And all the large players are behind this. They're all part of the confidential computing consortium that pushes this. But the challenge customers are running into, is for them to go use this they have to go refactor and rebuild every application. >> Why? >> And nobody's going to go do that. And that's exactly what we help them with. >> Yeah. >> In terms of why, as part of confidential computing, what it essentially means is that the operating system is outside the cross cycle. You, you don't want to cross the operating system because you don't want somebody with root access to have any access to your data. And what this means is every application obviously communicates with the operating system pretty often, right? To send something to the network or some, you know, save something to the file system, which means you have to re-architect your application and break it into two: a confidential piece and a piece that's communicating with the operating system and build some channel for the two sides to communicate. Nobody's going to go do that for every application. We allow you to essentially do something like Anjuna run application and it just runs in a confidential computing environment. No changes. >> Let's talk a little bit more about that. So when we're thinking about, I think we've talked a little bit about it, but I think there's a myth of control when we're talking about on-prem. Everybody thinks that things are more secure. >> Right. >> It's not the case. Tell us how enterprise security changes once when a customer has adopted Anjuna. >> Yeah, so I think you're absolutely right. I think the clouds can put a lot more effort and expertise into bringing security than the data center. But you definitely have this sort of more sense of security in your data center because you own the full stack, right? It's your people, it's your servers, it's your networks in the cloud >> Savannah: It's in your house, so to speak. Yeah. >> Exactly. And the cloud is the third party managing all that for you. And people get very concerned about that, and to some extent for a good reason. Because if a breach happens regardless of whose fault it is, the customer's going to be the one sort of left holding the bag and dealing with the aftermath of the breach. So they're right to be concerned. In terms of what we do, once you run things in confidential computing, you sort of solve the core problem of security. One of the core problems of security has always been when somebody gets access to the infrastructure especially root access to the infrastructure, it's game over. They have access to everything. And a lot of how security's been built is almost like these bandaid solutions to try to solve. Like perimeter security is how do I make sure nobody gets access to the infrastructure if they don't need to, right? All these detection solutions is once they're in the infrastructure, how do I detect that they've done something they shouldn't have? A lot of the vulnerability management is how do I make sure everything is patched? Because if somebody gets access how do I make sure they don't get root access? And then they really get access to everything. And conversation computing solves all of that. It solves the root cause, the root problem. So even if somebody gets root access, even if somebody has full access to the infrastructure, they don't have access to anything, which allows you to one, essentially move anything you want to the public cloud regardless, of the sensitivity of it, but also get rid of a lot of these other sort of bandaid solutions that you use today to try to stop people from getting that access because it doesn't matter anymore. >> Okay. So cyber security is a one and a half trillion dollar industry, growing at over 10% a year. Are you saying that if organizations were to adopt confidential computing universally that industry would not be necessary? >> No, I think a lot of it will have to change with confidential computing. Exactly, like the computer industry changed with virtualization. If you had asked when VMware just got started if the data centers are going to like, "Oh, this is going to happen," I don't think anybody could have foreseen this. But this is exactly what virtualization did. Confidential computing will change the the security industry in a massive way, but it doesn't solve every security problem. What it essentially does is it moves the perimeter from the machine itself, which used to be sort of the smallest atom, to be around the workload. And what happens in the machine doesn't matter anymore. You still need to make sure that your workload is protected. So companies that make sure that you write secure code are still going to be needed. Plus you're going to need security for things like denial of service. Because if somebody runs, you know, gets access to their infrastructure, they can stop you from running but your data is going to be protected. You're not going to need any of these data protection solutions around the box anymore. >> Let's hang out there for a second. Where do you see, I mean what an exciting time to be you, quite frankly, and congratulations on all of your success so far. Where are we going in the next two to five years? >> Yeah, I think with confidential computing the first thing that this is going to enable is essentially moving everything to the public cloud. I think the number one concern with the cloud kind of like you mentioned, is security and privacy. >> Savannah: Right. >> And this essentially eliminates that need. And that's why the clouds are so excited about this. That's why AWS talks about it. And I think Steve Schmidt, the of CISO of Amazon, used to be the CISO of AWS, talks about confidential computing as the future of data security and privacy. And there's a reason why he does that. We've seen other clouds talk about this and push this. That's why the clouds are so excited about this. But even more so again, I think over time this will allow you to essentially remove a lot of the security tools that exist there, kind of reimagine security in a better way. >> Savannah: Clean it up a little bit. Yeah. >> Exactly. And over time, I think it's going to change the world of compute even more because one of the things this allows you to do is the closer you get to the edge, the more security and privacy problems you have. >> Savannah: Right. And so many variables. >> Exactly. And it's basically out there in the wild, and people can get physical access. >> Quite literally a lot of the time, yeah. >> Exactly. And what confidential computing does, it provides that complete security and privacy regardless of even if somebody has physical access, which will allow you to move workloads much closer to the edge or to the edge itself instead of sending everything back to your backend to process things. >> We have interviewed a number of security companies here during this event, and I have to say, confidential computing has never come up. They don't talk about it. Why is that? Is there an awareness problem? >> Savannah: Are they threatened? >> Yeah, so I think the biggest, and to some extent, this is exactly like I kept bringing up VMware. Like VMware's, you can think of Salesforce, when they talked about SaaS, they sort of embedded the concept of SaaS. No other company on the planet was talking about SaaS. They created a new category and now almost everything is SaaS. VMware with virtualization, right? Nobody was using it, and now, almost everything is virtualized. Confidential computing is a new way of doing things. It's basically a kind have to shift the way of how you think about security and how you think about privacy. And this is exactly what we're seeing. I don't expect other security companies to talk about this. And to some extent, one of the things I've realized that we're almost more of an infrastructure company than a security company, because we bake security to be part of the infrastructure. But we're seeing more and more the clouds talk about this. The CPU vendors talk about this. We talk to customers more and more. Like almost every large bank I talk to now has a confidential computing strategy for 2023. This is now becoming part of the mainstream. And yeah, security companies will have to adopt or die if they don't fit into that new world that it is going to create >> This is the new world order, baby, get on the train or get left behind. >> Ayal: Exactly. >> I love it. This is a really fascinating conversation and honestly what you're doing makes so much sense. Yeah, you don't need me to validate your business model, but I will, just for the sake of that. >> Thank you. >> We have a new challenge here at re:Invent on theCUBE where we are looking for your 30 second Instagram reel hot take, thought leadership. What's the biggest theme, key takeaway from the show or experience this year for you? >> Yeah, so for me, obviously focusing on confidential computing. I think this is just going to be similar to how no network was encrypted 10 years ago and today every network is encrypted with TLS and HTTPS. And how five years ago no disc was encrypted, and today every disc is encrypted with disc encryption. The one missing piece is memory. Memory is where data is exposed now. I think within a few years all memory is going to be encrypted and it's just going to change two industries: the security industry as well as the computer industry. >> Paul: Does that include cache memory? >> What's that? >> Does that include cache memory? >> That is encrypting the RAM essentially. So everything, this is the one last place where data is not encrypted, and that's exactly what confidential computing brings to the table. >> Are there any performance concerns with encrypting memory? >> That's a phenomenal question. One of the really nice things about confidential computing is that the heavy lifting is done by the hardware vendors themselves as part of the hardware and not part of the critical path in the CPU. It's very similar to the TLS acceleration cards, if you remember those, which allows us to be extremely, extremely performant. And that's why I think this is going to be for everything. Because every time we had a security solution that had no performance impact and was super simple to use it just became the default, because why wouldn't you use it for everything? >> Ayal, this has been absolutely fascinating. We could talk to you all day. Unfortunately, we're out of time. But really thank you so much for coming on the show. Now, we feel more confident in terms of our confidential computing knowledge and definitely learned a lot. Thank all of you for tuning in to our fantastic four day live stream at AWS re:Invent here in Sin City with Paul Gillin. I'm Savannah Peterson. You're watching theCUBE, the leader in high tech coverage. (gentle music)

>>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.