Security teams should treat Active Directory backups as a resilience control, not just a storage task. Keep backups isolated from ordinary server and data backups, maintain at least two domain controller backups per domain, store copies offline or in object storage, and test restores regularly. The goal is a malware-free recovery path that limits reinfection and shortens restoration time.
How to Structure Active Directory Backups for Clean Recovery
Design the backup set around directory restoration, not just file preservation. Active Directory needs recoverable system state plus enough historical coverage to rebuild trusted domain controllers without reintroducing the same compromise. That means separating directory backups from ordinary server backups, preserving more than one restore point, and choosing storage that resists tampering, deletion, or encryption.
One practical way to think about this is that the backup must help you recover after destructive attacks, not merely after accidental loss. If the directory itself has been manipulated, your recovery path has to be trusted, clean, and restorable without depending on the potentially compromised production estate.
What a Clean Recovery Path Needs
At minimum, a clean recovery path should give you a known-good directory baseline, multiple restore points, and the ability to restore domain controller state without following the same bad configuration into production. That is why backup placement matters: keep AD backups isolated from routine workload backups, and avoid storing all copies in one management plane or one administrative domain.
Two backups per domain is a sensible floor, but the deeper issue is diversity of recovery points. A single backup can already contain poisoned objects, malicious changes, or latent compromise that only becomes obvious later. Maintain a sequence of restore points so you can step back before the point of intrusion or destructive change, then validate which copy is actually safe to trust.
For storage design, offline copies and object storage both have value when they are protected from routine deletion and encryption paths. Object storage can help with retention and immutability, while offline or logically isolated copies reduce the chance that the same attacker who encrypts production can also erase the recovery path. NHI Management Group’s Backup Security and Immutable Backup Guide covers the backup controls that make this kind of recovery path durable in practice.
Restoration testing is part of the design, not a later validation step. A backup that has never been restored is only an assumption. The restore process should prove that you can bring up a domain controller cleanly, confirm directory health, and recover service dependencies in the right sequence rather than discovering missing pieces during an incident.
Why AD Backups Fail During Ransomware or Wiper Events
The biggest failure mode is shared trust. If the same privileged paths, credentials, storage permissions, or management tooling can reach both production and backups, an attacker can often compromise the recovery path after compromising the directory. In those cases, “backup” becomes another target, not a countermeasure.
Another common failure is restoring a poisoned directory too quickly. If compromised admin accounts, malicious group memberships, rogue delegation settings, or tampered directory objects are present in the restored state, the environment may come back online with the original attacker still effectively inside it. That is why recovery planning has to include directory integrity checks, not just restore completion. NHI Management Group’s Active Directory and Entra ID Hardening Guide is useful background for understanding which privileged paths and directory relationships should be treated as high-risk.
Attackers also look for backup systems that are easier to delete than production data. Destructive operators and ransomware crews often target recovery infrastructure after initial access because it increases leverage: if recovery is unreliable, defenders are more likely to pay, delay, or make dangerous trade-offs. That is why tamper-resistant retention and separate administrative control are as important as the backup software itself.
A second useful reference point is Ransomware Playbook Template, which shows how backup validation fits into the incident sequence rather than being treated as a standalone IT task. For directory incidents, the order of operations matters: establish scope, preserve evidence where needed, confirm a trusted restore point, then rebuild access in a controlled sequence.
Risk and Threat Considerations
AD backups create resilience only when the backup path is harder to corrupt than the live directory. If backups share administrative credentials, storage permissions, or the same identity plane as production, a ransomware operator can sabotage recovery at the same time as it sabotages operations. The result is longer outage time, greater chance of reinfection, and a higher likelihood that the organisation restores compromised directory state.
Failure mechanism: Attackers delete, encrypt, or poison backup copies, or they compromise the credentials and administrative paths needed to access them. They may also rely on defenders restoring an untrusted copy that already contains malicious directory changes, privileged access, or persistence mechanisms.
Impact: Recovery slows down, clean rebuild confidence drops, and the organisation may bring back the attacker along with the directory. In the worst case, the backup program becomes part of the blast radius instead of a barrier to it.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | CP-9 — System Backup | AD backup design directly depends on recoverable, protected backups. |
| CP-10 — System Recovery and Reconstitution | Clean AD recovery requires restoring trusted directory state after destructive attacks. | |
| IA-5 — Authenticator Management | Backup protection hinges on securing the credentials and secrets that can access backup systems. | |
| Recommendation — Define and test protected directory backups with recoverable media and retention. Reconstitute domain controllers from validated restore points and rehearse recovery steps. Rotate and tightly control credentials that can administer backup and restore paths. | ||
| CIS Controls v8 | 11 — Data Recovery | The subject is fundamentally about restoring data and systems after ransomware or destruction. |
| 5 — Account Management | Backup recovery depends on controlling who can access and alter backup systems. | |
| Recommendation — Maintain tested recovery capability with isolated, verified backups and restore drills. Restrict backup administration to tightly scoped, reviewed accounts and roles. | ||
| ISO/IEC 27001:2022 | A.8.13 — Information backup | The page focuses on resilient backup design and restore readiness for directory services. |
| A.8.24 — Use of cryptography | Immutable and tamper-resistant backup storage often relies on cryptographic protection. | |
| Recommendation — Implement protected, tested backups with restoration procedures that meet recovery needs. Protect backup data with cryptographic controls that preserve integrity and confidentiality. | ||
Practitioner Guidance
What to prioritise: Treat the backup design as a directory recovery design. The first question is not “can we restore data,” but “can we restore a trusted domain controller and verify the directory state before reconnecting it to the rest of the estate?”
What to verify: Test that a restore can be performed from isolated media or isolated storage, that at least one restore point predates the suspected compromise window, and that the restored environment does not rely on the same credentials used to protect production backups. If those conditions are not true, the recovery path is still too exposed.
Practitioner takeaway: Clean AD recovery depends on separation, immutability, and restore validation, but the decisive test is whether the backup can survive the same adversary that destroyed production.
Related resources from NHI Mgmt Group
- How should security teams recover Active Directory after a cyberattack without relying on manual restoration steps?
- What should security teams do first when Active Directory forest recovery is needed after ransomware or schema corruption?
- How should security teams design cyber resilience so recovery stays reliable after ransomware or other attacks?
- What happens when a hospital has to recover Active Directory after a ransomware or wiperware compromise?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org