What happens after Active Directory is compromised but still remains available?

If Active Directory stays online after compromise, domain-dependent services may keep running, which can hide the severity of the attack. That creates a dangerous window where malicious changes continue to affect authentication and access while business operations appear normal. Recovery then requires careful rollback, validation, and restoration of trusted directory state rather than a simple reboot or rebuild.

Why Active Directory Can Still Operate After a Compromise

When active directory remains available after compromise, the attacker has usually not destroyed the directory service. Instead, they have altered trust, privilege, or authentication state inside it. That means logons, group policy, service authentication, and application access may continue to work, even while the directory is now issuing decisions from a hostile or corrupted state.

The operational danger is that availability can disguise control failure. A working domain controller does not prove the directory is trustworthy. In practice, that means defenders must treat the environment as both live and contaminated until they can separate normal service continuity from malicious directory changes.

Why Compromise with Availability Is More Dangerous Than Outage

Availability keeps the business running, but it also preserves the attacker’s access path. A compromised directory can continue to authenticate users, issue tokens, resolve group membership, and distribute policy while malicious changes remain active. That makes the incident harder to spot because the usual “everything is still up” signal is misleading.

This is why privileged directory compromise often becomes a persistence problem. If an attacker changed privileged groups, delegated rights, trust relationships, or authentication material, those changes can keep affecting access decisions until they are found and removed. The environment may look functional while the attacker still benefits from the altered state.

For practitioners, Active Directory and Entra ID Hardening Guide is a useful reference for the control points that usually determine whether the directory can be trusted after compromise.

What Recovery Requires Once the Directory Is Suspect

Recovery is rarely a simple reboot or rebuild. You first need to establish what the compromised directory was allowed to change, which identities or systems inherited that change, and whether the directory state was replicated to other controllers. If the compromised state has already spread, restoring one server without restoring trust will not fix the problem.

That is why recovery typically requires rollback to a known-good state, validation of privileged groups and delegation, credential resets where trust may have been exposed, and confirmation that policy, authentication, and replication are clean. The key question is not whether Active Directory comes back online, but whether it comes back in a state that can safely make access decisions again.

In practice, NHI Lifecycle Management Guide is relevant because the same lifecycle discipline that governs non-human credentials also applies to recovery of directory-linked identities, secrets, and access paths.

Risk and Threat Considerations

A compromised but still available directory creates a deceptive risk profile: the service appears stable while the attacker may still control authentication, authorization, or privileged membership. That can extend dwell time, preserve persistence, and allow continued abuse of domain trust before defenders realize the directory state itself is untrusted.

Failure mechanism: Malicious changes to privileged groups, delegation, trusts, or credential material remain active because the directory is still serving authentication and access decisions, so downstream systems continue to accept corrupted state.

Impact: Business services may keep running, but the attacker can retain or regain access, alter permissions, and move laterally until the trusted directory state is rebuilt or validated.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

Framework	Control / Reference	Relevance
NIST SP 800-53 Rev 5	IA-5 — Authenticator Management	Directory compromise often turns on stolen or altered authenticator material.
	AC-2 — Account Management	Compromise can persist through changed accounts, groups, and delegated rights.
	AU-6 — Audit Record Review, Analysis, and Reporting	Trusted recovery depends on finding malicious directory changes and replication effects.
Recommendation — Rotate exposed credentials and revoke any authenticator that could preserve directory access. Review and remove unauthorized accounts, group membership, and delegated access. Correlate directory and authentication logs to identify unauthorized state changes.
NIST CSF 2.0	RC.RP-01 — Recovery Plan Execution	Recovery from directory compromise requires controlled restoration, not ad hoc rebooting.
	PR.AA-05 — Access Permissions and Authorization	The issue is corrupted authorization, not just service uptime.
Recommendation — Execute the recovery plan to restore only a validated trusted directory state. Revalidate authorization paths before allowing dependent services back into normal operation.
MITRE ATT&CK	T1098 — Account Manipulation	Attackers often persist by changing privileged directory objects.
Recommendation — Hunt for unauthorized account, group, and delegation changes in the directory.

Practitioner Guidance

What to verify: Treat directory availability and directory integrity as separate checks. Confirm which privileged objects changed, whether replication propagated those changes, and whether dependent systems cached or inherited the compromised state.

Decision rule: If the directory can still authenticate while its trust state is uncertain, prioritise containment and validation over availability preservation. A functioning login path is not a sign of recovery if the access decisions are no longer trustworthy.

What good looks like: Recovery is complete only when the directory has a known-good baseline, privileged access has been revalidated, and the environment can prove that no malicious state remains in the authentication or authorization path.

Practitioner takeaway: The main operational trap is assuming that “still online” means “still safe”; with Active Directory, the real recovery target is trusted state, not just restored uptime.