Active Directory is usually the first thing attackers take over and the first thing you need back. Without a trusted directory, servers cannot authenticate, applications cannot start and administrators cannot sign in.
Why AD recovery is different
Restoring a domain controller from last night’s backup may bring back the attacker’s accounts, scheduled tasks or changed group memberships. Recovery has to start from a copy you trust and then remove anything the attacker added.
The core recovery steps
- Pick a known clean domain controller backup from before the intrusion.
- Restore it into an isolated network with no connection to production.
- Clean up accounts, group memberships, group policy and trusts the attacker may have changed.
- Reset the KRBTGT account password twice and reset privileged account passwords.
- Rebuild or restore the remaining domain controllers from the recovered one.
- Reconnect services in priority order and monitor closely.

What to protect now
- System state backups of at least two domain controllers per domain, kept immutable
- An offline copy of the runbook and of admin credentials for the recovery environment
- Regular test recoveries of AD into an isolated network
Key takeaways
- AD is the foundation of almost every recovery.
- Restore from a clean point into isolation, then clean up before reconnecting.
- Test the forest recovery at least once a year.
How long would your directory take to come back?
We help you plan and test a clean Active Directory recovery.



