Name: Protecting Innovation: Use AI Securely While Safeguarding Data
Uploaded: 2025-06-26T17:57:38.118Z
Duration: 40 min 28 s
Description: Protecting Innovation: Use AI Securely While Safeguarding Data

Transcript for "Protecting Innovation: Use AI Securely While Safeguarding Data": Alright. Cool. I think now we are live. I'm gonna bring my colleague David Stewart, on stage to make sure you can see all of us, and we will get started here in just a second, folks. Alright. Thank you everybody for joining. I see we've got a few more that are, hopping on. So we'll give them just a minute, and then we'll get started. Alright. It's, 11:02 mountain time, so we'll go ahead and get started. Thank you, everybody, for joining. I see we've got probably, 30 some odd folks who have joined, many of you customers. So we're grateful for your partnership and for your time today. My name is Cameron Galbraith. I'm the senior director of product marketing, and I'm joined by my colleague, David Stewart. And today, we're gonna go through, some interesting data on AI adoption that our Cyberhaven Labs team put together. Really interesting stats. We're excited to share with you really interesting insights into how AI is being adopted in the enterprise. And then, we'll talk a little bit about some solutions we put together to help address these challenges that have come up through the research. So, David, I'll let you just say a quick word to say hi, and we'll dive into it. Yeah. Hey, everyone. Great to have you here. As Cameron said, my name is David Stewart. I'm on the the product team here at Cyberhaven, and, I'm really excited to kinda tell you about some of the exciting, new capabilities that we've been delivering recently. Cool. Alright. So we'll dive in. So, AI adoption trends. I'm sure many of you joined because your organizations have either had a mandate to adopt AI or there's just been bottom up interest from your frontline workers and for really everybody from across the organization. And, you know, research is a big part of what we do here at Cyberhaven. We were founded by a group of PhD, candidates at the time, now doctors in computer science. And so deep research is a big part of our DNA. And so our Cyberhaven Labs team, took a look at some anonymized but actual AI usage patterns in the enterprise, and we compiled these findings into our twenty twenty five AI adoption of risk report that, some of you might have seen was published recently. And I'm gonna give you some of the highlights that we saw in this report, some interesting stats to be aware of, and then we'll dive into the implications of those. So first of all, it's no surprise that AI usage at work has been growing exponentially. So you see in this graph, it's been continually going up year over year over the last few years that we've been measuring this. And, you know, that little bit of variation, that's the weekends, holidays, things you would expect in a work, schedule, but the clear trend is upward. And what's really interesting is if you look at the two colors on this graph, this represents data both being copied from or going to AI, but also being copied from AI. So it's not just a one way thing. It's not just a matter of data egress. This really shows that AI is now clearly a part of the workflow of so many enterprises. So it's really interesting to see this overall. When we dug in and looked at, from an industry standpoint, where are we seeing the most adoption, who is adopting these AI tools, the trend across the board has been a big leap, year over year jump in who is using AI and how it's being used in the enterprise. And so, you know, not surprisingly, we saw I see at the bottom of the graph, technology. The technology industry was clearly an early adopter, but really it cuts across every industry now. We see a huge increase in adoption in retail, in pharmaceuticals, in manufacturing, health care, financial services, certainly. And we think this is indicative of how we've got off the shelf AI tools. You've got in house models that are being trained. But, again, every organization that we talk to seems to have AI as some kind of a mandate or initiative or major project that they are embarking on because, of course, the potential for productivity gains is just huge. Now from a security standpoint, that has some interesting implications. So when we looked at the amount of corporate data that is being sent to AI that is sensitive, there's also a clear trend and it's somewhat, we'll say, concerning or at least something to be aware of. So just over a third of the data that is going to AI solutions. So this could be ChatGPT. It could be Gemini. It could be some in house thing, etcetera. Just over a third of that in the last year has been sensitive data. So to us, this says this is indicative of AI becoming more integral to very mission critical workflows. Right? People are using, AI to help with cuss analyzing customer data. We're doing all kinds of things like that. But, of course, there are some security implications with doing that. So we drill down into it. And when we looked at the sensitive corporate data, that was being sent to AI by that type of data now, not surprisingly, like I said earlier, the technology industry was an early adopter, so source code is a pretty big part of that and r and d. But, really, again, not only does it cut across all industries, it cuts across all functions within a company. So source code, of course, that would be the development team and r and d, but sales and marketing, files. So things like strategy documents or customer lists or forecasts, corporate messaging, health records, HR and employee records, certainly for manufacturing, things like graphics, CAD, design, etcetera, financial files, and then sort of everything else that would be bucketed as other. So really, again, cuts across the entire enterprise and shows just how widespread this adoption has been. And that it's not just one group within the company that is handling sensitive data that's potentially exposing that or potentially handling it in a risky way. It really cuts across the entire company. So then we took a look at, alright, what kinds of apps, what kinds of AI solutions are they sending that data to, and then how risky are they? So something we'll show you in a little bit is this AI risk IQ that we've put together to analyze how risky the apps are. And, again, we saw some pretty interesting findings, potentially somewhat concerning. So almost a quarter had critical risk, meaning the way that they handle the data or maybe they train their models on that data or the way that that data might be accessible to other people. There's a few, versions of that, but critical risk and then half of it high risk. So you've got basically three quarters of all the AI apps being used that are risky in some way. Right? So they don't have the enterprise controls in place. They don't have, the SLAs, the things that you would need to make sure that they are safe, secure, compliant with the handling of data. And, again, this is probably indicative of employees just seeking a way to use AI to be more productive, to advance the mission of the company, to just get the job done. But it means that there needs to be potentially some guardrails on how they're doing that and steering them towards some safer usage of AI. So to kinda marry a couple of those stats together, no surprise then that the the majority of enterprise data, so breaking this down by how much of that data is risky, how much of the apps themselves are use are risky, you've only got about 16% of, that data going to enterprise ready apps. Right? So it's the corporate version of a chat GPT or Gemini or Perplexity or something like that. Really, most of it is going to probably personal accounts or ones that have just not been vetted by the organization. It's a big, what we would call shadow AI problem. And so those are some really interesting stats. And so taking a step back to look at that, then we really kinda boil this down into there are a few big challenges around securing data in this new AI era. The first is that last one I just talked about, the, identification of shadow AI usage. Alright. So just having an understanding and the visibility into what is being used today. Who is using that data? Who's using those tools? What is in the environment? This is very analogous to, if you remember, you know, ten, fifteen years ago when it really started to shadow IT sort of concerns. Right? When you had the rise of cloud, SaaS apps, and employees were using those, again, in furtherance of productivity and supporting the company's goals, but doing so with tools that maybe are not fully vetted and not fully approved for usage. So then there's sort of the two way movement as well. So, of course, there is the challenge of egress. So where is sensitive data going? And is that going into AI and making sure that we protect the sensitive data that might be going to some of these risky tools? But then going the other way too. Right? If AI is becoming a bigger part of our workflow and data is flowing in and out of AI, and there's this derivative data and fragmented data that is coming out. Well, then we need to track the AI generated material as well to understand how it's being used in the enterprise, how people are consuming that data, if we're making business decisions based on that data. There's a lot of things that we have to consider and look at, and having an understanding of where that AI generated or rather where that material came from and if it was AI generated can be pretty impactful. So that's kind of an overview of the findings that we had from this report. I encourage you to go to the website, download the full thing. It's about 20 or 30 pages. There's some other really interesting insights in there, and you can dig into that data. But so looking at that, then we also looked at, okay. Well, what kinds of controls can we help our customers with today? What can we put in place to help them understand that shadow AI usage, understand the data that's moving to and from their AI tools, and how risky are those tools in their environment. And so that's where we put together a solution that we're sort of altogether packaging up as security for AI. And this goes above and beyond the existing controls that have been in Cyberhaven for a long time around monitoring the use of data and where it goes and whether it's going into a personal or corporate chat GPT and other generative AI account, things like that. But to cover four big areas. So the first of all is that shadow AI discovery. So the visibility into what you have. Then there's the AI usage insights. So not just discovering it, but understanding how that data is flowing. I mentioned earlier also the AI risk IQ. So understanding how risky some of those apps are and what is the risk that they introduce potentially into your environment. And then the AI data flow control. So for customers today, this is gonna be, capabilities, everything that we're wrapping up into security for AI. This will be available in the twenty five dot o seven release, so available very soon. So I'll run through just a quick overview of each of these, and then I'll hand it over to David to talk about some of the other things that we're doing with AI at Cyberhaven. So the first element of the security for AI is the shadow AI discovery. So very simply, this is going to uncover the AI that's used by employees. And so what it does is it goes and creates this exhaustive registry of AI tool usage, continually discovers new ones as they emerge. And the goal here is we're gonna give you the visibility into not only the standalone AI tools, but also the embedded AI functionality within some of your existing SaaS applications. So if you think about many of the, SaaS applications that you use today, they're adding, you know, an AI assistant or a Copilot or something like that that is integrating AI to make assistant or a Copilot or something like that that is integrating AI to make that data store smarter. But that's something that you need to be aware of because it's a potential egress channel. It's a potential source of information. You wanna have some visibility into which of those applications are gonna have that. And, you know, again, we really believe that the visibility you get here is the foundation of an effective AI governance program. And you could sort of think of it like we're answering that critical question, what AI tools do employees use in our environment today? Right? That's a great starting point. Now once you've done that discovery, that's where we get into the AI usage insights reports that, again, will be out very soon on AI adoption. And this is gonna look at it from three perspectives, the tools, the data, and the users. So our research team analyzes data from millions of, users to identify those AI usage patterns, and we've incorporated those findings, things like you saw in the, AI adoption risk report, to help you understand the tools that are being used today and the usage patterns today and whether those are risky or not. So we can also identify the most active AI users across the organization. So in this example, on the screen here, you can see Emily Johnson. This is all, of course, anonymized demo data, but Emily Johnson stands out as a critical risk user. And in this case, she's accessed risky AI tools like DeepSeek and Better GPT, and perhaps more concerningly, is regularly sharing PII and other sensitive data with these tools. This is a great example of where you might wanna see, like, there could be employees that are handling sensitive data. They have access to sensitive data. Again, maybe they have the best of intent. They're trying to do a better job by using some of these tools. But the way in which they're doing it could put the organization at risk, so it's a great opportunity to identify that, reduce that risk, and be able to move forward and actually safely enable that kind of productivity by introducing some safer tools. So to that point, the next big element of security for AI is this AI RiskIQ. So AI RiskIQ creates this comprehensive risk profile for each AI tool, and it assigns risk levels from very low to critical for every one of these tools. So that risk evaluation framework evaluates the risk of every tool across five key dimensions. There's the data sensitivity and security, the model security risks, the compliance and regulatory risks, the user authentication and access controls, and then finally, their security infrastructure and practices. So each risk profile will include a very clear human readable summary that articulates each dimension and the strengths and weaknesses on that dimension. So you can further drill down to understand, you know, how we constructed that risk profile, where we obtained the source information, and what you might need to be aware of in terms of whether that matches your organization's risk tolerance or it's something that you wanna take action on and remediate. So how do we bring all this together? Well, we've got our AgenTic AI engine with some pretty deep research capabilities, and this is powered, basically, a proprietary risk scoring system that incorporates all of these. So it enables your teams to make those informed decisions about which tools can be safely used, for which kinds of data and which kinds of workflows. So you'd be able to get that granularity to drill down into the usage, the risk of the tools, and be able to align, again, your risk appetite with that usage. So then the final thing I'll mention on the AI our security for AI is the AI data flow control. So you remember back to that early that first graph where I showed, we've got an exponential increase in data moving to AI but also from AI. It's become a big part of enterprise workflows, and AI data flow control monitors and controls that sensitive data moving to and from the AI tools. So it's gonna utilize our core reimagine DLP and IRM technology to inspect the data, interacting with AI. But with this feature, the security teams can access, or can rather apply policies based based on each tool's risk profile. So using the data from that AI risk IQ I just showed, you can use that to help prevent sensitive data from being shared with high risk AI systems. And the same approach that prevents sensitive data from reaching the AI tools can also be leveraged to stop AI from revealing confidential information to unauthorized individuals, right, into this world of fragmented and derivative data, understanding that flow and that control. Again, the data going to and from AI is super important. And so we're giving you the visible visibility tools, to be able to see that, identify it, and then take action on that. So to that point, I'm gonna hand it over to Dave, who will talk a little bit more about Linea AI, which some of you may have heard of, but some of the ways that we use AI to help you protect that data. So, Dave, I'll advance the slides for you. Just give me the word and, perfect. Will do. Yeah. Thanks so much. Yeah. So let's talk a little bit about how we, Cyberhaven, are actually using AI within our product to help, discover previously unknown risks as well as it helped make your review of all the risks within the platform, as quickly and efficient as possible. So, yeah, Cameron do it on the next slide. So as quick background, we set out about a year ago to start kind of innovating and do research around how can we use air in our product to primarily address, you know, these two use cases, these two challenges that we've heard repeatedly from customers. Right? First of one being, right, we know policies can have blind spots. The only we know to look for the rules and terms you've used to define them. And so you have these hidden risks, these truly unknown unknowns. And so we wanted to investigate how we could integrate AI within our product to autonomously monitor all events coming in and surface, risk that you may not have known to look for. I'll talk about how we're doing that. I'll give you some examples about here in a second. That was one of the core challenges when we set out a year ago, in building this AI capability. And then separately, we also wanted to address this challenge where we know teams have limited time. Right? SOC teams often run lean. They're often, you know, you know, managing multiple different security consoles, so their time is very limited, when they go in and wanna do the triage and review of the incidents. And they really wanna know which ones are the most important. And when they investigate a particular incident, they wanna quickly get the context of what happened as fast as possible to kind of, you know, speed and aid, in in that delivery and in that time it takes to review it. So, again, I'll talk about how we're using AI. I'll give you some examples here in a second, to really address that challenge. So on, next slide, please. And so what we've done is we've developed Linea AI. It's a product that we've we've released about six months ago, and we call it this AI agent for superhuman insider risk management. And in particular, there are three really powerful benefits that Linea provides. First of which being it helps customers resolve incidents faster. We've actually measured from customers as they've adopted Linea, and we've seen a five times faster incident resolution process By using Linea's automated severity assessments and natural language summaries, they're given quick prioritization of which are the most important incidents to review first. And when they review that incident, they have all the context of what happened in that incident in order to make the decision about what to do next. And I'll show you example of that here shortly. Secondly, Lenny can also help you detect unknown risks. Alright. I mentioned this challenge of, you know, policies only being as good as the rules and terms that are used to define them. You have these hidden risks, these truly unknown unknowns. We use Linea AI to, you know, automatically detect risks that you might not have known to look for. And what we've observed from customers that have started to use Linea AI is up to 40% of the high and critical risk that they see in their environment were uniquely captured by AI. Right? That to truly kind of, you know, underscore that there are these, you know, hidden gaps, that that they may not have known to look for. And I'll show you some examples. I'll talk to you about how that works in the next slides. And then lastly, we don't just wanna create, you know, more incidents, with AI detections. We wanna pair that with the capability to reduce the total number of incidents that require manual review. And so we have a capability, that allows you to, only, generate incidents when AI has truly validated that the particular event is a higher critical, risk even when it matches your existing policies. And what we've seen from customers that have used that is they can reduce the total number of incidents that require manual review, by over 90% by using that capability to still allow them to define the rules, but having AI validate that those particular events, are truly your high and critical risk. And so next slide. So I'll just talk a little bit, in in-depth about how the AI detections work. Right? It really takes advantage of the fact that, you know, Cyberhaven is collecting, lineage information that we can use to build a semantic model of what are what is an expected, you know, workflow within a given organization. And how that could work is imagine on the left side of the screen here, we have this kind of, you know, notional data flow where the CFO creates this executive equity or document, shares it with a corporate accountant who downloads it as an Excel file, and then they go and copy and paste from that into Telegram. Well, we have built a model for that customer using their historical lineage data to truly understand, you know, what is expected, in that environment as far as, you know, natural workflows and what might be an anomalous or suspicious workflow. And so given the context of this flow so far, every event that Cyberhaven is collecting, we're analyzing through that model. And we might say, you know, in in this case, given the context of that flow that John, now that he has that downloaded Excel file, might upload it to corporate storage. That would be very expected. He might email it to other executives. That would be expected. But given the context of that flow and the kind of history of what, you know, we've observed in that in that environment, copy and pasting that into Telegram would be, very unlikely and therefore anomalous, and require further investigation. But we don't just want to surface these anomalies and then require the kind of customers to do that further evaluation. We actually can do that itself within the Linea AI products. On the next slide, once something is flagged as an anomaly, we kick in a more thorough analysis of that event where we are looking at the source, the destination, the full flow of the lineage, including insights into the content to truly validate whether or not that was a higher critical incident and then therefore create it, within your incidents table and and and, you know, encourage you to review that manually because we're we believe we've, you know, identified something that may have, been missed by your policies, but nevertheless would be higher critical. And so you can see here an example of that natural language summary. It gives you a quick explanation of what happened. I will show you on the next couple slides actually more live screenshots from the platform to see what that looks like integrated within the product. So next slide. So this first use case here is really just helping with that incident prioritization. So if you look at the top here, here are two incidents side by side that are essentially the exact same workflow. Alright? The user took a screenshot within their corporate device and uploaded that image to their personal webmail or unsanctioned webmail. Now just looking at the event data for that, these will look, you know, nearly identical. Right? It'll be an image file, you know, upload the personal webmail. If you're on a Mac, they're gonna be, you know, named exactly the same than the default screenshot application. So it's really hard to kind of differentiate between these two and understand, you know, what might be the highest risk if this occurs a lot in your environment. And in practice, this this does occur a lot in customer environments. But we can see here on the left there, Linea AI has already done its severity assessment of these events, and so it can you can distinguish between that first one being a high risk and the second one being a incredibly lower informational risk. And how did it do that? Well, we're looking at the the content here, giving an example because the one on the left is a, you know, AWS architecture diagram, right, that had all these infrastructure details, security measures, development testing, production environments, etcetera, and that was going to personal email, that does represent a higher critical risk. And Linea AI automatically did that, review for us. It, you know, generated that severity assessment. And before we even, you know, needed to view or preview the content there, it wrote that natural language summary so that we can, you know, immediately prioritize the highest severity risk first. We can open up the details, get that little, you know, one sentence, two sentence summary there. We know exactly what happened. If we wanted to view the content and we had it, you know, captured within the evidence bucket, we can do that as well. But it's performing that analysis for us automatically, right, as these events are coming in. And then just compare that to the complete other end of the spectrum there on the right. It's just the cat meme that the user took a screenshot of and then uploaded it to their personal email. We already saw from the severity assessment that it was low. We can just read that quick, summary to be, you know, to validate why we believe it's low. If we ever wanted to view the content, we could do that as well. But this is what, you know, what we're really getting at when we talk about the, the efficiencies, that our customers can see as they adopt Linea AI because they can prioritize which ones are highest risk first. And then in reviewing each of the details, they get this, you know, quick concise summary to help them fully contextualize what happened in each one of those incidents. Next slide. And then just to show you an example of AI detection. Right? So in this case here, right, Linea AI identified this event that did not match any existing policy and might have previously gone unnoticed with the, you know, volume of data that was collected, and service this as a potential high risk, for the customer to review. And, again, here, you know, we have, from the incident table itself, that first little, you know, snippet of screenshot at the top that's giving you the information to say this is the highest severity of risk. Because it didn't match any existing policy, Linea AI is actually trying to contextualize what it believes would be a a notional dataset or policy name for that. And then then it it's similarly giving you that natural language summary to give you that quick explanation to say, this is what happened. This is what was in the data, and this is where where it was going. Collectively, that is what, you know, led it to the to believe that this was a, you know, truly high severity risk. All three of these examples, by the way, just to note, you know, they are you know, in this case, you're just doing images. It's full you know, it would do it just as well for text or, you know, you know, data, you know, sheets or, you know, cell documents or any other, type of files being moved. But just wanted to highlight, the images once here in the in the, you know, for the slides. I believe, Cameron, that might be it for me. I think we'll be back next in the q and a and Yes. Hear from people on the call and, answer any questions that we can. Yeah. That's right. So if you have any questions, just drop them into the, the q and a little panel there. I see there's a few that came in, so I'll start going through some of these, and we've got a few minutes that we can go through those. So, David, first one will be for you, related to Linea AI. So the question is, are customers able to tune or train Linea AI AI models, for their particular orgs? For example, does closing an incident with destination not at risk, tune or white list that destination from triggering it in the future? So I know we've got a few ways that we can sort of tune things. Why don't you talk about that? Yeah. Great question. Right? So, you know, right now, the the way Linear works, I talked about, you know, how we, you know, we build that model with historical lineage within the organization. We actually retrain that every month, right, because we wanna, take into account any recent changes in the environment and, you know, keep an up to date view of what is, you know, the expected workflows, within the environment. There is capability to provide feedback to our team. Right? As reviewing incidents, there's a kind of, you know, mark as incorrect option, that that helps provide feedback to our team. On that particular question about, you know, closing incidents out as, you know, being valid or not valid and how that can help retrain it, that's on our road map and that's that's that's, you know, that that's areas we wanted to to address because we we do wanna get those signals from customers, around, you know, how they are, you know, evaluating incidents and how that might, you know, change what we might, how money might evaluate in the future. Not currently, being done yet, but if we do do that automated training, so we're constantly getting, the kind of expected workflows within the environment and having that an up to date knowledge, and we are working towards, you know, more of that kind of direct, you know, user feedback that that that you might give, you know, through your actions, like, closing incidents out. Very good. We'll take an easy one next. So how do you enable Linea AI for an existing customer? We'll reach out. We, basically, we'll chat with your CSM, so we'll connect with you. We can enable it, for a trial and and go into it deeper from there. Okay. So one more question. Let's see here. Okay. So question for you, David. How can we enforce block policies for incidents generated by Linea? Can it block it in line, or can we convert a Linea finding to a policy or dataset? Yeah. Great question. It's currently the latter right now. Right? So, you know, the the primary goal of Linea, you know, initially is just servicing insight into, you know, risk that you didn't know to look for previously. The process for Linea detecting these incidents is a slightly asynchronous process. It could take, you know, two, three minutes, for the AI severity assessment to to come in, which is not, you know, currently fast enough, support blocking actions. And so what we recommend and kind of what we, you know, have a position, you know, the the value of money detect is that it's surfacing, right, areas of risk that you may not have been aware to look for. And then we absolutely, you know, would like to see, you know, if that is is, you know, a area of high concern for you, then you can adopt new policies, update existing policies that turn that into blocking actions. And that kind of, you know, step from starting with the Linea detection and then manually updating, you know, policies or creating new policies, we're We're actually working too on our on our road map to, you know, automate that to give you that kind of, you know, you know, further kind of AI suggestions around, the appropriate next steps, which could include, you know, creating policies, updating existing policies. Very good. Here's a a good one related to linear and in general. So has this POC been used on obfuscation techniques as well, I e, PDF with sensitive data being hidden within? So if I'm understanding the the question correct, the then the answer is yes. So one of the things that is really valuable about the underlying core technology we have with data lineage is that it is not just looking at or rather just relying on the content inspection element. So because we know where that data came from and maybe how it's been modified, the file has been forked, copy pasted, etcetera, over time. If we identify sensitive data early on, then even if it gets into, let's say, a renamed file or another part of a file, as long as it's identifiable as sensitive data at some point earlier, so So even if you encrypt that file, etcetera, then we still have that lineage and therefore the knowledge to know that that is sensitive data. So I hope that answers the the question. We can follow-up offline if there's a more specific case. But, yes, that is one of the major advantages of data lineage is that many of the, let's say, most common, obfuscation techniques that you might use to circumvent a traditional DLP. Well, they don't work with Cyberhaven because we have that lineage. So we it's not, something you can get around. Let's see. Maybe I think we probably got time for one more quick question. So Dave on Linea. So the question is how to make sure that Linea is correctly correlating with lists and excluding exceptions while detecting? Got it. Yeah. I mean, that, you know, that question, you know, sounds like potentially from a from a customer that might already be using Linea AI or or or or or or POC in Linea AI. Yeah. We you know, there you know, just for background for everyone else, there there is a capability within Linea AI, the exception side where, you know, you may, you know, know certain situations where you don't want, you know, AI to be, you know, potentially, you know, alerting on incidents or just even, you know, reviewing those incidents. And a common use case for that might be I mentioned how we retrain that model every month. But there could be, let's say, you know, some, you know, subsidiaries or partnerships or maybe acquisition talks underway, that are, you know, at the early stages. And so the model doesn't have, you know, a good understanding of that. And it's seeing legitimate, you know, sensitive details go into, you know, new or, you know, previously not seen in in high frequency external domains and and will, you know, will be, understandably concerned about that. Might be triggering incidents off of that. And so, there is a capability. You know, you can use exceptions, kinda similarly the same rule, you know, definition that you can do with datasets or policies to say, you know, don't, you know, generate Linea AI incidents when, you know, things are going to this domain. Because I know I've just started talking with this company last week, and it's, you know, that we might, you know, acquire them. And so we're sending them sensitive data, and that's okay. And so there there is a manual capability to kind of fine tune and, it kind of restrict things. That does support the use of lists. And so certainly, you know, if the user has, you know, good questions, we're more than if there's, you know, issues they're running into, if they're using Linea already, we'll be more than happy to kind of, intake take that offline, and we can go into detail and and and take a look at their environment and make sure it's working. Yeah. That's great. Okay. I think we are well, I'll give let's do one more, and then we're probably at time. We'll follow-up with some other stuff. So, one more on Linea AI. So can Linea AI capture the interactions using a personal account as well? And then the follow-up to that is, can the product capture the interactions in mobile devices? Yeah. Two great questions. You know, I'll I'll kind of, you know, answer them separately. So that that first question, absolutely right. And so, in fact, all the examples, that I showed there, at least the first two examples, were files that were uploaded to personal webmail. And so we're able to look at the acting user information or the signed in account unit information of the, you know, the, you know, g in my case, to the Gmail to determine that it was a personal Gmail account and not a corporate Gmail account. And, understandably, the risk assessment that Linea would do would be completely different, right, if it was uploaded to a a corporate account, because it'd be staying in a corporate environment versus if things were uploaded to personal accounts. And so that is, you know, part of that evaluation, the fair the severity assessment that Linea AI does is looking at all of the the lineage information that Cyberhaven is generating to include information about the acting user, to, you know, help, you know, tell apart, right, the kind of, you know, personal use case versus a corporate use case, as well as looking at the content. Right? Because, you know, no one cares about cat memes going to personal web mail. They do care about, you know, corporate sensitive information going to personal web mail. On the question about can it, capture interactions in mobile devices. So I'll talk about more broadly kind of unmanaged devices, and where, you know, some of our, you know, recently developed capability, on cloud sensors as we continue to roll out, you know, more, you know, cloud sensor integration can really help that. So OneDrive is the great example right now. You know, we we just recently, you know, released, you know, really powerful OneDrive cloud API sensor, and it can detect, you know, data movements from OneDrive to unmanaged devices. And Linea AI can actually do, you know, surface, you know, AI detections for that where it will see, you know, if there was a, you know, what it believes is right, you know, sensitive data, through its, you know, AI analysis going to an unmanaged device, that can be, you know, by itself, in in in in in AI detection, that was serviced. And I forgot. I mean, it might have actually been let me go back and look at the oh, no. So they had, I was I was, you know, I was creating the slides yesterday. There was a couple different examples I was using. I thought maybe that, the AI detection example was actually an unmanaged device, but I just looked right back now and it was, to a generative AI service. But, that you know, it absolutely can can can do that. In that case for OneDrive, we're rolling out, you know, you know, you know, further cloud API sensors for, you know, for SharePoint and Google Drive and others that will support that same capability as well. Awesome. Thanks, Dave. Yeah. We've got some really exciting things that are coming up that we'll be talking about, along those lines publicly in the next month or so, so stay tuned for further updates. We're gonna end it there. I know there's a few questions we didn't get through, but we'll be able to follow-up, individually for your individual use cases. So the last thing I'll leave you with is just in general, if you want more information on some of these product capabilities that we showcase, or more information on Cyberhaven generally, access to the report, etcetera, feel free to to get in contact with us. If you're a current customer, contact your customer success manager. If you are a partner or we're not working together yet, we'll follow-up, because we'd love to start that conversation with you. So I will end it there. Thank you so much, everybody, for joining. Hopefully, this is really informative to you. We're gonna be trying to share a lot more insights from our Cyberhaven Labs team, on a more regular basis because there's really some cool stuff that they're coming out with. So with that, I'll leave it. Thank you very much, and, everybody have a great day. Thank you.