TL;DR: Active Directory remains the attacker’s fast lane because single-endpoint access can still expand into reconnaissance, lateral movement, privilege escalation, and ransomware or theft at scale, according to Semperis. The core lesson is that incident response fails when identity teams treat AD as legacy plumbing instead of the control plane that defines blast radius and recovery order.
NHIMG editorial — based on content published by Semperis: A Quarter Century, a Quarter Million Breaches: AD Security & Incident Response
By the numbers:
- Active Directory has passed its 25-year mark, and for most organizations, it’s still the backbone of identity.
Questions worth separating out
Q: How should security teams contain an Active Directory incident without destroying evidence?
A: Teams should first confirm the scope of the identity incident, then isolate high-risk privileged paths while preserving logs and at least one known-good domain controller if possible.
Q: Why do Active Directory incidents so often lead to domain-wide impact?
A: Because AD links authentication, privilege, and system reachability into one connected control plane.
Q: What breaks when privileged administration is not separated from routine work?
A: A workstation used for everyday tasks becomes a bridge into Tier 0 if the admin session is compromised.
Practitioner guidance
- Map Tier 0 identity assets explicitly Inventory domain controllers, AD CS, Entra ID Connect, AD FS, virtualization hosts for domain controllers, and key management systems as Tier 0.
- Harden privileged admin paths with PAWs Require Privileged Access Workstations for all Tier 0 operations and keep them internet-restricted.
- Preserve one known-good domain controller Build recovery procedures that identify at least one domain controller or site that has not replicated malicious changes if possible.
What's in the full article
Semperis's full article covers the operational detail this post intentionally leaves for the source:
- Michael Van Horenbeeck's full incident-response walkthrough for AD and hybrid identity environments
- The specific way the NIST CSF maps to Identify, Protect, Respond, and Recover in identity incidents
- Real-world breach stories that show how AD-centric attacks progress across the kill chain
- Practical crisis-management guidance for preserving evidence while rebuilding trust
👉 Read Semperis's AD security and incident response session summary →
Active Directory crisis response: is your IAM playbook ready?
Explore further