Video: Meet the Ransomware Response Team: See How to Streamline Recovery Across Identities and SaaS Apps | Duration: 3532s | Summary: Meet the Ransomware Response Team: See How to Streamline Recovery Across Identities and SaaS Apps | Chapters: Welcome and Introductions (7.44s), Team Introductions (96.08s), Webinar Agenda Overview (192.315s), Ransomware Response Team (303.485s), RRT Engagement Process (478.64s), Scalability and Detection (637.1s), RT Service Overview (798.405s), Incident Preparedness (943.82s), Preparation and Resources (1137.46s), Rubrik Security Cloud (1434.62s), Anomaly Detection Application (1631.925s), Cyber Recovery (1834.02s), Threat Hunting and Monitoring (1980.185s), Sensitive Data Protection (2320.135s), Recovery Options (2664.59s), Agent and Identity Protection (2937.76s), Recovery Warranty (3207.775s), Closing & Thanks (3337.35s)
Transcript for "Meet the Ransomware Response Team: See How to Streamline Recovery Across Identities and SaaS Apps": Everyone, if you've already joined, just give us a few minutes. We will wait for... We'll give folks a few minutes to join in and settle in. So, just give us a few minutes. We'll get started shortly. And in the meantime, if you don't mind, just let us know where you're from, where you're joining us from. Usually, I'm in Palo Alto based out of our headquarters, but I'm in San Francisco this week for Microsoft Ignite. So in case you are in San Francisco, you are at Microsoft Ignite, come by our booth, and say hi. Get some swag. Talk to us. Get some demos as well. Oh, East Coast. Pittsburgh. Nice. Yes. I like Florida. That's, like, my favorite state. Okay. I know we get a lot of questions. So in the interest of time, I'm going to get started. We are just one minute past ten my time, so probably, one minute past wherever you are. Okay. So let's get started. So good morning, good afternoon, depending on where you're joining us from. Thank you for joining us, to meet the ransomware response team. We'll take the hour to cover a lot of details, and here for any q and a. But let's dive in. So quick introductions. My name is Alpika Singh, and I'm a senior technical marketing manager at Rubrik. Been here over five years, and I cover everything that is customer facing, technical in nature that goes on the web, demos, webinars, our SC enablement, lot of, lot of other things that are technical in nature, for our SaaS, AI, unstructured data, and databases. But I have worked on other products, so plenty of experience about other products as well. So if you have questions regarding other realm of, Rubik products, do let me know. And I'm here with James. James, why don't you introduce yourself? Thanks, Abhika. Just first a quick, bit of gratitude to everyone who's taken time, another busy day, to, be here with us today. Thank you very much. I hope you find some value in this presentation. With that, I'll give an introduction. My name is James Knott. I'm a director of support here at Rubrik. I've been here just over nine years now, one of the founders and leader of our ransomware response team process and a couple of other things here at Rubrik. Thank you so much, James, for that introduction. Moving on, just a quick agenda. So James will walk us through the entire ransomware response team process, how you can engage with us, what the team does, what can you expect from the engagement. And it's really important to know this before you start engaging so you know what to expect. So, definitely lots of details to cover. Then I will get into, an RSC or Rubik's Security Cloud demo, touch into all the security apps we have, which is, you know, most commonly used by our, by our SaaS admin, so Microsoft three sixty five, and other admins as well. So our applications are common for all the workloads we support. We will focus on m three sixty five today, but just know that, it's common for everything. The process doesn't change, be it any workload. It will still the safest... It will still stay the same. And q and a. People love to ask us questions, so I'm expecting the same from this, this webinar as well. So, do ask us questions. We actually sometimes pause if if, the questions are relevant to the slide or what either James or I are talking. We pause, and, we take the q and a. So we want to make it super interactive. The goal is not to, like, just go through the slides and give you all the information, but to answer your questions. So there's a q and a tab left... Oh, sorry. Right inside of the screen, right next to the chat. So, please do, put in the questions because both of us will be monitoring the q and a tab as well. With that, I will hand it over to you, James. Great. Thanks, Topeka. Hey, folks. So before I talk about the ransomware response team or RRT process for short, just a quick bit of history. How did we get here? So as mentioned, I've been here with Veric for just a little over nine years now. It was probably the last couple of months of 2018 where we saw a couple of these attacks come in. And these immediately piqued our interest from the support side. You know, they were unlike anything else we were used to dealing with. And and we really wondered, were these gonna be something we needed to pay attention to? Were these here to stay? And clearly, as going into 2019, it was very obvious that these were here to stay. They were getting more numerous, more sophisticated, more severe. And since that time, we started building process and procedure here in support on how we dealt with these attacks, how we assisted our customers through these attacks, how we, you know, what what we learned from these attacks. And we've been doing it since that time. And as of 2021, when things really started to get bad... Or I should say 2020, it was probably about mid twenty twenty when things really picked up in terms of just the sheer numbers of attacks, the increasing sophistication, the pervasiveness of the threat actors. Just everything kind of went sideways. We took a step back here from the support aspect, and we said, what do we need to do to keep pace with what's happening in the world today? How can we better assist our customers? How can we keep pace with what's happening? And through that brainstorming section came the development and deployment of the ransomware response team process in early twenty twenty one. And what RT is is it's not a separate team. This is actually a Rubik process and overlay, fully powered and delivered by Rubrik support. And what we do is we we create virtual teams for each and every customer incident. And key members of these teams are incident managers, senior support staff, so that's gonna be support engineers, escalation engineers, even dev engineers when they're required. One thing to note is your Rubrik account team will be a very integral part of these virtual teams, as well as members of our executive leadership team. And that's not to say our executives are the ones pushing buttons and pulling levers, but since the very beginning, going back to 2018 and 2019, they were very keen on understanding what's happening with these customer attacks, what's really transpiring down on the ground. So by their request, by design, and I don't ever see it changing, they're a part of every virtual team that we create. When a customer opens up an incident with us and we we assist that customer. And next slide, please. So RRT, how do we engage? So as mentioned, RRT is a Rubik support process. So there's no additional phone number to call. There's no web form to fill out. Nothing like that. You simply open up a Rubik support case. Ideally, you wanna do this by telephone to get an engineer on the line who can immediately begin assisting you. And just mention any of the keywords, ransomware, cyber attack, hack, compromise, anomalous, or suspicious behavior. All of our support engineers are trained on this process. So in... Any of those keywords, any mention will immediately begin them starting their process. They're going to notify their management, and, subsequently, we go ahead and spin up the RRT process. So once again, very simple engagement. Simply open up a priority one case calling your regular Rubik support number. And what we do from that aspect is we're all about, incident management, urgency, continuity, communications, and confidentiality here on the Rubrik side. These are top of the pile highest priority for us, and I wanna touch on confidentiality. So one thing to note is currently, as of today, we're managing, eight of these concurrently. And even internally, we keep these strictly on a need to know basis. So for instance, say virtual team number one, helping customer a. They may know nothing about what's going on with virtual team two, helping customer b. We certainly never breathe the word of any customer incident outside the company unless they were to do a public testimony for us and you would see it on our public website. So confidentiality is extremely important and essential, for us here at Rubrik as a whole. And what we like to do when we get engaged with the customer, when a customer opens up that support case, help, I've been attacked by ransomware, I'm undergoing a cyber attack, we immediately wanna get on the war room call. We wanna understand what's happening. Who are the key players on both the customer side and any other third parties, incident responders, security vendors, other technology vendors, we want to openly partner with each and every one with the common goal of getting our customer back on their feet again as quickly as possible. And we do that by complementing our customers' recovery plans and their priorities, you know, keeping that first and foremost in our minds. And one thing to note is as this is a Rubik support process, there's no additional cost, there's no additional SKU, there's no additional license. You simply need an active and valid support contract. There's a question here, and it's it's it's an important one. It says, doesn't that limit your, capacity to track issues at greater scale, or do you de identify the issue after action review and dissemination to the broader team? And I and I see that question, Opika. Let me read that. just so I can try to understand. So in terms of greater scale, I I do wanna talk about that for a moment because that's a question that comes up frequently. So people ask, how are you able to, attend to, like, say, like, a mass casualty situation? And as mentioned, we're able to do this by being a process and overlay of Rubrik support. So all support engineers are trained on the process. All of our support managers and customer experience managers are trained on the process. And. I hope that answered your question. And that's question from Mike. Right. And I will advise you all to use the q and a tab if you don't mind. Just a reminder. Yes, But... Yeah. please. I like... Yeah. And like, James mentioned about, like, you know, g... Like, we want to complement what recovery plans, what customers are doing. So just wanted to touch base that, you know, when Rubik backs up your data, be it Microsoft three sixty five or your hypervisor databases, You know, what we do is basically take your current backup and, compare it to your previous backup to look for a lot of changes in your data. Like, we have a lot of algorithms, ML algorithms that are built into the platform to look for any major changes. So it could be, like, massive deletion events. Like, if you don't encrypt your data, there's an entropy event, things like that, if there is that ransomware note. So we have a lot of tools built into our platform, to give you visibility as to what's happening with your data. We do it using the backup data. If there are any active threat actors, they are not aware of that you are actually looking for malware or if you're looking for ransomware. They don't go and just detonate all your data. We are cautious, but we do give you that information so you can take quick actions, quick decisions, and essentially complement... It complements with all the exist... Existing security tools you have. I'll give you a demo, but I will let, James continue as well. Thanks, Topeka. Sure. And a further clarification on the question, it makes it sound like for privacy purposes, you have silo teams. Who is coordinating to assure that a problem at agency a isn't the same at agency b? So there's a subset of folks, myself included, who are engaged in all situations. And it's not just a a one person. There... There's there's a number of folks, at the support, leadership level, who are actually engaged in looking at all incidents concurrently. And if we do see anything that, perhaps correlates one with another, we certainly, communicate that as as appropriate. Oh, yeah. I need to change the slides. Sorry. Okay. So RT by the numbers. And just to kinda reiterate one of the last, a point on the last slide. So from that initial engagement call, from when a customer first calls us requesting assistance, we are there at the highest priority, from the beginning until the end up until our customer declares recovery. Everything is back to normal. Business is operating as as it should, and we can disengage. Yes. So from, that first inception up until our customers are covered, we engage, really until you tell us to go away. So as we are Rubik's support, 24 by seven by three sixty five coverage, for all customers with a valid support contract, immediate response in the sense we get a question, well, what's your SLA on response? If you call in, you'll get a live engineer on the phone who can immediately begin assisting you at that point in time. Zero additional cost, As mentioned, just having a valid support, Rubrik support contract is all that you need. We've been doing this for over five years in the, official RT capacity and several years even beyond that just as from a Rubrik support perspective. And as mentioned, a unified virtual team and, you know, just touching back on that question for individual customer engagements, but also folks looking at if there's any larger picture, any kind of overarching things, we're also looking at that as well. And just to reiterate the RT Charter. So we're there to complement and assist our car... Our customers' recovery plans and their priorities, working in lockstep, with them. One thing to note, we get this question pretty frequently, is does RT assist with any, anything in in in regards to, say, tabletop exercises or runbooks or planbooks? So from the RT perspective, from that process, we do not. We are strictly reactive only, right of bang, if you will. An analogy we use frequently is think of us as, like a medical analogy. Think of us as the hospital emergency room in ICU, so life saving medicine only. Once again, confidentiality is extremely important to us, both during and post incident. Once again, we're looking to partner with all involved teams, both on the customer side and any third parties that are involved in the mix. That makes for the most efficient, and most really meaningful engagement and recovery process. And once again, we're there from the beginning until the end. So we're always asked about preparedness. Question that comes up really in every conversation, what can we do to be better prepared? And the answer is it's in the question. Really, it's by actively, taking that step to be better prepared. So two things. One is nobody knows when the attack will come, how it'll manifest, what'll be the impact, all the infinite variables in terms of responding to and recovering from said attack. But the one thing all of our customers have in their, in their capabilities is being actively prepared for an incident, and that's developing a, comprehensive incident response and recovery plan, testing that plan, really putting it to the test in in terms of actual practical application of going back to the tabletop exercises. What worked well? What didn't? What took longer than expected? The human element. What teams maybe had a a need for a interaction or dependency that wasn't thought about? Learn from those, recalibrate, test again, make it muscle memory. Establishing a relationship with a reputable cybersecurity vendor. We partner with Mandiant, CrowdStrike, also Sophos, but we've worked with all the big ones, most of the medium sized ones, and many, many small ones, and there's many good ones out there. But, really, the gist of this is having that security vendor already on retainer, already in your pocket. They understand your business. They understand your recovery needs and priorities. And when you need them, they're already ready to go as opposed to trying to spin one up, from scratch, you know, when you don't have a relationship. That takes... We've seen a minimum, and I mean an absolute minimum of eight hours. Usually, it's more like twelve to a full day, and that's just time wasted. Exactly. Certainly... I think you... Jits. Say again, Opika. No. No. Go ahead. Certainly leveraging everything on our Verbrake support portal. So not only from a regular just normal day to day support perspective in terms of managing your support cases, opening cases, all the all the, information and documentation that we have, training videos. But in terms of the cyber context, we have many good documents for security hardening, best practices, white papers. Certainly take advantage of all that documentation up on our portal. Nothing is gated. Once you have access, you have access to everything. This information is always regularly reviewed and maintained, and it's highly recommended. So take advantage of it and use it and apply it in your environments. And certainly, leading up to Yalpika, making sure you have the tools, the rubric tools at your disposal, to be able to effectively respond and recover from an attack. Exactly. And, like, you know, James mentioned, get with your team early on. Like, if you have an exam, you don't just go give the exam. You have to prepare for it. And you test yourself before the... An actual exam. In this case, you never know when the situation arises. So you need to be doing this very regularly, testing it out, making sure, all the important personnel details are correct, if people have moved on and people change their jobs. Right? Like, the phone number changed, email address changed. Anything like that, you need to be aware of and you need to document it. So it needs to be built into the plan because when that cyber attack hits, you don't have the bandwidth to figure out who you need to call or who you need to reach out to. Right? So it's important that all your steps and everything is ironed out. And like James mentioned, we have tons of great resources on our Rubik's support portal. Now this is a gate gated portal. I will mention that. But as a customer, you have access to all of this information. So we, update all the best practices very frequently. There's like a start, you know, how to get started with the recovery plan guide, things like that. So even if you're just starting and if maybe you are a new, person on a new team and you just want to check if the existing plan matches what we have or, you know, take the best of both worlds. So, it's a great spot to get a lot of information. And then, of course, our tools, we will get into that, shortly, but it's important that you use. There's one question. I think it's important that we answer this now, James, if you see it like the, what role does the sales portion of the team play in the recovery process? Yes. That's a very good question. So this is not to say, your Rubik sales team is gonna be doing anything with with regards to the recovery process. What their participation is is they are are very familiar with all the key players, there on our customer side. Not only, the technical context, but also the leadership, folks as well. So they really just ensure that everyone is communicating well on, the customer side, making sure there's no breaks in communications, any silos, and, of course, all the while, showing all the care and concern of our customer who's really suffering through what really could be the worst day of their lives, professional lives, I should say. Perfect. Thank you. I will move on. Oh, just a couple of more things. So for the security folks in the room, you may roll your eyes. That's okay. It's it's worth repeating. Protect all your administrator accounts, Rubrik and otherwise, with, multifactor or pass keys. Certainly don't make it any easier on the threat actors. And, really, from the Rubrik support side and the RRT process side, if you see something, say something. Open up that priority one support case. Even at that moment, things are still indeterminate. We want to listen. We wanna learn. We wanna understand what's happening. And in the event we have to act, we're already up to speed and we can act quickly and efficiently. And if for some reason it really turns out to be, nothing at all or something very small, there's no harm in a false alarm. So, certainly, minutes can matter. Rubrik may not be your very first call, but it should be one of your first two or three. Perfect. Thank you so much. And with that, I will take you into the demo aspect. Okay. So as a customer, what you are entitled to is our SaaS platform, which is called Rubik's Security Cloud. Every customer gets it. And what does it do? It's a centralized management plan, for all your Cloud, SaaS, identity, and, on prem workload support. So all the protection, all the security apps, different things, you can do all... Everything from the big security cloud. That's the best part of it. We have a lot of SaaS apps other than other than M three sixty five. So Google, Jira Exchange, we just launched PowerPoint as well. Your entire Microsoft three sixty five ecosystem can be protected via Rubrik. Same thing for Cloud as well. We do have support for Azure, AWS as well. From data center perspective, all your databases, your hypervisors, we just announced support for Azure Local. Think about it like your entire Microsoft ecosystem can be supported. That also includes AD and on Friday. It's like one stop shop for all your backup and recovery needs. Like I mentioned before, once we do the backup of our objects or your m three sixty five objects, what we actually do is compare the current backup with your previous backup, and it's like a multi stage process. So one stage could be actually analyzing and looking for any major changes, like things getting deleted, and the other stage could be looking for ransomware note, entropy, and things like that. And, you know, just because a file was deleted, we won't flag it. Over a period of time, Rubik's, the algorithm actually learns about your network, what's normal, what's not. So it will flag things which, it will flag incidents that, it thinks that it's it's not normal behavior. So on this dashboard, you will get an overview of any anomalous objects, if there are any hunts, if there are any threat monitoring hits, things like that. Next one is the data security posture. This comes in very handy. So this is basically analyzing your backup and looking for any sensitive data, where it's located, who has access to it, and if, you know, if there are any open access, if if suddenly access changes, things like that. So we we, want to make sure that you don't have any sensitive data exposure, if you have a ransomware attack. So we want to make sure that we tell you where your sensitive data is. If it's not locked down, you can then lock it down before you hit any exposure. Of course, orchestrated recovery, this is where you track all your recoveries if there are any recoveries ongoing in your environment. I'll kick start with Data Thread Analytics. Now like you see, there are anomalous objects. I'm going to click that and it will take you to our application called anomaly detection. Now, like I mentioned, we support different workloads. Right? So you will see, that there are different hypervisors. There's Kubernetes. There is unstructured data. There is, m three sixty five as well. So, now that is supported for your on dry... OneDrive and even even for your, emails and things like that. So I am going to quickly just do a file share, which is very similar to... Okay. What happened? Yeah. Which is similar to what you get in OneDrive. So you will have a very similar looking result where the object type is going to be a SharePoint or OneDrive or email. Right? Exchange. It'll tell you where it's located, if there are any anomalies, like if there are any encryption, like in this case, it's LockBit, it will show that to you. So if you click into the share, it will tell... Give you a summary of, when was this first detected, what is... Which snapshot it detected it, if there are any ransomware node, how many files that are suspicious in nature and other things like that. It will actually give you the list of all the files, with location as well. If you dive in deeper into the folders, it will tell you exactly the folder so you can see how many suspicious files things getting deleted in different files and folders. Like here, what you see is that, the... There was a doc x... Several doc x files. They were deleted and they were encrypted with a log bit encryption and then added it back. Now this is the level of detail we can provide you. Like if you want to do a simple recovery of just the deleted files, you can click on Recover. What you will see here is that there's a snapshot that is already selected. Now this snapshot is basically non anomalous, meaning there is Rubik identifies a snapshot that is clean in nature, and you can, essentially recover it as well. But, of course, we are not asking you to do that. There's a lot of sanitization checks that happens before you do your recovery. This is where you work with your existing cybersecurity vendor, work with our other tools, which I will get into in our RRT team before you perform any recovery as such. What I wanted to talk to you about is also, the ability to, actually do a cyber recovery. I'm going to just do clear. Now what is a cyber recovery? You know, a lot of times when you're dealing with hypervisors, you've been asked by your SecOps team that they need a clean room environment, where we... They can test, the... Either the snapshot, for recovery or even for their analysis, on the malware itself. Now if you just think about it, the amount of time it will take you to actually, you know, figure out what is clean, what is not clean, and other things like that, it can take hours. If you're thinking about several virtual machines, like hundreds and thousand, it can take you days. But what Rubrik does is it makes that process very simple. You select either a snap, a, virtual machine or several and just click on Cyber Recovery. What it will do is that... I'm just going to just run through quickly. Now by default, it will tell you a non quarantine and non anomalous, but it can actually give you a snapshot that is anomalous in the nature as well. Like you said, like you see that I just changed the outcome and it automatically selected the snapshot that is anomalous in nature. Like if you need a non quarantine, it automatically selects a clean snapshot. If you just want to do further analysis on the malware itself, you can actually just select all the compute resources, give it a network which is isolated, give it a name and just kick start data copy. I'm just showing you for one virtual machine, but think about it, if you are hundreds of virtual machines, it can take you days. But Rubrik can actually simplify that process and bring it down to seconds. That was one of the other tools I wanted to touch on. Then yes, Threat hunts. Now, threat hunting is like the name suggests, it's actually hunting for threats across your entire backup infrastructure. Now when I say entire backup infrastructure, now I'm talking about your entire SaaS app. Microsoft three sixty five itself has different workloads. There is OneDrive, SharePoint, Exchange, Teams, things like that. Just four of that workload itself is huge. But now I'm talking about your virtual machines, your databases. Rubrik has the capability to look for threats and hunt for it. I'm just going to select about threat hunt and I'm going to search for threats using hash values, but you can use Jira rules as well if you like. I'm going to select all your eligible data sources. This includes everything that will be protects. I added one file hash, but you can actually add all the way up to 100 file hashes at the same time. Give it a name, and then you can do different time ranges. Just know that if you're selecting all your snapshots, it's going to take longer. So if you have already narrowed down, the time range, for your... When when the event has happened, You can even, do custom time range and it will obviously, be completed faster. Give it a name, which I did, review all the details and kick start. And that's it. Ruby gets to work. I do have one selected here. There's, like, M365, but I have one that was... Yep. So in in about three minutes, basically, the threat hunt, scanned over 800 objects, and it also has identified all the objects, like 101 objects, and then what can you do with it? It gives you all the information, how many snapshots are affected, which was the first snapshot where they found the malware, which is the latest snapshot where they found the malware. It gives you all the share details, where it's located. You can actually quarantine your share as well to make sure nobody accidentally recovers from that snapshot as well. So there's a lot of capabilities built into, the the threat hunting capability. Now this is a very passive or, like, approach where you already know that, like you are affected and now you're looking for threats. To make this a proactive process, what Rubrik is now supporting is threat monitoring. As soon as a backup happens, Rubrik actually will go and scan your backup to look for threats. Now, what threats are we talking about? Rubrik actually has a threat in Tel Feed. By default, it's Mandiant, Google Mandiant, but it, also gives you the capability to add your own custom feed, thread feed... Thread in Delphi. It can be coming from maybe CrowdStrike or another vendor you are partnering with. So once we have the threat feed, Rubik scans your backup and looks for that, threat. Now I do have to point out that the... These threats are not... That was prevalent ten years ago. These threats are essentially that is most common, right now, across the world. Like, there are a lot of zero day, threat also, and the threat feed is, feed is updated multiple times in a day. So, as soon as your Microsoft three sixty five workload backup completes, we'll look for that thread and tell you if there are any active threads. Like for example, you see, like, there's a s three bucket and there is a threat or there is a hit for that particular bucket. What you see here is that it will tell you which files it's matched to, all the observed snapshot. Again, very similar to threat hunt. It will give you all the information. You can, again, quarantine. It can also give you all the IOC details. It will tell you, where it's... What the threat intel sources. Like in this case, it's CrowdSite. So it can be your own, custom feed as well. So with that, now let's move on to... So... Yeah. This is our... Essentially our active or, aggressive way of looking for threats before, it hits your... All your workloads. You know, it started with m three sixty five grade, but we don't... We want to contain that threat. So this can, come in very handy to identify threats early on in addition to your other tools as well. Now we'll move on to data security posture. What does it do? It's looking for sensitive data across your M three sixty five workloads. Again, it is supported across pretty much all our other workloads as well. The way this works is by default, there are lots of analyzers that Rubik has built that is looking for sensitive data, different sensitive data. Like for example, we have, analyzers to look for Netherlands patient numbers. You know, the way patient numbers are defined, it's different across the globe. So, anything that complies with HIPAA or your personal information, we have analyzers to look for that sensitive data. You can actually create custom data type as well and map it to a data category. The name, medium, maybe. And then you can use either a regex or dictionary word, or phrase to search for your sensitive data. And we understand that every organization is different, so we have that capability built into it. Now, these data, analyzes map to categories. So... Sorry. For example, like, we have, you know, prebuilt, data categories to look for CCPA or business or financial data or HIPAA. Most common ones across the globe, we have it listed here. And these, categories will have certain number of analyzers mapped to it to give you that information. You can, again, like, create your own custom data category also with your own predefined or, custom, analyzers. Once basically you figure out which data category to use, you apply these data categories to your M365 workloads and other workloads. As soon as a backup completes, again, it scans the backup to look for sensitive data. Let's head to Object Inventory and let me do a filter to show you some Microsoft three sixty five data. So, essentially, it will tell you, that maybe there's a... There's an individual in your company that has a lot of sensitive data. Now we're talking about 2,000,000 and all the data categories, where it's located, and if it has any open access, things like that. It'll give you that information. If you want to dive in deeper, you can select the object. It will tell you exactly where it's located, all the data categories it's mapped to. Now Abigail must be an important person because it literally has a lot of personal information like ranging from financial to HIPAA. Maybe this person is from HR. But what you can also track is that maybe this person is from engineering and out of the blue, this person got, access to all this sensitive information. So it's important that you track this, and what can you do with it. You can actually download all these information. And if you are, looking at a cyber incident, this can help you with sensitive data exposure or if it's a regular day and you see any HIPAA violation. You can download that... This information and give it to your team, to make sure this person has the right level of access to the right amount of data. So Rubrik protects, helps you, you know, safeguard your data at rest. We've also partnered with DLP, data loss prevention vendors such as Zscaler, to prevent your data loss in flight. How does that work? Once once we finish all this sensitive data analysis, we can actually tell Zscaler or any other DLP provider that, you know, in this wide estate of data, Here is the sensitive information. Here it's located. It can be in Cloud, it can be in database, like your m three sixty five estate and things like that. We will provide that information to Zscaler. And from the Zscaler UI, you can actually set up policies to prevent this information from exfiltration. Right? So if somebody is leaving, they can't take your sales, leads and just upload it to their personal Google Drive or they cannot email it to themselves, things like that. So we also help prevent your data loss, when it's in motion as well. And now with that, I'm gonna pause and see any questions so far, James, or good to go. Alpika, there's one question, maybe some more information regarding data classification. Oh, yeah. Sure. So essentially, let's go to data classification. So I'm not going to show you how to create... Okay. So... Okay. Let's do that. So you can actually select five, like, how many ever, sensitive data types or analyzers you want. You can create a new one, and then, it can actually be linked to any document type. So it it can identify what the different document types are, and then just give it a name. Once this is done, the way it works is that, you select the data type and you assign resources to it. So either you can do it by cluster. So for all your on prem workloads such as your databases, hypervisors, you can just do it in one go. And otherwise, you can actually do it by object type. How does that work? So here, we break it down by the object type. And here, I can either do more... Assign it to my vSphere object or my unstructured data or my, Microsoft three sixty five. So I can select the subscription to which I want to, do this, you know, look for, the sensitive data. Again, like, I can do multiple at one time and then once I hit assign, it... The the data category will be, applied to the subscription itself. So as soon as the backup completes, Rubrik will then start scanning your backup to look for, that sensitive data, that matches CCPA, and then provide you with the breakdown like you saw before. Hope that helps. Again, like, I just wanted to touch base on one more thing about recovery options. You can always do recovery from from from the workload, but you can also perform recovery, from the anomalies section itself. It can be for, like, a single virtual machine or a single single file as well if you say for OneDrive. I am going to see and click on Recover. Okay. Sorry. It's a bit slow. Like, you can see that, it can actually give you a snapshot. You can change the snapshot. I'm sorry. This is... This one doesn't have much data. Just select this one maybe. We did my dentist. Okay. Yeah. So like you can see, there's the analysis of all these snapshots. And if I'm trying to do a recovery, it selects a snapshot which is labeled as November 16 at a particular time, and it is clean in nature. By default, it has identified all the snapshots that are either anomalous in nature or clean in nature, but it will select the most recent clean snapshot. Again, do your testing before you do the recovery, but there are multiple options for recovery as well. In place recovery, you can export it to another cluster, same for databases, same for OneDrive, lot of options built into it. And with that, I'm gonna pause. Did I miss anything, James? No. I don't think so. Okay. Awesome. Thank you. I will come back to see if there are any questions. By the way, great question. And, thanks for asking us to go deeper on certain section. It really helps us, to make it more interactive. Okay. In the interest of time, I'm just gonna go to the next slide and just touch on a few products. I'm just gonna build up the slide anyways. A Rubrikation Cloud. Now we talked about, you know, all the cyber resilience, and how there are different options for you, to figure out what data is good, what data is anomalous in nature. Similarly, we want to have, a similar, monitoring capability for our agents because agents are everywhere. So our Rubik Agent Cloud, it's our newest addition to our AI portfolio, where with this product, it's a standalone product. It essentially can monitor all your agents. We work as a gateway between your agents and your LLMs. All the calls that goes to your LLM, it goes via Rubrik Agent Cloud. So we are able to monitor and see what these agents are doing. We actually have policies to govern these agents. So if you have read only tools, that should be only reading the tools and not making any updates to your Salesforce CRM or deleting customer information, things like that. We can actually block these agents from performing those actions. Or if you're not comfortable from blocking, if you want us to just monitor them, we can do that as well. And we have extended this to our agent identity... Agent identities as well. So we tell you all the information about which, identities these agents are using for performing actions. So we give you a holistic view of your agent tech, world as well. And not to mention that we have the capability to rewind or remediate, Yes. if if there are destructive actions. Now this comes, this option of remediation is available to our customers only and only if you are backing up your data with Rubrik because to rewind, we should have the capability to access the data as well. If you're backing up the through break, especially with your Microsoft three sixty five estate, your Copilot agents can just do a lot of destruction. There are several incidents. I'm not going to touch on that, but we do integrate with M365 and essentially recover all your data for your Exchange, OneDrive, and things like that. With that, one more thing I wanted to touch on is the identity resilience. I did mention that we protect your Entra ID and AD. It's not just protection where you do backup and recovery, and even Okta for now. We actually tell you, what, your identities are doing. So if they... Again, like, if they have certain permissions and they're... They have escalation in their privileges, we are able to, detect that risk. We are able to see what configurations they are doing if they are changing anything, and that are malicious in nature. Like, for example, where, you know, if if an identity has now gone and, updated the policy from where you can get emails, who you can send it to, things like that, all the domain controls. And if, somebody is doing that, we actually track it, all these misconfigurations. And as an admin, you can, take action, before you have widespread, identity crisis. Right? So an identity is the forefront. If if people have, your... Some... Like an identity that is compromised, they can get access to all of your data. So we help you safeguard your identity. It's a separate SKU, like all our other workloads, but we have lot of capabilities built into that. So the... Real quick, can you please show the one's navigation to anomaly screen for recovery? Essentially, you just click the object and click recover. That's about it. Yeah. Ransomware response, warranty. This is this is the best, capability, I think, or or warranty that's out there. It's for $10,000,000. As a customer, the way you qualify is that you do have... You you must have Rubrik Enterprise Edition licensing. So there are different, tiers of licensing. If you just have Foundation Edition, you do not... You're not eligible for recovery warranty, you need to have Enterprise Edition. That means you need to have access to our data analytics, our data security posture, capabilities. Once you have that and you're following data security best practices, such as enabling MFA. James touched on that, like just having that MFA, rule based access control. And it's not just for your Rubik, but across your entire organization. If you're following best practices, you're updating and adding all your patches to your operating system, things like that. You are eligible for the 10,000,000 warranty from Rubik. And, James, I'm gonna let you talk about our customer resilience manager aspect. Yep. Certainly will. Thanks, Topeka. So, yeah, folks. The two real basic requirements are Rubrik Enterprise Edition and, also subscribing to our customer resilience manager, now called TAM, technical account manager, because they're gonna be really the steward, to help you and ensure you're following all security best practices, you know, in general and from the Rubrik side. So those two are essential, in terms of being able to apply for and attain the ransomware recovery warranty. Awesome. Thank you. And with that, I am going to leave you with a lot of resources. Again, like these resources, we have it for other workloads as well, but we are talking a lot about M365. We have a very cool capability called Autonomous Business Recovery. I'm just going to talk about it. Essentially, Autonomous Business Recovery is recovery option for a subset of your users. Rubrik in the background basically identifies what these users have accessed in the safe past seven days. It's not all the data, but it's what they are actually working with. We recover that first and then do all the other data recovery in the background. Why do we do that? This is to get your users back up and running quickly. Then also there's so much API limitations from Microsoft, how much APIs anyone can consume. We do not want to waste these on stale data. We are trying to recover the most recent data that your users are using and then help them get back up and running faster. With that, I'm going to pause and see if there are any questions. If not, thank you so much. And, you know, it's Thanksgiving time. So also do want to reiterate that thank you for taking the time and spending the hour with us, asking us great questions and making this super interactive. We have lots of other webinars on deeper dive topics as well at a workload level. Join us for another webinar or join us for another RRT's session. Every time we try to change it up and make it different demos, maybe we go deeper on a topic. So, thank you so much for taking the time and listening to us and asking us questions. With that, I think we can go offline. If anything, reach out to us for any questions. Thank you all. Thanks, everybody.