Why Password Resets Alone May Not Evict Attackers from Active Directory

· Original article ↗

Summary

Password resets may leave cached hashes, active Kerberos tickets, service-account credentials, forged tickets, or malicious AD permissions usable. The sponsored guide recommends terminating sessions, resetting KRBTGT twice for serious compromises, rotating credentials,,

Key points

  • Cached password hashes on devices that have not reconnected to the domain may remain usable after a reset; hybrid password-hash synchronization to Entra ID can also take time.
  • An attacker with an active Kerberos ticket may retain access after a password change; the article recommends terminating sessions and clearing tickets through logoffs or reboots.
  • For serious compromises, the article says resetting the KRBTGT account twice is often necessary to invalidate forged Kerberos tickets.
  • Service accounts may retain long-lived credentials and elevated privileges; rotate their passwords, especially for privileged accounts.
  • Audit group memberships, delegated rights, ACLs, privileged accounts, and AdminSDHolder changes for permissions that could enable access to be re-established.
  • Specops says its uReset service, used with the Specops Client, can update the local cached credential store immediately on the device where a reset occurs.

Article Details

Defense Focus
Evict attackers after an Active Directory or hybrid Entra ID password reset by invalidating existing sessions and Kerberos tickets, rotating exposed credentials, and checking for persistent directory permissions.
Detection Methods
  • Audit group memberships, delegated rights, ACLs, and privileged accounts and roles for changes that could allow access to be re-established.
  • Review the AdminSDHolder object for unauthorized ACL changes that could be reapplied by SDProp.
  • Check for active sessions and Kerberos tickets that may remain usable after password changes.
Data Sources
  • Active Directory group memberships, delegated rights, ACLs, privileged accounts, and roles
  • AdminSDHolder ACLs and SDProp-applied permissions
  • Active sessions and Kerberos tickets
  • Cached credentials on endpoints
  • AD-to-Entra ID password hash synchronization state
Platforms
  • Active Directory
  • Entra ID
Defensive Actions
  • Terminate active sessions and clear Kerberos tickets through logoffs or reboots on affected systems.
  • For serious compromises, reset the KRBTGT account twice to invalidate forged tickets.
  • Rotate service-account passwords, especially for accounts with elevated privileges.
  • Clear cached credentials on endpoints as systems reconnect.
  • Review directory group memberships, delegated rights, ACLs, privileged accounts, and roles for persistence or unauthorized access paths.
  • Consider enabling AD Change Notification or manually initiating synchronization to the Entra ID tenant to reduce password synchronization delay.
  • Use Specops uReset with Specops Client to update the local cached credential store on the device where a reset is performed.

MITRE ATT&CK

Vendors

Products

Related Articles