Video: Cyber Recovery: Your Cyber Resilience Guide to Protect, Detect, and Recover | Duration: 5480s | Summary: Cyber Recovery: Your Cyber Resilience Guide to Protect, Detect, and Recover | Chapters: Introduction to Workshop (7.04s), Cyber Recovery Essentials (367.22s), Preemptive Recovery Engine (785.12s), Identity Resilience Solution (1239.6951s), Identity Alerting System (1425.9401s), Anomaly Detection Systems (1548.21s), Threat Monitoring Automation (1789.13s), Advanced Threat Hunting (2020.76s), Recovery Plan Execution (2317.2148s), Cyber Recovery Options (2539.945s), Threat Containment Features (2843.05s), Lab Overview (3184.355s), Q&A Session (3561.915s), Disaster Recovery Planning (3645.125s), Concluding Lab Instructions (3962.31s), Concluding Remarks (5417.225s)
Transcript for "Cyber Recovery: Your Cyber Resilience Guide to Protect, Detect, and Recover":
Hello, everybody. We're gonna give everyone just a couple of minutes to, get joined in here and make sure nobody misses anything. We do have a very packed agenda to for today's rubric workshop, so we are going to start here in just a minute or so. Okay. Looks like we got a good number of people. So I think I will go ahead and kinda get started with some quick housekeeping type stuff, and then, we'll start diving into the content. So this is a Rubrik workshop. Specifically, we're gonna focus on cyber recovery and how we can, as Rubrik, help our customers to get back to a clean, productive state after a cyber attack. So we're gonna cover a lot of territory because there's a lot that we we bring into that. It's gonna start with probably about forty five to sixty minutes of, slides and conversation. Don't worry. Those are pretty technical slides. As a technical marketing manager, I've created a lot of these slides myself, and my colleagues have. So we'll we'll get into the weeds pretty pretty heavily here. And then we'll transition at the end of that to, what we what we call a virtual lab. It's it's a self guided it kinda has all the prompts in there to walk you through our interface and see what's going on within it to be able to actually experience it for yourself. So that's that's a pretty it's not a live environment, so there's there's not a lot of things to fail for you. But that could potentially take you some time. So we'll talk more about that once we come to the end. Most likely, you are going to go beyond the hour and a half we have scheduled for this, to go through that lab. So we've we've given you some time to finish that. I'm very big on asking questions. This is gonna be technical, so, your questions are very, very welcome. I have several places where I'm gonna pause and look at the q and a. So as questions come up, feel free to, plug them into the q and a box, which should be on the right of your screen. Those will get in. They'll get triaged by the team on the backstage for me so that when I get to those breaks, I've got some questions ready for me. So don't hesitate to throw those in there. If I happen to answer them after you ask them, that's fine. We'll we'll just discard those questions and and move on past those. So please make it interactive. It makes it much more interesting for me, and and it gives you the answers you need fairly quickly, and and makes it much more interesting for you as well. There is also, you'll see in the, chat section, over there by the q and a, you know, we'll we'll provide some information in there, links to, the the virtual lab, for example. There'll be, you'll see a pop up for, feedback at the end, which I look at. I I really treasure any feedback people have. Please make it productive so that there are things that we can do to, make this better in the future would be great. I love positive feedback as well, so it's good to hear that you did well. So I think that's all of the main housekeeping items. Again, if you have any questions about this platform or what's going on, drop those in the q and a, and and the team will will answer those on the backstage as well. So with that, I think we'll go ahead and jump into, our actual content here. So, my name, of course, is Brian Knudtson. I didn't say that upfront. I am a senior technical marketing manager for Rubrik. So one of my jobs is to help communicate how our platform works, how it can, bring advent advantages, to all of our customers. And in this particular, we're gonna talk about kind of the whole what happens when a cyber attack happens and what Rubrik will do to help you, to get past that. So with that, let's dive in, and talk about, you know, the thing we all dread is seeing. Hey. You you got hit by ransomware. However that pops up on on your radar, it's it's never a good feeling. It's something we're all kinda sitting there waiting for it to happen, wondering what's what's when's it gonna hit? At this point, most of us are not asking if it's gonna hit. Most of us realize at this point that this is something that's hitting the biggest companies out there that have the money to protect themselves, and and shouldn't have these gaps that allow ransomware to get in. But we all know people are fallible, and and they're getting in. So if failure is inevitable, then what should we be focusing on? For for me personally, and and and Rubrik has this philosophy as well, is first off, we gotta reduce the risk. So this is our defensive posture. We gotta make sure that it's harder for them to get in. We have to minimize the impact. Assuming they're gonna get in, what can we do to prevent it from being a bigger crisis? And then finally, we need to optimize recovery. We need to get back up and running as quickly as possible. And those are all critical. So we really look at kinda this equation of risk plus impact plus recovery equals cyber resilience. And that's how I like to define cyber resilience. Of course, it's big buzzword these days, but it's it's really focusing on those three things. And and each company is gonna focus on different parts of that at different points. It's important to mature over time. So, you know, do what you can to shore up any of those and then move on to the next one. There are three nonnegotiables when we talk about cyber recovery. As you're recovering from a cyber attack, what do you need? First off, you need to have backups that are going to survive the attack. We are seeing more and more cyber criminals aiming for destroying the backups. They get harder to recover so that they can get their ransom. And then actually having infrastructure to restore too. So it's very possible that your production environment is now questionable, that you look at that production environment, you say, I can't trust restoring. Even if I have backups and I know they're clean, if I recover it into that same production environment, they're just gonna get hit as well. So, you know, the net result ends up being if you don't have those things, you just can't recover, and the business is probably gonna suffer immensely from that. Secondarily, the ability to find the clean copies of data. Cool. We have all of our backups. They're secure. They can't be touched. They can't be destroyed. They can't be, you know, vaulted out early, you know, reducing the retention or those types of things. I need to be able to tell what's clean, what's not clean. I'm going into an isolated recovery environment, a clean room, whatever it might be, so I can recover everything, make sure it's all clean before I open the doors back up to the world and and reopen the business, essentially. Because if you can't find the clean copy, you're just gonna reinfect your environment. And we've seen this time and time again. Change Healthcare is a great example. They took forever to restore because they kept reinfecting their environment every time they would restore something. Finally, the identity and data context, knowing what's going on in our environment, knowing what got exposed because, you know, every breach, we see, hey, customer email addresses, but no customer credit card numbers were were exposed in this attack. You need to figure that out, and there are time limits on on that reporting. So, you know, your compliance and legal teams are gonna want to know about that kind of information. So knowing that, knowing, what they maybe were aiming for. So you can do a digger digger analysis. Sorry. Dig deeper and do more analysis on those systems because those are the systems they're trying to get to to get that sensitive data. And, you know, what identities were compromised? I don't wanna restore an identity that, would provide a backdoor for that attacker to get back in. So how do we deal with that? How do we know which identities are most critical to our environment is is a super important aspect of that? And we'll talk about all those. I mentioned maturity. You know, the the easiest way to measure how mature you are is that you're constantly improving your ability to find that clean cyber recovery point and and having that objective of getting to it faster. On the other hand, you know, we're used to this RPO, RTO thing. On the other hand, we wanna get restored as quickly as possible. Now the challenge with the the the RTO, the recovery time objective in a cyber incident, is that it is far more complex than what we're used to in a disaster recovery type of an environment. So if we look at that timeline and what it takes to get back up and running, there's there's a lot. There's a lot to deal with here. Of course, you're gonna have a lag based on, you know, when the compromise started to when you get alerted to it. And and, you know, if you don't have enough, monitoring going on in your environment, things can easily slip through. We're starting to see attackers actually disable the, endpoint protection tools and being able to get into the environment and say, hey. You can't see me because I've turned you off, or knowing how to get around those things. Of course, when when you detect that there's something, you need to get the team together. You wanna have a, full team approach, generally speaking, when it comes time to do to to do those recovery activities. So getting them all together, you know, you wanna have a a solid plan for that. Then when you sit down and you're like, okay. What's going on here? You just gotta figure out what's going on. Where did they go? Who attacked us? What are they after? You know, can we can we shut down the environment so that they can't spread any further, get some more, exfiltrate more, all those things that go into the forensics aspect to figure out what's going on so that you know what you have to deal with. And then you start going through your backups. You start trying to figure out where that clean point in time is. And this is kinda what I alluded to before that really starts to stretch out the recovery ability and and that cyber RTO, making it very slow is is you could potentially take days to recover here. And I guess this is an important point to to note these times are are not standard. They're kind of the average of what we've seen from customers that it that we've helped respond to a ransomware incident. So your mileage may vary when it comes to some of these times that we talk about here. They really are just illustrative in this case. Then you go into a quarantine phase. So we've we've detected where they're at. We're gonna we need to stop them from moving. And this is both, like, actively in production as well as within your backups. So we've, you know, we've we've identified those clean points in time, which means we found which ones have, latent compromises in them. They've they've changed the password on that identity. They've dropped, their their back end their backdoor tools into that system. Maybe the ransomware has already been deployed in in that particular system. We need to quarantine those so that those never get restored into production again. Then we actually get to that point of recovery. And using all that knowledge that we've built up to this point gets us to that point where we can recover. And, of course, if you're doing things manually, if it's not orchestrated and automated and preplanned and all those things that we talk about with disaster recovery already in place, it's gonna take a long time to get things recovered. Even even in a large environment with it all automated, it's gonna take some time to get it recovered. So do you know what your minimum viable business is? What the what the minimum amount of stuff you need to get up so that the business can conduct their business. It may mean sacrificing some systems that are are secondary or helpful by, you know, hey. If our business is all about transacting with our customers, we need to get that transaction system up as quick as possible. Then we get into kind of the, preparing for next time and and reporting aspects of things, which unfortunately tend to be very at the end, and to be lengthy and and time consuming while the clock is ticking. And so knowing what we can do to stop it from the next time because, you know, any any good disaster is a good learning opportunity that we should take, into the next into the next phase. So this is this is a general there there are other things that go on in here. These are the things that we kinda see that that take a long time that that, you know, there's stuff that may fit in between these, but these are really what stretch things out. So how do we do a faster cyber RTO? The way Rubrik goes about this is to really kind of focus on doing things beforehand. What can we do in your environment ahead of time? So that when when everything's on fire and people are running around trying to do things under stress that you have less work to do. And so we focus on, you know, using Rubrik as a redundant monitoring system. We look at documenting and practicing your plan so that you know what's going on in your environment and and what needs to happen should should an event happen. Continuously looking through the backups that we are taking out of your environment. This all starts with backups for us. Whether it be cloud, whether it be on premises, whether it be SaaS, what can we do to see what's going on in the in that environment that are indicators of compromise or indicators of, you know, risky identities out there. And then using index the the indexes that we gather from that information of your backups to be able to hunt through those So very quickly then be able to say, hey. Here's where your backups are contaminated, which, of course, are an indicator that the production team can use to figure out what's going on there as well. And then being able to very quickly click a button, quarantine, and move straight into restoration of your applications. And there's a lot of stuff that we do ahead of time, which is which is really what we're gonna dive into is to show how a lot of this work is done ahead of time with Rubrik, so that there's less to do in the heat of the moment. This is what we call our preemptive recovery engine. And it's it's it's an interesting term that we spend a lot of time discussing, about how we're you know, what term to use there and and how we're going about that. And, really, it kinda comes down to two things. One, we're precalculating a ton of stuff. Most, ransomware, most malware is executable. So for every backup, we're gonna look at what new executable have shown up on this environment, what executable have been deleted in in this particular, object, you know, whether it be a virtual machine or a file set or a file server. And we're gonna look at that and say, let's hash that. Because one of the big things we use in the detection as an industry is hashes. Very, very pointed, very exacting as to, what a file is and being able to identify that. So we we take those hashes ahead of time, and then we're gonna scan through those hashes. We're gonna scan through the files that we index and saw on that latest backup and try to figure out, you know, Yara rules, file paths, and hashes to find those indicators of compromise and be able to alert you, hopefully, before they execute the ransomware and then lock everything up and then cause downtime. All of that then leads to this faster cyber RTO. By doing that prework, by by doing it preemptively and making sure, we get a good sense of what's going on in the environment and then use that information later on to, bring that information to bear. So that's kind of the setup to that. That that's kind of the value that that Rubrik brings. What we're gonna do now is really dig into the details of that and how we're gonna go about that. And we're gonna start with kind of that protection and mitigation. We're gonna look at, really kinda how do we reduce the risk and minimize the impact and ensure that we have the backups that we need to go forward. You know, Rubrik is focused on, having a zero trust architecture for backups to ensure that they are going to be there. I'm not gonna talk much about that, but know that, you know, everything becomes immutable. Everything is encrypted, both in in transit and at rest, to ensure that those backups cannot be manipulated by an attacker. It's been the strong focus for Rubrik from the very beginning. So that that is a bit of a unique value prop for us that there really is no way for you to configure it wrong for the most part. But making sure that, you know, the default is the the secure way, which is where we need to be as an industry quite honestly. So let's start by talking about, reducing the impact or minimizing the impact of an attack when it happens. One of the first things that we do is is look at the data access and govern that. This is an industry standard term. If you're not familiar with with the security industry, data access governance or DAG. Like I mentioned, it starts with backups. In this scenario, I'm gonna really be focusing on Windows files and the and the SharePoint and OneDrive. We do have other products that do support this. But, you know, this kinda brings together the whole picture of things when we consider the the identity side of things along with the data side of things, which is a huge huge part of what we do. So first off, what we're doing is we're gathering a ton of information just from these backups. We pull these backups in. We index what's changed, which gives us an index of everything that's going on at that point in time, both from your active directory, your Entra ID, and whatever files got pulled in through these. And being able to to understand information about who these users are, what groups they belong to, what what groups and people have access to a given file, what's in those files, and and really being able to a lot of information. So then the next step is to really evaluate it. This is where we start building knowledge about your environment. So identifying what's risky in your environment, to to understand what violations to your policies are going on within that data to say, hey. You've got a user who does not appear to have, who who doesn't appear to be in the accounting group. You know, they've they've got permissions elsewhere in the environment that have nothing to do with accounting. But at some point, they got added to this group. And and to be able to process that and say, finance people should only have access to this file that we've through document classification, understand to be a tax form. That might that might be a violation then that we that we bring up. And and this is where things really start to hit the road is being able to understand where data is in a risky scenario, in a in a risky position. And you can see a whole bunch of violations that we can find there. These are the built in stuff. You can definitely create your own policies, to then be able to put you in a position where you can take action. And this is what really matters in the end. Whether you're sending it off to a ticketing system or you're seeing SOAR platform, telling DLP, your data loss prevention systems. For those of you that, maybe are more on the the SIS admin side of things, who don't deal with the security team much, these are the tools the security team cares about. These are the tools that they use day in and day out. So being able to to provide them the information they need to secure the environment, as well as in some cases, being able to actually make changes in production, like to MIP labels. So if you're in a Microsoft three sixty five environment, the MIT labels is a big big part of that for being able to control access to things and and making sure that that things are properly secured in your environment. We We can identify, hey. This one doesn't have a MIP label or this MIP label appears to be wrong. Would you like to change it? Yeah. We go straight to M365, make that change for you. The next backup, we verify that that that got applied appropriately, and now we can eliminate that, that violation, that alert. Okay. And and I should add, this is all part of Rubrik's DSPM solution. Next up is identity. This has been a big push for Rubrik lately. Again, being able to to look inside of active directory, Entre ID. Just today, we announced our support for Okta as well as one of our identity providers. So this all starts with security analysts in your organization going in to Rubrik and creating policies. Again, using policies to define the overarching what we need. Then we pull in those backups from from the identity providers, pulling that into a central identity inventory. So we have within Rubrik one single inventory of all of your identities, both human and nonhuman, which is a big differentiator there as well. That then goes through the engine, applying the policies to determine what violations exist out there, and, again, take action on that. Whether it's to to remediate that change immediately. You know, there may be some GPO that got changed that you're like, woah. Wait a second. That shouldn't have changed. Based on our policies, we know that that's a change that, based on time, shouldn't happen or got changed to a scenario that that shouldn't be the case. Go in and remediate that immediately. Maybe you maybe you wanna track it. You put it in the ticket. Maybe yeah. We we did that. It's good. Dismiss it. Again, all of this potentially being fed to security tools, and and showing up in the the Rubrik interface, for for monitoring and management type stuff. This is all coming out of our identity resilience product, which you'll you'll see all of these in the lab once once you get into that. So that's the first place I wanna pause. That is kind of the how do we make our environment safer, and ensure that, you know, the likelihood of them getting in through a risky identity is less, or that if they do get in, which we have to assume is inevitable at this point, that the blast radius of what they could potentially hit is going to be diminished. So with that, I'm gonna flip to to my q and a panel, see if there are any questions that have been flagged for follow-up here. I'm not seeing any right now, so please pump those in, if you have any questions on kind of that before phase, if you will. Again, I will reiterate that the lab will walk you through how Rubrik does this, how you would manage this in a Rubrik interface. I don't get into with the lab deep into, kind of that connection to the security team's tools. Those are, we we've we've got separate demonstrations of those. If you wanna go see that to see how we integrate with Microsoft Defender or integrate with Cisco XDR or CrowdStrike, in multiple different ways, those those demos exist similar to what you will see at the end of the presentation here, in this kinda self guided click through type scenario. So lots of lots of information that you can gather from that. Not seeing any questions pop in here. So I'm gonna stop babbling and get back to the presentation so that you can get to the good stuff. Okay. So now we're in that scenario where you may not know that you've been attacked, but there is an attacker in your environment. So we need to find them as quickly as possible. Again, it's that first thing in that timeline that we talked about. How do we reduce the lag of somebody got into, we know about it, and can action on it? And then what do we do about that, the response side of things? So we're gonna continue with the, identity resilience, feature that that or, product feature add on, whatever you wanna call it, for Rubrik, which is identity alerting. So different than violations. Violations are kind of a a break to a policy that we notice through the backups. Alerts are actually gonna work in a, active more active more more near real time type of a situation. So today with active directory specifically, Entre ID is, you know, is is one that we're working on. We are going to through our backup agent installed on your domain controllers, we'll be sitting there constantly kinda looking. Every fifteen minutes or so, they're going to investigate, hey. What's changed? Using our normal incremental type approach to looking at from this point in time to this point in time, we're gonna look at what changed and then analyze those changes, again, against the policy engine as to what's going on there and say, hey. You've we noticed this thing. This user got added to a group. This group policy got changed, and and it's breaking that policy engine. So what can we do about that? Again, very easily gives you the ability to open up a ticket, to dismiss those types of things. We're not actively going to to change in this case, because a lot of those changes, you know, we don't wanna react too quickly, I guess, in in some of these scenarios. False positives are a thing. We won't deny that. So being able to to quickly get that alert and say something's going on. Generally, we say within thirty minutes, you're gonna get notified that this is a thing that's going on in your environment. So really, really cool feature set from that. Again, identity resilience. Next, we'll talk about anomaly detection. So at this point, they've executed some sort of ransomware, mass deletions, mass changes, mass adds of files. We we wanna detect those things. And this is happening at both a, can happen at not only a file level to look at a file system and say, hey. This file server had a bunch of stuff that changed on it, but also across virtual machines. Because what we're seeing more and more of the the vast majority of attacks that are happening over the last year or so have been at the hypervisor level because your hypervisor doesn't run endpoint protections. There's nothing sitting there watching processes trying to determine that something is happening in that environment to try to shut it down and stop it. Once if they can crack into that hypervisor, they don't need to go between virtual machines. They just encrypt all the virtual machines. Very, very, common with, like, scattered spider attacks. So as you can see, it's a two phase approach to things. So, going through this real quick, not necessarily intended for you to read all the slides. We start with, you know, the previous snapshot and the new snapshot that we just took, compare the metadata of what changed between those two, and then do an incremental diff. What is the difference that happened between those two things? That thing gets fed through a, a large language model, a machine learning model, to understand what's going on there and try to infer what happened there. At that point, we get a list of anomalies. This is a list of, hey. These are the changes that we saw. We're not really analyzing what the changes were, just that, hey. These mass deletions, mass additions, mass changes. We then feed that through Gen AI model that we've created specifically to look for false positives in this. We want to know and and that's the thing with anomalies is that they can be very false positive heavy, because a lot of things can change files in in a twenty four hour, twelve hour, eight hour period, whatever your backup increment is. So we wanna look for those those false positives. And from there, identifying, hey. These are the things that we think are actual positives and put those in the UI. Put those into, again, going out to, the SIM server or the source server to help the security team be able to react to that as quickly as possible. As a separate process, what we're gonna do is we're gonna take that anomaly list, and we're gonna we're gonna look at that to see if we could figure out what's going on, what what's actually happening in in those anomalies. And that then could potentially lead to us finding ransomware and adding this to, a tracking table that we that we have, that we manage internally as to what we think actually happened. That then goes into another machine learning model to investigate it and say, is it encryption? Are we seeing an actual ransomware event here? And, again, trying to trying to narrow it down so we get as few false positives as possible, give you as, clean an indicator of what's going on. And then that then goes into that same UI to say this was an actual encryption event. Not just a changed mass change event, but an actual And that's where we really are like, hey. We're we feel pretty confident that you have ransomware going on in your environment. This is all a part of our enterprise edition, specifically the data threat analytics side of things, specifically anomaly detection. So you'll see that we've we've done a lot of packaging of of different things in here. But, again, this is to identify to you something in your environment is actually going on. It's been launched. We've seen the effect already. Now working in parallel with anomaly detection is threat monitoring. And this is really designed for, again, part of data threat analytics, part of our enterprise edition feature set, being able to just kinda turn it on and let it do its thing. It it's very automatic at this point. Today, we automatically pull, using the mandate feed, the Google threat intelligence. We do some we we really focus on the high, the high confidence indicators of compromise that come through there along with any, indicators of compromise you add into that feed. We combine and send down to your into your Rubrik environment, whether that be cloud native, whether that be on premises with the Rubrik Secure Vault. It's going to get this feed. And today, it updates every twenty four hours. As you can see, it includes both Yara and Hash rules. So we're we're pulling in both of those because they, generally cover most everything that's going on there. And then every time a new incremental snapshot is created, you take that backup, it goes into the system, we're gonna run it through this threat monitoring thing. We're gonna check all those yara rules, all those hashes, and see if any of the changes that happened at that point in time are going to get a match. We're also going to do every twenty four hours today when that feed updates. If there are new Yara rules, if there are new hashes that come into that, we're we're actually gonna go back to all of the all the backups that you've taken previously that are still resident within the environment and check and see, hey. Do do any of these match? And that's really our our a way of helping to deal with zero days. And we have all those backups. We can go through, and we can do that deep analysis and search outside your environment. We're not hitting your production at this point. This is all within the backups directly. And being able to search for anything that may have been new added into the environment. Anything we find there, the metadata for it, specifically, like, the file location, which snapshot it was, which indicator of compromise it was, we put into a dashboard so that you can very easily see what's been detected there. The other cool thing is, as part of this process, we are hashing every executable and looking for those files in that backup. Well, if we take the time to do a hash, why not just throw that into a catalog that we can use later? That's gonna be a very important point as we move to the next thing. Again, this is all threat monitoring. This is automatically happening with every backup, with every new indicator compromise that comes into your environment to look for things that are latent sitting in your environment that have been added to a backup. So this could simply be, hey. We've, an attacker. Scatter Spider is really big at using identity to get into the environments. They're not necessarily dumping payloads immediately. Eventually, they're going to dump their tools. They're going to dump, some sort of backdoor, the actual ransomware that they're gonna utilize. At that point, we can find it in the backups and potentially alert you before they actually execute it, before anomaly detection finds anything, which is the ideal. But at some point, sometimes they pop, and and they get into your backups. And it's a zero day. We don't see it right away. But, you know, that new YAR rule comes down. We're able to find it, and we're like, hey. Wait a second. Something's going on in your environment. Or it's a true zero day, and we've you know, CrowdStrike sends your security team an announcement. Hey. There's this new thing that's going on out there. There's a lot of good information sharing that goes on in the security environment to be able to then indicate, hey. There's this new this new hash that you should be looking for. So now we wanna actually go hunt for it. We actually wanna go find it. And backups give us a really cool ability to then be able to go through, you know, the most recent backups. Maybe you decide, hey. We're just gonna take an on demand snapshot of everything in the environment, go searching for it at this point in time that we discovered that there is a new zero day that's out there. There are two ways you can go about that. One is to do a fast detection. This is really using, metadata, the index type data, or these hashes that we talked about on the previous slide. Very easy, very quick, very definitive ways to find what's going on in your in your backups or in your environment. This is actually agnostic to Rubrik. This is just general how do you find an indicator of compromise. The the the way this works is if you're not familiar with hashes is it essentially just runs it through an encryption algorithm, an MD five, a SHA two fifty six, and it creates this this string of of, characters. If you ever downloaded software and wanna check the integrity of it to make sure that what you downloaded was what was supposed to be downloaded, you you do an MD five hash to figure that out. So you give it a you give it a string, whether it's bytes or actual text, whatever it might be, and it comes out with this the string of gobbledygook. This comes through the encryption side of side of the industry. The downside with that is that it again, it is very exacting. If I make one minor change in that particular string or that file, the whole hash is gonna change dramatically. So it's a very exact thing. We know for sure we found this point in time that they compiled this. But if they take that malware and they compile it multiple times, the hash approach is gonna break, which means that we need to do a deeper analysis. We need to to actually look at the content itself. And and there's a bunch of different ways that that can happen. When I talk about Yara rules, that is kind of the domain of Yara rules, is to be able to say, here's a set of criteria if they match. You probably have an indicator compromise. Not as exacting, more prone to false positives, more prone to, finding things that aren't actually malware using these approaches. So the two work together. You know, you can't really have one or the other. Using hashes really is the more exacting way, and and especially when it comes to to finding something that you already found in your environment. CrowdStrike found this thing. It shut it down. Here's the hash for it. Go find it. Now you can know that you're finding that exact file throughout that, and you'll you'll see the rubric version of that in the lab. So two ways that we address this. The first is advanced threat hunting. This is the YARRA rule approach. As you can see on the screen, we can also do hashes. We can also do file patterns. Hey. Look for this particular file name in this particular directory. Some of these are faster than others. Some of these take a little bit more effort. But what, ultimately, we're gonna do is we're gonna go through the backups that are in the Rubrik environment and search for those. Again, similar to, very similar to threat monitoring when there's a new YAR rule that comes down through the feed, we're gonna do this completely outside your production environment. We're going to do this completely within within the Rubrik environment. This can take some time, though. So you you kinda wanna limit what what you're doing because it could take forever to scan through everything for every indicator of compromise. That then results in, you know, a a dashboard that shows, here's what we found based on the limits that you put around us to look for and the indicators of compromise. We found these things. The other side, turbo threat hunting is a really cool, newish feature, came out earlier this year, that allows us to utilize that hash database. So similar to what we saw in threat monitoring because it starts with threat monitoring, creates a hash catalog, creates a threat dashboard. What, Turbo Threat Hunt does is it's gonna go to that hash. So you provide Rubrik up to 10 hashes, for for an individual threat hunt, and we are now going to be able to go into that hash catalog. And instead of hitting backups, which you'll notice, that line doesn't go to the backups. It doesn't go to the threat threat feed. You are providing these copy and paste type type of a manner, and we're searching through that that catalog. It's just a simple database lookup, which means it happens really, really fast. And then we're able to dump those results down into the threat dashboard, same same type. It it's different places in the UI, and you'll see that, but very similar, dashboard that you'll see there. Now what we do with both threat monitoring and threat hunting is in that dashboard being able to say, hey. We wanna we wanna quarantine. We wanna contain these backups. And I'll talk more about the the details of how this works. But the essence at this stage is we found threats in our environment. We do not want these backups to get reintroduced into production. We wanna control the ability to, to be able to restore this point in time, so we wanna contain it. We wanna quarantine it. You'll see that how that works, in a little bit and, you know, what what it looks like within the UI here in a little bit. All this threat hunting stuff is also a part of data threat analytics in our enterprise edition. So these all work together. You can see how kinda entwined they all are towards helping you to be able to find what's in your environment and to to help, with the with the initial response to an attack. So that's kind of the during an attack, you know, how how are we dealing with an attack that actually happens? So another point where I'm gonna look at q and a. So if you have any questions about any of that or anything up to this point, please please plug those in. First question I'm seeing on here, what Rubrik products provide this level of recovery? So I'll talk about the recovery here in this next section, the actual let's let's execute a recovery plan. I kinda kinda listed as we went along, but I'll reiterate. So if you want that kinda deep analysis of your data, where the sensitive data is, and being able to, help to clean it up beforehand. You know, we wanna reduce the blast radius should somebody get in. We want to minimize, the the impact of a cyber attack. That is the realm of our, DSPM solution, which today, is most robust in the m three sixty five, use case where, you know, the most sensitive data is being created these days. We did a lot of analysis and found OneDrive and SharePoint are the places. Now, of course, not everybody is using m three sixty five to store their data. We we realize that this is this is a product that will continue to expand into other use cases there. A earlier version of it is available for cloud and on premises or enterprise workloads. So those those are available for for those products as well. Identity resilience is is our newest product. That is that ability to look at identities, to figure out which ones are risky, to help you remediate those things, to to look for life changes in in your active directory, in your entree ID, and be able to to help remediate those things, to very quickly undo those changes, to to clean up those risky identities. You know, it's very common for, if I change my job role within the company, I'm now you know, I go from IT to finance. Now all of a sudden, I have a whole new set of permissions. I have access to all this financial data that, as an IT administrator, I couldn't directly access. But if I don't clean up if if if the team doesn't clean up my previous access, I may still have admin level privileges across the environment. I may still be able to log in to the VMware environment. In general, I don't want the finance people to do that. And so now we're able to to help remediate that kind of stuff that may happen, gaps gaps in the process, if you will, that should be cleaning that up. And then all of the the anomaly detection, the threat monitoring, threat, threat hunting, sorry, as well as what we'll talk about for the orchestrated recovery piece are all enterprise edition. So the that's the level of of licensing you need to get to. These are all separate licenses that we talk about. We'll also talk about identity recovery here in a little bit. Actually, the the very next section. That is a subcomponent of identity resilience. So you can do identity recovery, or you can uplift that to identity resilience. So being able to recover is is the cheaper way to get in, but being able to make it more resilient to be able to have that, keep the environment clean and and reduce our risk in the first place is, the next the next level there. So that's the only question I've seen come in. So I will continue forward with talking about what we can do after somebody gets in our environment. We've we've we're now at the stage where, the ransomware has been executed. We know that we've had, you know, maybe maybe the ransomware hasn't been executed, but we know there's massive infiltration across our environment. 80% of our servers all have we've detected this threat, this this IOC on there. What do we do about that? So let's talk about kinda high level, and then I'll I'll narrow down as we go along our cyber recovery, our ability to do recovery of these backups. Obviously, you you have a per object. I just wanna restore this one file. I just wanna restore this one virtual machine, surgical type of recovery. We also have full recovery plans where you plan this ahead of time and you test it on a regular basis. We've got a lot of different options there. Not all of them necessarily apply to a cyber attack. So I'm gonna first off narrow down to these four, which are really the the most critical, to be used in a cyber attack. Now the two the two big, the surgical and and the planned side of things, what differentiates those two? Well, that's probably pretty obvious. One starts with a plan. One starts with, I'm going to choose in the heat of the moment which ones to recover. For cyber attacks, you can create different different types of plans. Assuming that, hey. If we have a massive outbreak, we're gonna have to recover the whole thing to a clean room, to an isolated recovery environment, whatever you wanna call it there, because we just cannot trust this production environment. We're just gonna isolate it. We're gonna shut it down. We're gonna leave it in place for forensic purposes, and we're gonna move everything over to this other place. It could be your Doctor location. It's it's walled off, so we know they haven't gotten in there, and we're gonna recover. We're gonna get everything up and running in it quick as possible. That's where a plan would come into play. On the other hand, hey. We just had one file server get attacked. They haven't spread beyond this one file server. So we're just gonna shut down that one file server and restore just that one. So being able to to only restore those affected files versus the entire environment or, entire applications. You know, a lot of times, your plans are gonna be based around an application. I need this web server, this, database server, and this application server. That's all I need to recover. Both types of plans can be run through our anomaly and quarantine filters, and we'll see that here in a little bit what that looks like. If I dig a little bit deeper, what differentiates, you know, the the two in each of those boxes? Very high level, starts with a plan, starts with a detected event either through the anomaly detection, UI or the threat monitoring, threat hunting screen. The process is more or less the same once you start there, but the perspective that you're looking you're looking at a blast radius is something that actually did happen versus just indicators of compromise. This is this is stuff we found in your environment. When we look at, how recovery happens vis a vis production versus an isolated environment, obviously, the only place where we're really generally going to recover on top of the original virtual machine is an in place recovery. In the other places, we're, we're gonna leave the original virtual machines as they are. Yeah. We may shut down those virtual machines to keep them from spreading. We're gonna restore a new version of it there. You could potentially delete and recover on top of, but it is technically kind of a new virtual machine at that point. And and the reason why that differentiation exists there is that for everything but in place, you're generally going to do a, live mount or an export. Live mount is, hey. We're gonna we're gonna expose that point in time through Rubrik and use Rubrik as the, as the storage for that virtual machine and then migrate it later on over to, over to the the virtual machine storage. Whereas an export is we're gonna copy the whole thing into your virtual machine storage and power it on after it's all copied. So there's a timing aspect between those two options. The in place is is by far the fastest way to recover, and the way that works at a very, very high level is we're going to scan the current state of that virtual machine. We're gonna look at the the snapshot that's chosen to restore, and we're gonna create a differential between those two and only recover those files that have changed between those two. We do that as a snapshot on the original virtual machine. So, you know, that virtual machine has to come down. A new snapshot's added to it. All those changes are put into that snapshot. You power on that snapshot. You wanna undo that restoration, that in place restoration, all you have to do is shut down, delete snapshot, you're back to where it was beforehand. Very high level. Then the final thing that kinda makes a difference here is that the, the isolated plans that we create are plans that can be run, either scheduled or on demand at any point in time. So testing is really the the thing there. I wanna test this plan over and over again. And we can schedule those to run into a a secondary environment, and be able to email us the results of that or go into the Rubrik interface to see the results of that. So every week we need to test it. Cool. Let's schedule that at 02:00 in the morning when we've got the resources. Let it do its thing. Shut it all down. Send us the report, thus showing how well automated it really is. Okay. So, again, this is all, coming from our cyber recovery orchestrated recovery platform, that is included in the enterprise edition. Now we're gonna move on to threat containment. So as I run these, these recoveries, all of them have anomaly and, threat or quarantine filters that we can utilize. What does that look like? In the act of doing a restoration, we have these types of, these types of interfaces that show, the screenshot at the top right. Here's all your snapshots that you can choose from. If you wanna pick a very specific point in time, has it been scanned? Has it has it gone through a threat, monitoring, threat hunting scenario yet? Have we found threats in it? Has it been quarantined or not? You could see that, you know, both the columns saying yes or no, as well as an indicator on the little, the little camera icon, if you will, will indicate that. And using role based authorization controls, we are able to prevent who has access to restore a quarantined or an anomalous snapshot. The purpose for this is really so that you can retain for forensic purposes snapshots we know have a threat in them. We've investigated. We know that there's ransomware running around inside of this. We know that there are tools that the hackers have thrown out there quietly that could give them a backdoor back into the environment. We don't want anybody to do this. In fact, I would recommend that any regular admin, even if you're a super admin, should not have those permissions. You don't wanna accidentally do that. If I'm gonna go into a clean room and do forensics on a known bad point in time, I'm gonna use a special account that has the permissions to do that and maybe only has permissions to do that in the isolated environment. Like, you could control it at that level. Super important there. Because as you go in there, you can very easily say, I just want anomalous. I just want quarantine. I just want non quarantine, non anomalous. I know I want a known clean state when I go to do that recovery. And if for a plan that maybe has 20 virtual machines in it, I can choose that filter at the high level, and it'll automatically pick based on a point in time. You'll see this in the lab. What level, or or what point in time it's gonna choose as the most recent non quarantine, non anomalous. And then if you want to, you can go in and surgically change those. Again, you'll see all this in the lab. This is all kind of the combination of everything. This is this is really where things come together that that really differentiates Rubrik to be able to say, we've done all of that preemptive recovery engine work to figure out where the things are so you can very quickly get to the point where they're quarantined or anomalous and be able to go in and do your orchestrated recovery very quickly. Given the fact, this is why that data threat analytics piece and the orchestrator recovery piece are both part of enterprise edition, being able to to have all of that in place so that, boom, it's ready to go. Okay. Final thing, and then I'll I'll start talking about the lab, is reporting. Obviously, reporting is a huge part of it. You're going to have to, report to the board, to compliance officers, to whoever it might be. There's reporting necessary. Even for yourselves, I need to know how successful a given plan was when it ran. So two ways this works through the UI on the left there, gives you very detailed step by step. As it's going, this is live updated as it's running through the plan. So you can sit there and watch it while it's doing its thing. Secondarily, you can, in the interface, click a button, download the report, and that's what you see on the right side there is is an example of that report. Again, a lot of detail there. What's the success rate? All that kind of stuff. This is also this this report is what would get emailed to you if you do a scheduled recovery. Have it automatically email me the report. You'd see this in your inbox the next morning. Final final thing, the ransomware response team, is a really cool feature that every Rubrik customer has access to. In fact, it's a virtual team across our support organization. So the people you talk to when you open up a ticket on the Rubrik side are most likely going to be the same people who are part of your ransomware response team. What it is is it it's a set of guiding principles that they then use. If you say, we have a ransomware event happening. Boom. There's there's a flag on that particular case, and all of a sudden, we we behave very attentively to you. We're there kinda with you through the whole thing until you tell us to go away. We're not there to do the the recovery for you or or to be an extra person on the team to execute. We're there to kinda shoulder surf and make sure everything's working the way it is, making sure that if something goes wrong, we see it happen when it goes wrong so that we can then jump into action to fix it as quickly as possible. The goal is to get you back up and running as as quickly as possible. This is part of our, ransomware recovery guarantee. You can go look that up. It's it's got a of course, it's with any guarantee, it's got a series of things that you've got to make sure you execute, including, doing all the best practices that we have and using the ransomware response team. They have done hundreds of these at this point. The the two fifty plus on there is actually out of date, and had a 100% success rate getting customers to restore their data, again, using those best practices that we provide ahead of time. You can't implement those at the time that that the attack happened. So know that that's there to to support every customer. It doesn't require any cost. This is part of just the basic support that you get with Rubrik. Okay. With that, now it's time to do the lab. There's there's the link there. Chase will also drop this link so that it's a little bit easier. You don't have to try to try to decipher that that random set of characters there. Go ahead and get it open. Make sure you can get to the first screen. I'll talk a little bit about it here, so don't actually get started on it yet, so that you can hear what I have to go through here. I'm gonna hold off in answering questions until I get through this lab stuff. I see that there are, a couple of questions there. But, being able to to get you up and running on this so you can start working on this while we ask questions. Again, it's it's a little bit of a long lab. So I'll give you a few tips and tricks there. A few things before I switch off of this particular screen. One, it's not a live lab. This is a single path. You can't make mistakes. You can't screw things up on this thing. It it is not using the actual interface, but it's actually using the HTML of the actual interface. It's just preventing you from clicking wherever you wanna go there. It is self guided. So I don't need to walk you through this. Once you get in and I get through all this, you can go through it at your own pace, take as much time as you want, explore the interface. A lot of screens will have, every screen, I should say, will have a pop up with some text. Sometimes it'll point at a specific thing. Sometimes it'll have a next button. Sometimes it'll have a little clickable place, to walk you through that. What it doesn't always do is, it can be a little weird when scrolling. So some screens that require scrolling, even if that prompt is up, you can scroll up and down to look at that interface. And there's a couple places where I actually prompt you to be like, hey. Just scroll around. Look what else is is available for you in here, because I didn't have the time to call out everything I would wanna call out. There is menu navigation available. I'll show you that here in a second. And it is available until, for the next week. So next Wednesday at essentially midnight Pacific time is when this is going to to time bomb. So you have a week to get through this, so don't feel like you have to rush through it in the next half hour that that this this event is scheduled for. I don't want you to rush through it. I want you to take your time. Make the time to do it. Me walking through it kind of as my final check, reading everything, taking some notes on what I needed to tweak, it took me about ninety minutes. So it'll be a little bit of time. I'll talk about the navigation. I'll allow you to jump around a little bit if if you need to, particularly if if you're already familiar with Rubrik for the basic backup and recovery side of things, that you can skip some stuff there. Okay. I think that's it. Let me let me, switch over to what you should be seeing now. Hopefully, you've clicked on the link that is in the, the q and a chat. This is what you see. This is the very first screen here. Let me point out, first of all, the navigation piece of things. So that's this little purple box here. And you can see that there are a lot of chapters in this. Some of them are a little bit longer than others. But kinda I you know, this should all match up very closely to what I went through in this presentation. They're meant to work together in that front. You'll see that this first one kinda has three screens similar to what you see when you first bring it up. They kind of explain what's going on. It explains about this menu item as one of those screens. But, really, it's it's just to start to transition you from the presentation into this lab. Again, if you're familiar with Rubrik already, if some of this was was repetitive to you, if you've done some of these guided demos or seen a demo before, you can skip around in here and and jump to a different section if you want to. Like, this first section is all about the data protection. Yeah, I mentioned the focus on on making it secure so you don't lose the backups. There's a strong focus on simplicity as well. If you're already running a Rubrik environment and and using our SLAs and protecting data that way, you can skip that first section. Okay. Back to this this first piece. Again, I mentioned the next button, so it it's pretty simple. You just kinda next through things. We're gonna jump into it. We get to this first section. You'll notice this is the when I clicked on two, this is the same thing that you saw there. So they all flow together nicely that way. Little bit of explanation about what we're gonna talk about in this section. Click next, and now we actually get to the interface. So you're seeing I mean, it's got all of the hovering capabilities. I can't click on just anything. Not everything is going to result anything if you can't tell I'm actually clicking on these different elements. There's only one place you can click, and that's where this little bubble is at. So in this case, I'm telling you a little bit about what what we're seeing on the screen, what this button's gonna do, what actions we want to take. So at this point, we wanna create an SLA domain. So the first thing you do is you click on that. This This is one of those examples of the scrolling. So I can scroll through all of this and see these are all the different data types that we can protect with Rubrik. So very strong focus on trying to get everything in your environment if possible. So being able to to click on these checkboxes, notice that automatically scrolls for me. So I'm never hunting for where this box is at, so it's gonna take me there, which does cause some weird scrolling things sometimes. So I'm clicking on these things. Okay. I've clicked two different VM types. I wanna go next and then explaining some things. So I'm gonna skip over some stuff just from a time perspective. I'll explain what's on the screen, tell you why we're skipping it, and move on to the next thing. If you wanna go back, you you can I'm gonna actually look at it this way. There's a little back arrow. So if oh, I didn't read that well enough. I'm gonna go back. So you can go back that way. You can also go back and just restart this whole thing by clicking this little replay. Or if I wanna go back to a whole different section I already completed, I can do that. So very good on navigating. If you wanna jump around and see specific things, if there's something that caught your attention, you wanna jump straight to that piece, you can do that. They all mostly stand alone. There is a story that I tell through the whole thing, so it is designed for you to go through the whole thing step by step. That is going to be your best value, but you do have the ability to jump around if you want to. Okay. I think that's all I need to tell you about that piece of things. If you have any questions on that, please dump questions in now. We will hang out for the next half hour that this was scheduled to answer any questions. So use this half hour to start going through this lab, getting getting familiar with it, bumping your toes into anything that that you need to so that we can answer those live for you. If there's any questions for the rest of the presentation, I'm gonna hang out for half an hour. I'll answer whatever questions you have on the Rubrik product, anything that we we we just talked about, that I talked about and you listened to. Again, make this interactive. Ask the questions you need right now. This is your opportunity to get those questions answered. So speaking of questions, let's see if there is anything in here that we can talk about. Okay. The essence of this question it's a little bit long, so I'm gonna try and summarize it, is asking about gap fill for organizations that, have no idea where they will recover their on prem system data to. So to me, best practice is always know where you're gonna recover. Have that environment ready to go at a moment's notice. This is our old Doctor planning. Hey. Tornadoes just hit our building. Hurricane's bearing down on us. We need to get up and running in a different place physically as quickly as possible. Have that environment already ready to go. Whether that's, you know, we're gonna recover to another whole building, you know, 80 miles away, whatever whatever that safe distance is for the disasters you're planning for. That is best practice. Have that environment ready to go. Could also be, you know, if you're a VMware shop and everything that you need to recover is in a VMware virtual machine, go to Azure, go to AWS, go to GCP, go to Oracle. There are others. There are plenty of, non hyperscaler clouds out there that offer a VMware native environment. And I wanna recover to those. I wanna I wanna be able to replicate all my data there and click a button and restore there This is another lower cost way of doing that because you have to manage the infrastructure, have to manage the facilities. And some of those actually do provide kinda pilot light. Essentially, you you have the agreement. You pay for, essentially, to have the service, but not necessarily to have the resources on all the time. And an agreement with that, that provider says that within half an hour of me clicking the button, they're going to bring up all of the all the servers that I need, whether those be physical or virtual servers. And knowing that within half an hour of clicking that button, I can go and start doing a restoration. So that is one one place where I don't wanna put forward the whole cost of a secondary environment in place. I don't know where I'm gonna recover to, but I know I know that those resources can be available to me as quickly as possible. The secondary way of going about it is to say, hey. I've got a Terraform script or whatever I might need to bring that environment up as quickly as possible. There is a danger, and and I honestly will kinda question the approach of this question, not not to disperse anybody, that may have this question. But it is a question that implies I'm not prepared for a disaster to happen, whether that be a cyber or a, environmental type problem that would be your typical traditional disaster recovery. If you're gonna really be prepared, if you really wanna minimize the cyber RTO aspect of things, you need to know where you're gonna restore to. That's important. Where you might not with a cyber attack is know whether I'm gonna restore it back into production or into into my isolated environment or my my secondary environment. That is one thing that really differentiates a Doctor plan from a cyber attack plan. So being able to know that, hey. There's this place that I can restore to quickly if I need to restore the whole thing. But deciding in heat of the moment whether it's just that surgical approach, if if you think back to that previous slide, or if it's the full the full run the full plan to restore those things. That's a piece that, again, is part of your, business continuity planning, your, cyber attack recovery planning to know how are we gonna make that decision? Whose decision is that to make? Do we have to have the CEO make that decision? Is it a CECL level decision? Is it, you know, two thirds of the c suite needs to needs to approve which way we're going to to go, is is super important there. Okay. Now I'm I've seen a clarification of the question, so I really appreciate that. Referring to the partnership with rack, with Rackspace. Yeah. So there's there's nothing built into the Rubrik environment, to do that. The the relationship with Rackspace is really, you have to have a level of relationship with them. And, essentially, what that results in is you replicating native Rubrik to Rackspace to be able to have, have your backups in their environment ready to go. And then, they have a couple different levels in which you can contract to say, you know, whether whether you have that kind of pilot light approach to things or if you're gonna have a full virtual environment to to restore directly to when the time comes there. So thank you for that clarification. That's that's an important, aspect of it to call out is is that relationship with Rackspace. We have relationships with, other, partners that that utilize Rubrik for that as well. There's there's a number of those, and you can find those on our our partnership page on our website. But, yeah, there's nothing built into the Rubrik interface because at this point, it is very much you need to you need to work with them. It's it's not a push a button in Rubrik to create a Rackspace recovery environment. We don't have it at that level today. And, honestly, I don't think we'll get to that point. Don't hold me to that. I'm not I'm not in charge of our product road map. But there's there's just so many things that go into it that are kind of beyond click a button in our interface, to be able to get to that. So if you have any more clarification on that question, please please post that in there. I'm gonna go ahead and, ask the team to clear those two questions. Next question. What Rubrik products provide this level? Oh, I answered that one already. Okay. Cool. So we can, approve and answered. Answered. Approve and answered. Okay. Cool. Okay. That's all the questions. That's that's unusual. I'm used to getting a lot of questions in these things. So I'm gonna assume that I did excellence on that presentation and gave you all the information you could possibly need to know. I don't think that's the case. So definitely encourage you to, to ask more questions here, particularly around the lab and the product. Again, I'm gonna hang out for a while, and and bring you any answers to any questions that may pop up. Some of them I may just answer virtually. But for now, I think what we'll do is hopefully, everybody's clicked on this link and has gotten in and and probably started at this point. Definitely do that. I mentioned the feedback. I think Chase is gonna pop this up in front of you for the feedback form. I would personally prefer would would would give personally ask you to fill out feedback form. Chase says that's popped up. It just doesn't show up in my interface. So that should be in your interface. Click on that. Open that up. You don't necessarily need to fill it out immediately right now, but I'd say within the next twenty four hours as you kinda get through the lab and or hopefully all the way through the lab, or at least partially through the lab to be able to provide any feedback on the lab, the content, the platform, how we went about this. This is probably the longest workshop that we've done like this. Let me know if it's too long. I'm I'm really curious if it's too long, if you felt like it was right, if if you're like, it was really long, but, man, the content was you know, you you painted the full story in it. I understand it needed to be that long. If there's any chance to to shorten it down, let me know. But, yeah, there there's there's a lot to it, because there's a lot of functionality that Rubrik provides. And and as we talked about across multiple different kinda licensing levels, as to, what we can do there. I guess what I I did mention the, the the active directory recovery, the identity recovery piece of things. I'm not realizing I kinda left it out of this particular, presentation. You will see that in the lab. It is definitely in that lab. It's it's active directory force recovery, and that is a a lesser licensing level than the resilience piece of things, but is included in the resilience piece of things. I did a good job, I think, of of explaining ADFR, as as we like to call it shorthand. So that is in the lab. It should walk you through that and kind of explain to you what it's doing. But at a really high level, it's it's a fast forward button on restoring active directory of full force. Doesn't matter how many, how many subdomains you have in the forest within within a few hours to be able to get that up and running using Microsoft best practices around active mercury forest recovery. If any of you have done that manually, it's painful. It's error prone. So automation is is is a really good friend to have on that front there. So apologies for missing that, but that would've just made the presentation even longer. Okay. Cool. Well, I'm not seeing any other questions pop in here. So what I'm gonna do is, essentially move move to my final slide, which is which is the thank you slide. I really appreciate the time. This has been just over an hour, and that is valuable time for you. I've I've been in your seat. I've been an admin. I've been an analyst in the past. I've I've been a billable time resource as well. So I know that that time is valuable, and I really do appreciate you taking the time here. I really hope it was valuable to you. Again, that feedback form, tell me how I can make it more valuable, or tell me, hey. It was as valuable as it could be. I'm happy happy to hear either either end of it, because I am very much a continuous improvement type of person. And then we do if this goes well, we'll repeat this for others, and tweak it to improve it for them as well. So with that final, thank you. I I think I will leave you to it. Stop talking in your ear while you work on this lab. Continue with the lab. Continue to post any questions that you might have as you go along. I'm gonna go off stage, if you will, and and be quiet for a little while, for the next twenty minutes or so. If any questions do come up, I'll I'll pop up and and answer some of those live. If I feel like they would be good for everybody to hear. Some of them I may answer in the q and a panel itself if if they're pretty pretty simple, answers to to answer through text. So I'm gonna stop talking now. I'll pop back on before the end, just to say a final goodbye for those of you that are still hanging on and working on this. Okay. Well, we are at the, end of the scheduled time. I can see a few people still definitely going through this, so I appreciate your time, going through these labs. I did not see any other questions pop up, so, I hope everyone is getting through this lab well. This, again, will be open through the end of the day Pacific US Pacific time, next Wednesday. So you've got a little bit of time to to work through this. So please feel free to get back in there and look at it. We've set up so that, there will be some follow-up emails that will send you out the link again to remind you to to finish it up before then. So, you'll have you'll have a little bit of a reminder to get that done. But really appreciate you all joining, especially for those of you that are still hanging out and going through the lab. I hope you all have a good rest of your day and a good rest of the week, and, we hope to engage with you more in the future. Take care, everybody.