Whitepaper
Your technical guide to Identity-First Recovery (IFR)
Recover your directory. Scan the target OS for risk and make sure it’s clean.
When an AD forest is compromised, traditional recovery ties the directory to the underlying OS. Without scanning for malware, organizations risk recovering threats in the OS. Also, traditional recovery requires rigid matching between source and target hosts. Finally, because traditional ADFR might mean recovering gigabytes of data you don’t need, recovery slows. This whitepaper is your technical reference to how IFR solves this.
You’ll learn:
-
Where IFR Fits and Why: Where IFR fits alongside SSR and Bare Metal Recovery (BMR), what's required before you start, and how Threat Monitoring/Threat Hunting help you make a threat-informed decision as to the clean recovery point.
-
IFR Architecture and Workflows: How Rubrik separates the ntds.dit and SYSVOL from the host OS, using the backups and SLAs you have in place.
-
How to Recover to any Target: Introduce the ntds.dit and SYSVOL into a clean Windows instance free of attacker persistence. Includes portability across on-prem, hypervisors, and cloud.
Scan for risk. Accelerate the recovery. Download the whitepaper to learn how.
Whitepaper