Q up or configured or, you know, um, sometimes it's a little bit uncertain whether, you know, there's, there's that much, uh, uh, how people are pushing these things, but, you know, fundamentally there's a lot of discussion of like AI security. Um, how do you think about that in the context of the enterprise stack, what people should do or not do, how CSA should be thinking about all this?
A Yeah, so up until now, the concerns came from, uh, human threats, right? So this is, uh, uh, not you, where customers would come to us and say, hey, uh, we were, uh, exposed by this, uh, ransomware attack. So during our time at AWS, it was a very large customer that was impacted by ransomware. We, we thought that they were completely protected using our technology, the, uh, Disaster recovery service that we managed there, and we learned, unfortunately, that the customer thought that they were protected. They weren't protected because they didn't map and classify and tag their resources properly, so it wasn't protected, and so 60% of the environment was, uh, was exposed by ransomware, and that's one of the reasons why we decided to launch Eon and solve that pain point around human threats such as ransomware. So being able to detect when that happens, look for Uh, irregular write patterns and entropy changes and things like that, protect against it, and then also allow customers to, uh, recover in a granular fashion and very quickly. What we're seeing now on steroids is that the same type of threat is coming from non-human actors, from, uh, AI agents that essentially have legitimate access to the environment with, uh, legitimate permissions into such and such databases, and all of a sudden, and this now happens very rapidly, Uh, a table is all of a sudden dropped. Uh, fortunately…
AI assessment note: “What we're seeing now on steroids is that the same type of threat is coming from non-human actors”