Analyst and Investor Product Demo - SAILPOINT INC

Good afternoon, everyone, or I guess good morning for many of you. Thank you all for joining us today. My name is Scott Schmitz with Investor Relations here at SailPoint, and we are very excited to show you all the highlights from our Navigate conference next week, which was a great event. But before I get started, a little bit of housekeeping. Today's presentation and discussion are strictly reserved for research analysts, shareholders, and members of the financial investment community. If you do not fall into these categories, please disconnect from the webcast at this time. Additionally, please note that the development, release, and timing of any features or functionality described for our products that are not currently available remains at our sole discretion on a when and if available basis. It may not be delivered at all and should not be relied on in making purchasing or investing decisions. We will not discuss the financial impact of products on this call. So with that, our agenda today is fairly simple. Chandra, our EVP of product and chief technology officer, will recap key messages from Navigate. And then in the spirit of showing versus telling, Levent and Dan will demo the platform. And for Q&A, the chat function is enabled. So please type your questions as we go, and we'll aggregate and address at the end. So with that, let me turn it over to Chandra. Thank you, Scott. and welcome everyone to the super intelligence security briefing, you know, is a way I would describe it. So look, we are at AGI, and I think our, or at least near AGI. And I think this is pretty important context for the conversation today, because the speed at which these machines are operating, the scale and the complexity, all is being driven by the fact that we are at or near A GI. So with that, I'll really start with what are the key messages that we really delivered last week and that we would like you to take away today uh one is look uh you know given we are at hegi uh you can't really solve or you can really secure ai by having human in the loop all the time and i'll kind of walk you through more in detail but so we announced our autonomous agents vision uh a class of red blue and green agents uh i'll talk to you more about it but you know that was there was a big announcement last week uh we delivered and announced the very first operational identity platform that can truly deliver least and zero standing privilege uh this has been an ideology for about 20 25 years getting to least privilege and zero standing privilege as a really as the true north of being very uh secure that is a there's never been an operational platform that uh delivered it with what we ga that black hat and And what we announced last week, the combination is the very first operational platform, both for human and for AI. Atlas, which is our platform, that is the core service layer that underpins everything we do. We have completely rewired it. I'll walk you through the changes. We've also made Atlas extensible because, you know, a platform's got to be extensible. So we announced some major capabilities around plugins and application builder and marketplace. And in fact, we conducted a hackathon with 250 to 300 developers, hugely, hugely successful on using Atlas Extensibility. We have continued to innovate on the core because we have more than 2,000 cloud customers. And so the core innovation has been going just as fast as these other things. And lastly, on the operational side, we announced a few new regions, support for things around EU, Sovereign Cloud, FedRAMP High, as well as a completely, we showed a completely reimagined user experience. So those are the key messages that you should be taking away by the time we are done today. So I want to start with, you know, how we are solving the problem. The foundation, you know, the foundation is really solving it as a human plus AI problem, because you can't really have two platforms, one for human, one for AI anymore. You have to solve both of those in the same place, which is what we are doing. And when you really introduce AI into the mix, right, you have speed, right? Machine speed. And so you have to be, so the platform has to be real time and you have to be in line with threats. On the scale side, we have done the math. We are beginning to see this in our platform already. There are somewhere between 75 to 150 million agent tech interactions a day at any of our large customers. Think of a global 2000 corporation. When you give an agent a task, it calls multiple LLMs, APIs, data, and so on. When you do the math on all of that, It's about it's like somewhere close to 100 million interactions a day at that scale. It's not just the scale. It's it's the topology and the complexity of those of those interactions, the surface areas that you have to deal with. You know, this concept of zero trust, which was really invented 20 years ago for the human world, will no longer work. This is why we announced our vision for autonomous identity. And we were very, very excited to launch our SailPoint autonomous agents. And we really described them in three classes, right, to really simplify this. And it's not like one red, one blue, and one green agent. It's a class of red agents, a class OF blue agents, and a class Of green agents. Let me really bring this to life for you because we kind of showed our vision around about 10 of these, right? But let me really brings this to light. A red agent, a good example is let's say you are on PTO, you have a bunch of agents working on your behalf. You have a Microsoft co-pilot agent that's taking some notes in the meetings that your teams are doing. and you might have an agent for the agent inside Salesforce and a cloud agent built by you on top of Google Cloud. Now, what if those agents are accessing data that they were not supposed to, that you don't have permission for, right? This is what a red agent will catch. It will basically say, wait a second, this agent is accessing data, critical data that its human owner was not even supposed to access. And while they are on PTO, this doesn't look right. A red agent will catch that. A blue agent now is actually a defensive agent. A red agent is an offensive agent. A blue agent will be like, oh, okay, looks like the red agent found something. Let me go do further diagnosis on this. And if it actually determines there was a breach, it will stop that breach. Meaning, if this agent that is working on your behalf is accessing critical data that it's not supposed to, a blue agent will automatically stop it. Now, a green agent is what we call a peacetime agent. A good example is automating certifications. So, look, our customers, these are the large ones, the complex ones. When they run a certification campaign today, even just on the human side, not even including AI side, a lot of them have between 5, 8, 10 million line items in a cert campaign, right? And just that's huge complexity. Our contention is 95% of that should be automated because you should, we are moving to policy-based governance in a policy- based world. You should be able to apply intelligence and automate 95%. That's what a green agent does, right. And so it's not just a vision. We announced that we will be launching a few of these at least in the next few months. And in fact, last week at Navigate, we signed up one of the largest banks in the world as a design partner to actually build and deliver on the green certification agent by like the December, January timeframe. So we are quite excited. This was extremely, extremely well received. now look the reality of today is uh 99 of the world is is in standing privilege right so it's going to take a journey to go from where we are today to get to autonomous identity that's why going through least and zero standing privilege is critical this is why our announcement uh with what we ga the black hat and what we announced last week we are the very first operational platform that can truly deliver on least and zero standing privilege. Now, we spoke to you, you know, I walked you through this exact picture on Investor Day. I think many or most of you would have been there. As well as at Black Hat, we, you know announced a lot of this or we generally made these available. So what I'm going to do in the next few minutes is really give you a glimpse of what's new that we announced last week so that you know what's coming. I'm not going to rehash what is already in the market because we have talked with you about that you know already um so and the first of the newness i'm going to talk about oh sorry you know i'll stop here right which is look the single point value proposition across both agentic and and the human side is discover govern and protect and you know uh on investor day under black hat i actually talked about protect and I said this is protect is where all the runtime controls are right and this was extremely well received last week and in fact there was a massive reinforcement that the world is sort of moving from doing discovery to really you know wanting to act on things they are finding and starting to do audit and governance which is which is under governed and so this was extremely well received but I also want to say you know because there continues to be a question about But when SailPoint says runtime controls, you know, how does it play with other IDP players, right? It could be an Okta, it could be a Microsoft Entra or a Ping and so on. You know, what they do is, you Know, the IDPs do authentication, right, and so both for human and for AI. So they are really the front office or the front gate, right or the Front Door. Once they come in, what we have done now is with all the runtime controls, we have actually introduced another gate, right, which is what we call a policy decision point, right? And so in the flow of traffic, so you can get authenticated and get token exchanged, and a policy discussion point will actually evaluate the risk of that access, right. and determine whether even though you have the right credentials for accessing a critical piece of data, whether or not you should at this moment, right? That's what a policy decision point does. So protect, there are five runtime controls. And this is a big deal because you want to have discover, govern, and protect in the same platform. You don't want them in different platforms. So, in terms of newness, right, let me quickly give you a sense and then Levent and Dan will actually show you. So, as you know, we acquired Entro about 90 days now. I'm thrilled to be announcing the SailPoint Agentech Fabric and Entro will be completely integrated come November and the fully integrated product will be generally available. at least at least in my experience and our experience this is one of the fastest software integrations you will see uh we have been very very ambitious here given the pace of innovation in the market we wanted to make sure that we had one product that actually brought everything together uh so come november this the fully integrated product will be generally available on the sale point agentic fabric there were a number of net new innovations we announced let Let me give you my own personal favorites, and Levent and Dan will walk you through it. On the Discover side, the main message that we delivered was really, or what we announced, was around posture, autonomous posture. And I'll tell you, look, we have 20 plus real-time signals to which we calculate a sale point risk score and get posture. Now, the mainly differentiating part of the sale point posture relative to everyone else in the world is the fact that we can actually act on the posture. So it's not just, hey, you know, that is an exposed credential. Our platform will allow you to go rotate that credential or, you know. Delete it. Right. And so you can you can act on the vulnerabilities you find. That's a main differentiator on the government side. We are bringing certification for agents and human together. This is a big deal. Right? You can no longer certify either a human or an agent without knowing who's or the human or the agent associated with them and what they have access to. So we are bringing the certification experience for human and agent together in one platform. On the protect side, we are really delivering on, you know, just in time. There are on top of it's not like we have four or five controls in the market today. We have we have added more depth and expanded the surface area. Right. So all around just in time, real time authorization and the main and the main advancement we announced last week and a ton of customer excitement was all around the ability to do real time authorization to find the right data. And the way we are doing it is through integration with all the big data cloud platforms, be it Snowflake, Databricks, BigQuery and so on, as well as all the existing DSPM providers. Right. So Sierra to proof point. Right. You know, we're all in this right. So if a customer has already done classification and has policy on data in those DSP and DLP providers, we will automatically integrate with them, grab that context and map it to the identity context. Right. And so so those were those were the things that we talked also we announced and my personal favorites. On the human fabric side, I think in fact I would characterize our innovation on the human fabrics like to be just as rich actually as what we have done on the agent side. On the Discover front, one of the things that I'm personally most excited about is we are really bringing the element of risk and posture to humans and this is a big deal. Now, in our platform, if you go to the same point human fabric, for every human uh you will have a risk score and the risk score is not what what they are supposed to access what they're accessing at the very moment now in actually real time and the risks associated with their access right and so this is this is a huge advancement um on govern we introduced we announced effective privilege this is huge deal because you know what you have access to it's not what not just what is granted to you it's all of the indirectly what you inherit through all the groups and roles you are part of right and it's always been there it's it's been a hidden problem and we kind of the world got away with it because uh at machine at human speed you couldn't really find these things but these machines are running around and finding all this indirect access and they are becoming a major risk vector right uh a breach vector and that's why now when we show an access graph in SailPoint's identity graph, you will see not only what the granted privileges, but also the effective privileges. And we announced on PROTECT not just JIT, but doing just-in-time authorization with policy, continuous evaluation, and so on. So that's quickly what to expect, and Dan will give you a glimpse of it. But on Atlas, like I said, I think, you know, massive innovations, right? So there are four layers of Atlas where we are completely reinvented. One is a data model, right. You know, we realized we can't solve this AI problem without really completely redoing the data model. So we have really redone the data module to be from human to human plus AI. We have built a whole context and intelligence layer with the risk engine and intent engine as well as all of the privilege classification we are doing because that's the foundation for doing just in time. And the policy engine, the policy engineer is core to actually us being the policy decision point, right? And so that is a net new innovation we announced. and the enforcement layer where we are the dynamic provisioning engine as well as the ability to respond right away from the SOC. So that's quickly what we announced in Atlas. Melissa, why don't we just go to the user experience because I'm being mindful of the time. I just want to get through this. Look, for the longest time, the feedback has been like, you know, Our capabilities are actually very good. The user experience needed some work, right? And we have heard it. About nine months ago, we went and got a world-class designer to actually lead our design team. And he has done an incredible job, he and his team. So we announced and sort of unveiled a bunch of our newer, the new SavePoint experience. on both the agent side as well as the human side. And it's not just a look and feel. We have taken a fundamentally different approach. It's all about our UI is now not just about who has access to what, not just intelligence, but the ability to act on it, right? And so a very action-oriented UI. We also think the users are expanding. It's not juste an administrator or a practitioner. It's every business user. So we're also driving more of a consumerization of our end user experience. Excuse me. I'm fighting a little cold. But, look, you know, hopefully that gave you a glimpse of what we announced last week. I know I went through it quickly. But what I want to do is, you knows, hand it over to my good friend and colleague, Levent, our chief product officer, who will actually show you some of the innovations we launched on the agentic side. Levon, please. All right. Thank you, Chandra. Hi, folks. I'm really excited to show you the product that we just talked about in action. So what I'm going to do is I'm gonna walk you through our agentic capabilities, our agentics and our agent fabric. I'm not going to walk you how a security professional and an administrator can discover, govern, and protect their agents, their non-human identities, their credentials, their secrets through our capabilities. And I'm going to hand it over to Dan, our VP of product for our human fabric. He's going to walk you through our capacities and all the innovations that we've done across the board on the human side. So I'm gonna start with our agentic overview. This is where a security administrator, when they launch their agentic fabric, would land. You hear they can see all the agents that they have, all the unsanctioned AI, those AI platforms that maybe were not approved by the administrator beforehand, all the agents without owners, some major basically critical risks here that they want to know about in numbers, and all the NHIs that they have. And the risk widget here shows you the critical, very well organized and sort of critical high and other findings here. You can see in one quick snapshot, a critical attack vector has been in both the Frontier model exploits, but also in general in the cyber attacks lately has been exposed credentials. These are the credentials that for some shape and form leaked either publicly or in the, you know, not places that are publicly available or accessible to other customers or other users. So you can quickly see all your exposed credentials here that we have detected also sorted by criticality. And, you know, this is basically just a great dashboard that gives you, like, a quick glimpse of your landscape, the top risks, the top pieces that you have to pay attention to. We have Vizca AI agents here again. One of our key capabilities is behavioral monitoring. We monitor the agents and their behavior as well as NHI and their use in almost near real time to see the spikes in their activity. I'll show you more about this in detail in a second. So we have some great data here about what we found, some of the anomalies that may be flagged and in some really useful information here that you can't see in a dashboard but let me dig in to a little more detail about what we actually show so let's start with the the agent inventory now our inventory is aimed to be the single source of truth across all your visual landscape we have multiple as chandra said we have multiple detectors and sensors we plug into the platforms we have thousands of connectors first of all and then you know in addition to that we plug into all the top ai platforms all the the critical uh you know sas platforms that you know are used in enterprise that we can imagine as well as of course we have our own sensors on the endpoints so we can detect any kind of endpoint agent activity ourselves uh as well as on the web browser we have a very great easy to deploy centralized uh web browser plugin that basically detects any kind of user and agent interaction now that's very critical because that means that we can basically detect the full life cycle of an agent and their use of nhi from beginning to end from the point that the user maybe prompted an agent with a specific task where we can understand the intent and how it's planning its activity all the way to you know um actually accessing the resource and executing the mission and all along we can you know track all that activity and detect behaviors right so let me show you how we do that here so you know here's for instance let's you know these are all for agent inventory let's click on one of these so here very quickly you can see who owns this agent what are the other users or owners that does this this this was a clearly a cursor agent that was discovered an endpoint it's accessing aws so let's let's look at the the critical actually insight that our customers love which is the lineage the usage and the lineage of this agent so here you can see ella pitters created this agent on her local macbook pro it was a cursor agent and some interesting things right like so this agent is using multiple identities they caught all of them right there's a service account here there's a token here that we kind of created and you can also see what these agents uh and through these identities are accessing to so in this case it's a very interesting right like you know it's accessing a storage s3 storage account it has access to figma the design system it has a production sql database so these are some really high privilege access that this agent has through cursor so and that's why it was you know if you look at it it was probably you know uh ranked as critical right so let's kind of go dig into further though here right so um you know we can look at the the access graph of this agent so we the lineage showed you what it did the access graph shows what it has access to that also goes into our risk calculation so you can see the full access graph for what this agent can do you can zoom in slice and n of these and understand that uh and you know you can't see the identities are using it uh the accounts are associated with it but here's the most important tab i would say we have a dedicated risk tab here for this agent we figured out the top issues that this agent has demonstrated and classified those risks in this case this agent was using an unclassified unsanctioned mct server so that means that it had capabilities that you the administrator probably didn't know about that could be dangerous it's an unsanctioned platform so that's clearly another risk factor um the human owner was confirmed but the ownership was you know is not exactly the classification is exactly matching the behavior so some really great uh you know details here that you can see right off the bat and here's another critical piece here uh and this is the behavior so i talked about our abnormal behavior detection this is basically that in action you can uh on this graph all the sessions and activity that this agent has done over time and you know when there was specific things like or just you for instance in the very first one it was an unsanctioned agent platform that we saw that and then it was accessing you know uh you know it did a spike in its uh planning for a specific activity all of these get basically got flagged uh on our abnormal behavior detection and that figured in to the high risk severity so we already kind of found out from the very get go that hey look, this is their high risk agent, access and production systems, non-sanctioned platform, you don't want this. So again, as Chandra said, this isn't just a discovery platform, this is an action platform. So you can very easily take action on this and you can create policies to first of all, block this action. I'll show you how, but in this very moment, we know that this agent needs to go. So we can just simply say deactivate and deactivate the agent and that would be gone. It's as easy as that. So that's the power of this platform. You can deactivate and take action any moment. That's our kill switch that we have here. Now, let me move on in the interest of time here. We talked a lot about agents and how we detect it, but the reality is agents use credentials and equally important to manage and govern and protect other credentials. and here we can see all the credentials that you know your landscape has you can slice and dice them by idle ones by exposed ones you know maybe ones are owned by former employees that's a major flag that you should manage those ones that are privileged and you can easily you know go through those you know filters and you know either rotate them or take action on them and but more interesting about credentials and one of the top attack vectors as we mentioned especially the frontier model incidents exploited was exposed credentials. So let's go there because this is one of the key areas that are, when we do a POC, customers get surprised quite a bit about. They are so surprised, A, how they have way more agents and how they are way more credentials than they thought they have, and B, how many of those credentials are actually exposed, are not secured or stale or idle or owned by former employees. So this is the place that they would come to, in this case expose credentials and they would take action on it so for instance in this case let's take for instance this one let's take a random one here this was the aws credential exposed on a slack channel right that you don't want that because slack channels are not exactly safe places to expose your credentials again you can see how that credential was used in this case it was another user it was a cursor agent you know and then that credential got used for access to much better things and you know you can easily take action on this as well as chandra said to rotate it or or be activated so that's basically our exhaust connection now uh to show this was just one risk vector to really explore all the risks on your landscape which is again one of the top areas that people are very curious about and gets rise when we do a poc with them is the risk center this is the place that they come to see all the top risks again here you can sort by critical risks and you know and you notice various type of filters here that we can go do abnormal tokens abnormal wall activity from employees again and you can you know basically go ahead and you know easily see these risks and handle them as you see you can see the details all the connected services all these pieces are here all right so now we talked a lot about activity of agents and nhri the risks around them and how we can manage it how we can govern and protect them let me focus into an area that you know is very critical for our customers and that's auditing compliance so usually other than compliance is this ceremony that takes you know in some cases honestly weeks to finish and months for some of our large complicated customers and we really thought deep about how we can innovate here how can we make their job easier faster quicker and we came up with a new innovation here that you don't know other you know vendor has which is pre-can easy to use uh other reports that automatically run on a schedule that you would like so here we have basically covered most of the frameworks that our customers are trying to out of time comply to like gdpr and hipaa and you know the eu ai act and the great thing about these is while you know we have these pre-canned reports that we can just simply you know export that just created the tax and that's going to basically be in progress and and it's gonna be ready probably in a few minutes. You can do this, you can export anything, you can also schedule this on a time basis. So this is a great innovation that we added. Customers love it so much that, hey, I want this on the human side too, so we're gonna now unify our other capability and create that on the humans as well, these capabilities. And it's really been a very exciting capability for our customers. And each of these are also customizable. So if those pre-canned reports doesn't fit your needs, You can actually go ahead and create your own customized evidence reporting that's as easy to export. All right, so I'm mindful of the time here. Let me come to a very important protect capability, and that's our authorization, agent authorization capabilities. So one of the key things our customers, of course, face is once they discover an agent and their agents in their landscape, once they discovered the NHIs, the first thing they want to do is start putting guardrails. for instance you know you know they can be very simple they can't be very complicated we can do all of the guardrails that people want to create but for instance one guardrail that people want create is hey look first you know i'm deploying a coding agent for my developers obviously those coding agents have some critical access to github and other resources i don't want that maybe to access uh i don t want that to be used by uh people in marketing department we can't do that right we have authorization policies that enable that so here we have this policy center that enables you to create all these great policy types i'm going to show you a quick one here in this case for instance we have another one that says hey look i do not want uh our agents to send uh slack messages right because you don't want to maybe spam the user or you know share credentials or anything like that so we can let's walk through this this policy basically uh says hey make sure that cloud code right agents using any mcp servers it could be a server, it could a gateway, it doesn't matter. Whatever they use, again, we enforce it on multiple layers. That's the power of SailPoint. Cannot send any Slack messages. And remember that we can... Notice that it's a very fine-grained policy. It just says, do not send messages. You can still read messages on the platform with this policy. So this one is enabled. That means you already have the protection. So if I were now to create an agent and that you know try to create a stack message it would not work now i will uh so that's a very quick glimpse of all the capabilities that we have uh on the sale for agentic fabric we have way more than that the time doesn't allow us to show it but these are some of the top customer favorites i'm going to hand it over to dan martellati our vpo product for human fabric where he's going to walk us through the innovations that we had on the human agentic site on human my fabric side. Thanks, Levent. I'm going to go ahead and look at what we see from our autonomous identity security posture management that Chandra talked about earlier. It is the ability for somebody from a security and risk perspective to be able to see what's happening across their identity program for all types of identities, whether it be human identities or non-human identities. And look at a variety of posture dimensions to understand what's happening within the environment and what risk may exist. Now, as Chandra mentioned earlier, the key thing around the posture management work that SailPoint is doing here is it's not just visibility, it's about remediation and action. So when we identify where there is a potential issue within the system, we're going to use AI to be able to analyze the risk and provide you with a recommended remediation of that risk that you can then execute from within this single dashboard. The other interesting thing about this whole program is as organizations are expanding their identity program and expanding the types of identities that they're governing, understanding their capability adoption of the program and how that impacts their ability to truly govern what's happening in their environment. So, this gives them some insights into the adoption of capabilities they have across the SailPoint platform and how it impacts their potential risk posture. Now, let's take a shift and look at an administrator and the work that they're doing to onboard entitlements into the identity program so that they can be properly governed. So a couple of years ago, we rolled out the ability to just create entitlement descriptions. And the idea of entitlement descriptions are, as an application owner, when I define the description of an entitlement, I do it from the perspective of an expert. And it doesn't necessarily translate into descriptions that end users understand about that application. So we discovered, we created capabilities to create descriptions, but now we've automated that process. So when I onboard a new application and we discover new entitlements, we're going to automatically generate entitlement descriptions for all of those entitlements. As the administrator of the program, you can review those entitlement subscriptions and make adjustments to them. But now by providing that level of context, when anybody needs to interact with the application, they have better understanding of what that entitlement grants access to. Now, another view of this is looking at what we're doing from a privilege perspective. So as you're onboarding new applications, being able to evaluate those entitlements and help you understand what is the privilege associated with each of those entitlement. Is it high privilege? Is it medium privilege? And giving you the ability to make adjustments to that. We also talked earlier about this idea of effective privilege. So I can see for a particular entitlement how that privilege severity was defined, and it can include the effective privilege that's associated with the embedded entitlements that are a part of that role. That's the power of the identity graph. So now we're going to transition to an end user who needs to request access. They need access to go in for themselves. And we've generated a new user experience where instead of having to go in and search for particular entitlements or know the name of something, we have a new agentic experience where you can go in and interact with search and say, I need access to run payroll, for example. We're going to do an analysis of who the user is, what roles they have within the organization, and make a recommendation for the role or the entitlement that they should request. So this is a high privileged role, and it is also a just-in-time role. So I'm going to add this to my request and submit it. Now, what traditionally would happen is that entitlement or that role would be provisioned to the end user, and they would have standing access to go perform that task. Well, since this was a just-in-time privileged entitlement, we now have a launch pad that the user can go to, and when they're ready to use that entitlement that they are pre-approved for, they can click on start session. That will be when we automatically provision the access for that particular item within the boundaries of policy associated with that access. And we may require the user to provide some justification or a ticket number to be able to activate this access. But once the activation happens, now we provision that, the user can perform that task, they're time-bound based on the policy associated with that particular entitlement, and when they're done, they can simply end the session, and that deprovisions that access, right? So, now, we've moved from standing privilege or standing access for privileged entitlements to just-in-time access when I need to use it. So, I've got pre-approved permission, but it's not a standing privilege. And then last but not least, we talked earlier about certifications. This is one of the toughest things that our customers have to deal with. You're asking day-to-day professionals to go in and certify and review the access of all of the employees that they've got. I know that when I talk with Levent about this, right, there are things that I have access to or people on my team have access too. We're not quite sure whether they should have that access or not. We don't have all of the details about the entitlement or how they're using those entitlements. Well, with this new mechanism that we've developed, we can go in and automatically generate and review the access associated with all of those users and make this recommended decisions on the access for all of those entitlements. And it's going to be based on a variety of guardrails that are defined as the certification policy is put into place. So I can create guardrailes that say, for example, if this is privileged access and it hasn't been used in the last 30 days, recommend revoking that access. If it's access that's been reviewed multiple times and had been approved, Well, let's just go ahead and automatically recommend keeping that access. What we see as a reviewer now is all of the recommended actions that are being taken. I can override these if I choose to, but I can see all of the details associated with every single one of the decisions that the system has made, and I can choose to adjust or confirm those decisions. We believe this is going to really reduce the amount of time that people spend reviewing the access that their employees have and really create more value. All right, Chandra, I'm going to turn it back over to you for any closing thoughts. No, look, I don't have any particular closing remarks. Scott, I'll turn it over to you because I think we should really move to taking Q&A now. Perfect. Yeah, there's several questions that were submitted. So if you have others, please type them in and I'll go through a few here. So the first one I wanted to relate to the team, and there's a couple of different versions of this, so I'll just read one of them that kind of encompasses it. But a lot of identity security players are trying to become the runtime enforcement layer for agentic identity. What gives SailPoint the right to win here compared to other identity vendors which are already operating in line for human access management? Sure, sure. You know, I'll start, you know, answer that in two paths, right? One is, look, you know, the only way to have, or the only way to really enforce runtime controls in a very, very effective way is to have deep identity context. And the best way to think about this is, you know, the proverbial kill switch now, right, the kill switch for agents. A lot of runtime platforms claim to have a kill switch, right. You know, our viewers, an agent kill switch is supposed to kill a bad agent. Now, a kill switch should know, or what's the basis on which the kill switch will know what is a good agent versus a bad agent, right? You know, it's like giving a security card a gun and say, well, shoot the bad players, right, you know, they've got to know how to distinguish the good and the bad players. So that requires knowing deep identity context, right. You know you've got to be able to say this agent is a bad Agent because it violated all the policies of access. there is a pattern of access behavior here where it's tried doing bad things. We have analyzed the intent for that agent and it doesn't have the right intent in the way it's prompting. And so with that depth of context, you have to combine that with the runtime control, which is what we are doing. And that's a real differentiator. And the context comes from discover and govern and protect is where we enforce that, right? So that's sort of part one. Part two is in most cases, we actually coexist. It is not a one size fits all. It's not a win winner takes all, right? So let me give a couple of examples. So you could say after Microsoft Entra, they are in line with the traffic. They are looking at the token. They're doing token exchange and so on. But they are really the front door. Once you are inside, you know, at a very fine, you know, they will tell you, you have access to the Snowflake database. Okay, go. You are validated. Now, it could be a human or an agent. But a specific row or a column of data inside Snowflakes and what is the, and, you know, if it's, whether the data is very sensitive and at the very moment that human or agent, can they have access to it that context they don't have that context we have and that's why we are the policy decision point and we are the real-time authorization engine so they do the idps do authentication and we do you know we do authorization find great authorization so hopefully that that makes it clear on why on the differentiation and the need to coexist Great. Thank you. I think a good follow-up to that is that we have several questions on just the differentiation versus the platform vendors, and what telemetry do we rely on from those vendors, or what are we incorporating into our platform from the platform players? Yeah. Look, you know, Levin, you want to talk about how we have our own telemetries, but we also get all the logs from the… That's right. Exactly. Yeah. I can't Yeah. So look, I mean, look, we are obviously, you know, we're hooked into as many places as we can, and we never turn down data. So we, first of all, have our own sensors and telemetry directly that we source, right? uh again from a genetic perspective we're on the endpoint we have an endpoint sensor as i mentioned earlier we're in the web browser so we can get direct interactions in a web browser with agentic pieces right we are have thousands of connectors so we connect to all types of different sources right in the both for the humans and the agents combined right so we cannot see their access what they're entitled to we actually you know manage that access right we control that access and we know exactly what their provision not provision for now on top of that of course uh we have you know you know we also plug into all the sim and xar tools we can get like real-time log data from you know from many of the providers out there from like network providers and idps both at the log layer but also at the direct integration with their platform so we can see all the activity through both those platform players as well very easily um so literally like you know i can go into details here, but we are aggregating and putting all that information together. It's our unique differentiated data that we have through our thousands of connectors, our presence through Endpoint and the web browser and the direct plugins to all these platforms. Plus, we also suck all the data in as the customers, of course, allow us to do, to overlay it, combine it, and add human and data context to it. And that's the power of it. We make intelligent risk assessments and creations and create policies out of it that that then people can deploy on their platforms. And Levin, it's not just access to applications, it's also access to data, right? So we look at it holistically across the board. That's right. We plug into the DSPM, the 11 providers, we have our own classification, but we also get all the related classifications for customers that have existing classifications from their Microsoft Purview or sales of the world, or proof points of the role. So we can easily get that and also make that a policy decision parameter for our policies, our customers on our platform. Got it. So I think you probably answered this in some of that response, but then what makes identity or SailPoint the right kill switch relative to some of those other players in the market, right? Where they have a lot of visibilities, but why is SailPoint, the right killswitch? Yeah, it's really the con, you know, it's the, you use the word context And, you know, I recognize it's actually an overloaded work. So the plain English translation of that is, you know, the kill switch needs to know, you know, be, you know, particularly for agents, right? You know, what is the risk associated with that agent? And, and, you know, if that agent has done or if that agent has gone rogue because it has, like, drifted from policy, the policies that were, you know assigned to it to you know how bad is it dreamt uh is there a pattern of behavior over the last few weeks where it has continuously drifted uh you know analyze the intent because a lot of times you know what people don't realize is agents are prompting they will go to a command line interface and they will prompt something to get access to a tool let's say analyzing those prompts and seeing whether the intent behind those prompts is right, this is what we do, right? And so when we say the lineage, the depth of context, we take like 10 parameters into account to actually determine risk. And this is why this risk and posture is very important. Now, then we use that to do the enforcement, right, you know, actually doing the enforcement is actually the last mile, 80% of, you know, the, uh, the traffic, you know, isn't actually make doing all the analysis, the policy drift, the risk, the intent, all that analysis to make sure that you are a hundred percent convinced that, you know, uh that you, that you have spotted the real bad actor and now is the time to stop them. Yeah. And Chandra, the additional piece of that, right, is the human context. Many of those agents that you're talking about are acting on behalf of somebody. And so if the human contexto provides insight that there's risk, that can flow through as a part of that. Yeah. I mean, imagine like, you know, if someone, imagine an agent shows up on your front door and they have a pass that says, hey, I want to access this resource. Like, I'm going to get into this house, right? If they have an access pass, it looks legit, right. That's what an access layer does, right! They let them in based on that past, which is a token, right, with a claim on it, right? But what SailPoint does is, hold on, that agent is trying to access or that person is trying to access that house, right. They have bad intentions. They were trying to break into deep financial information, maybe. They're owned or they are associated with a network of bad players, right there. I have like a behavior in the past, right that have like malicious intent and malicious behavior in The Past, right and they're trying to you know obviously get access to all the critical things in your house would you let them in that's the sale point power right you know and access there might just see the token so you have a visitor pass go in but we see the full context of data what they have done what they did what they want to do and basically stop it right there so i think that's the differentiation that we bring to the table very helpful uh and next question is really again all these are kind of related um but how do we enable the provisioning certification review of agents uh that are ephemeral in nature and how do how do they manage this ephemera agents really yeah i can take that we we capture from all agents uh just easily because again we have near real-time capabilities of the detecting these agents in real time with our sensors right uh so we can see them and there There are multiple ways. First, we can, as I show, we can create policies to say, hey, look, I allow sanctioned AI platforms to do certain things, and I don't want them to access certain resources. For instance, a marketing agent, however long-lived or ephemeral it is, cannot access maybe GitHub repositories or production systems for coding. So those policies get applied no matter what, ephemera or not. We detect them, we apply our policies. And we also, of course, also have a record of a firm of agents that will detect them as well. So if you need to certify their access or audit them, we have, we'll have all that in our evidence trust. Great. Okay. Switching gears a little bit. A couple of questions came in on Identity IIQ. So what, can we just kind of quickly recap, what are the importance of the announcements that we made at Navigate on IdentityIQ, and how does the features or how do you manage agents if you're on IdentITYIQ today? Great question, Matt. Yeah, do you want to take the IQ and I'll take the agent side? Sure. So look, the reality is lots of customers are still running on top of Identity IQ, and we're continuing to invest there. So there's a lot of new features that we delivered as a part of this latest version of Identity IQ. And part of that is really modernizing the platform on which Identity EQ runs. As a piece of software that runs within the customer's environment, they're responsible for the web servers, et cetera, that are running on top of it. And those are maturing and changing. And so part of the investment that we made was making sure that we can help customers run on a secure environment while we continue to invest in the core capabilities that are part of that application. Yeah. And we understand, you know, obviously, you know, while we invest in IIQ, a lot of customers still have agentic needs, and our agentic fabric does not require, it can run standalone. It doesn't require you to be on our human fabric. It has direct connectors to IIQ. It can bring in the human data context from those connectors easily. So you can have IAQ and our agentic fabric run side by side without, you know, doing a migration of any kind of sort of anything like that. So that's the beauty of our setup here. That's right. Okay, great. I'm going to go back. Another question came in. I just want to make sure we clarify this point, so I want to ask this question as well. It said, in line with previous replies, what happens when agentic activity happens on the endpoint, not necessarily via MCP? and do we have visibility to that or how do we manage that endpoint that we may not, you know, do we see all that traffic? Yeah, look, we, yes. Sorry, I was trying to. Oh, no, no. Please, please. Okay, look. Look, we meet our customers where they are. And what we see is while there's a lot of convergence on NCP, you know we realize a lot of people have different setups that they have to accommodate for. And we have layers of protection that basically come in and both detect and protect and govern those agents so obviously like if the customers have mcp we plug into their mcg gateway or we have our own mcb gateway we also have an mcd server that we can use on locally but if people don't want to do mcps or if it's not maybe a shadow ai you know we have an endpoint uh sensor that people push out to their endpoint devices and we can basically monitor all the processes and and figure out what the agents are doing and apply our policies that way as well so we don't have to have an mcp we basically you know protect and guard against non-ncp agents as well yeah the only thing i would add is we also have plugins right and so for instance for all the big uh endpoints we have a plugin so we get clock code cursor codex right and so let's say there is a new endpoint agent that gets launched tomorrow um and if they don't support ncp it'll take us like a week or something to actually build a plugin right and And so we, because we have the full context and we view the endpoint as both a detection mechanism as well as an enforcement mechanism. So as long as they have some published API, we will actually, you know, we can do enforcement through them. It doesn't have to be MCP compliant API. Yeah. and it has to be both right because sometimes agents will bypass mcps and go directly to the endpoint so we have to be able to do both right good point um okay another question here again switching gears a little bit just in terms of what's available today what's coming uh i know chandra you had a slide but maybe just is there a way to kind of for investors think about what we announced at investor day what's ga today what'S coming any kind of yeah yeah so yeah you think of them instead of three three tranches a good chunk a good majority of them or gender or will become generally available november one which is which is our start of q4 right and so i guess in in about 20 days from now that's sort of tranche one uh tranche two is by end of year sometime in December before our Q4 ends, then there are a few things that will be in Q1 of next year. So think of February, March timeframe of next Year. Those are the three tranches. But a good majority, I would say 80% of what we talked about is November 1 end of year. Great. And I think one last question here, and I know we're running up on time, So I think it's a good one to end on. But can you just help us understand where customers are on their journey to help govern and secure agents? There's a lot of different noise and tools in the market. Just help us understanding what we're seeing from customers and where they are on our journey. Yeah, I'll take that. Look, and we had, I think, I want to say close to 125 conversations last week. So here is sort of the theme, right? You know, the big takeaway, which is it was even up until two months ago. Discover, discover, discover. It is still that, but it is, you know, there is a big change in terms of they are like, you know, at some level, we are like overrun with discovery. We might not be discovering everything, good and bad, but we have enough. What do we do with it? So, there is one big shift in the market, which is, you know, take action on it. You found, you found, 300 exposed credentials, rotate them or take them away right away, right now, right? So, theme number one is take action, take actions on it, run time controls. Theme number two, particularly, particularly in the last two weeks, you know, after the White House meeting with the tech giants, the, and the president signing into an executive order of the superintelligence accord audit and compliance right this just last week right the the the volume of that conversation you know the fidelity that just went up by orders of magnitude because uh if you go read the executive order and a lot of the it's all about accountability and accountability comes from audit and compliant so and and with fine-grained controls, right? And so those are the two big things in terms of market or customer adoption from discovery to runtime controls, audit and compliance. Perfect. I think that's a great spot to end. If we didn't get to your questions, I will follow up. If you have other things that came up or things that you were thinking about, please reach out to me. We do go quiet on Friday, So hopefully we can we can touch base either later today or tomorrow for anyone for any questions that are still outstanding. Otherwise, we look forward to talking to you again during earnings. Chandra, Levent, Dan, thank you very much. I think it was very helpful. So appreciate everybody's time. Thank you, Scott. Bye. Thank you.