Domain Compromise Investigations

Active Directory Compromise ForensicsCredential Theft, Ticket Forging, and Proving Domain Wide Compromise

Active Directory is the identity backbone of most business networks, which makes it the single highest value target once an attacker gains a foothold. Compromise of a domain controller or a privileged credential can escalate an incident from one infected workstation to control of the entire environment, and proving the true scope is one of the hardest and most consequential questions in incident response.

Updated August 2026 · Reviewed by Elite Digital Forensics examiners · Nationwide breach response

Domain controllerA compromised domain controller or its NTDS.dit database effectively means every credential in the domain must be treated as compromised.
Ticket based attacksKerberos ticket forging techniques allow persistence that survives ordinary password resets across the domain.
Certificate servicesMisconfigured Active Directory Certificate Services templates have become one of the most common paths to domain administrator.

Quick answer

Active Directory compromise forensics investigates how an attacker obtained and abused domain credentials, using techniques such as Kerberoasting, DCSync, golden and silver ticket forging, and Active Directory Certificate Services abuse to move from a single compromised account toward domain administrator control. Because ticket forging and certificate abuse can grant persistence that survives ordinary password resets, proving the true scope of compromise, and confirming when it has actually been eradicated, requires correlating domain controller security event logs, replication metadata, and certificate services logs rather than trusting a single source.

Common questions, answered in one line

QuestionOne line answer
What is Kerberoasting?Requesting service ticket hashes for accounts with a service principal name and cracking them offline to recover the account password.
What is DCSync?Abuse of directory replication permissions to pull password hashes for any account directly from a domain controller without touching it interactively.
What is a golden ticket?A forged Kerberos ticket granting ticket built using the stolen krbtgt account hash, granting domain wide access that survives normal password resets.
Does resetting passwords fix a golden ticket compromise?No, the krbtgt account itself must be reset, typically twice, and even then thorough eradication verification is required.
What is AD CS abuse?Exploitation of misconfigured certificate templates to obtain a certificate that authenticates as a privileged account.
How is domain wide compromise proven?By correlating domain controller logs, replication events, certificate issuance records, and endpoint telemetry across multiple hosts.

Key terms defined

TermWhat it means
Domain controllerA server that hosts Active Directory and processes authentication and authorization requests for the domain.
krbtgt accountThe special service account whose password hash is used to encrypt Kerberos ticket granting tickets for the entire domain.
KerberoastingRequesting Kerberos service tickets for accounts with a service principal name, then attempting to crack the encrypted portion offline to recover a plaintext password.
DCSyncA technique that abuses directory replication permissions, normally reserved for domain controllers, to extract password hashes for any account directly from Active Directory.
Golden ticketA forged Kerberos ticket granting ticket created using the krbtgt hash, allowing an attacker to impersonate any account in the domain for an extended period.
Silver ticketA forged service ticket created using a specific service account hash, granting access to that one service without contacting a domain controller.
AD CS abuseExploitation of misconfigured Active Directory Certificate Services templates or permissions to obtain a certificate that can authenticate as a privileged account.

How Active Directory compromise escalates from one account to the domain

Most Active Directory compromises follow a recognizable escalation pattern, and understanding it helps an examiner know which artifacts to prioritize at each stage.

  • Initial credential access, commonly through phishing, an exposed remote access service, or a vulnerable application, giving the attacker a foothold with a standard user account.
  • Kerberoasting and password spraying against service accounts, which are frequently configured with weak, static passwords set years earlier and never rotated.
  • Lateral movement using harvested credentials and living off the land tools to reach systems with cached privileged credentials or direct domain controller access.
  • DCSync execution once an account with replication rights is compromised, extracting the krbtgt hash and effectively every account hash in the domain in a single action.
  • Golden ticket forging using the krbtgt hash, granting the attacker persistent, domain wide authentication that does not depend on any single compromised account remaining valid.
  • AD CS exploitation as an alternate or parallel path, abusing a certificate template that allows a low privileged user to request a certificate usable to authenticate as a domain administrator.

Why this matters for remediation, not just investigation

An examiner tracing this chain is not only answering a historical question. The findings directly determine what has to be reset, revoked, and rebuilt before the organization can be confident the attacker no longer has access, which is why Active Directory compromise cases require close coordination between forensic findings and the remediation team throughout the engagement rather than only at the end.

Evidence sources for reconstructing an Active Directory compromise

No single log source tells the whole story. A defensible reconstruction correlates domain controller security events, directory service events, and certificate services logs, along with endpoint telemetry from the hosts involved at each stage.

Evidence sourceWhat it typically showsKey limitation
Domain controller security event logAuthentication events, account changes, and, when auditing is properly configured, Kerberos ticket requestsRequires advanced audit policy to be enabled; default settings miss many relevant events
Directory service replication logsReplication requests, which can reveal DCSync style extraction from a non domain controller sourceRequires specific auditing to be enabled and can be missed if logging is at default levels
AD CS certificate services logsCertificate requests and issuance, useful for identifying abuse of a vulnerable templateOften not enabled by default and rarely reviewed until after a compromise
Endpoint telemetry (EDR)Execution of credential dumping and ticket forging tools on individual hostsOnly covers monitored endpoints and can be tampered with once an attacker has elevated privileges
NTDS.dit and SYSTEM hive analysisA definitive list of every account hash present at the time of acquisition, when a domain controller is imagedOnly reflects a point in time; does not by itself show what was actually used maliciously

Advanced audit policy is often the deciding factor

Whether an investigation can even attempt to answer these questions frequently comes down to whether advanced audit policy settings, such as detailed Kerberos service ticket operations and directory service access auditing, were enabled before the incident. Organizations that have never reviewed their domain controller audit policy are often surprised to learn how little detail their logs actually captured during the compromise.

Suspected domain controller or credential compromise

Active Directory compromise scope determinations are time sensitive and technically demanding. Our examiners can begin evidence preservation and analysis immediately.

Proving domain wide compromise, and proving eradication

The hardest question in an Active Directory case is often not how the attacker got in, but how far they actually reached, and whether the organization can be confident that access has truly been terminated after a golden ticket or certificate based persistence mechanism was used.

Step 1

Establish the initial access point and the first account compromised, using endpoint telemetry and authentication logs.

Step 2

Identify every account and host touched during lateral movement, using authentication logs, EDR telemetry, and any available network evidence.

Step 3

Determine whether DCSync style replication abuse occurred, which if confirmed means every account hash in the domain must be treated as potentially compromised.

Step 4

Review certificate services logs for any certificate issued to an account inconsistent with its normal role, indicating AD CS based persistence.

Step 5

Confirm remediation steps taken, including a double krbtgt reset, certificate authority review, and privileged account credential rotation, and document the evidentiary basis for asserting the environment is clean.

What matters most

  • Confirming whether advanced audit policy was enabled on domain controllers before the incident, since that determines what can even be reconstructed.
  • Treating any confirmed DCSync activity as compromise of every account hash in the domain, not just the accounts observed being used.
  • Understanding that a single password reset does not remediate golden ticket persistence; the krbtgt account itself requires a double reset.
  • Reviewing AD CS certificate templates and issuance logs even when the initial compromise vector appeared unrelated to certificates.
  • Coordinating investigation findings with remediation in real time rather than delivering conclusions only at the end of the engagement.

Common misconceptions

Resetting all user passwords fixes an Active Directory compromise

It does not address a golden ticket built from the krbtgt hash, which requires a specific double reset of that account itself.

Kerberoasting requires domain administrator access to attempt

Any authenticated domain user can request service tickets for accounts with a service principal name, making it accessible from a low privileged foothold.

AD CS abuse only matters if certificate services was recently deployed

Long standing, forgotten certificate templates are a common and often overlooked path to domain compromise.

If the domain controller itself was not touched, the domain is safe

DCSync and ticket forging techniques allow domain wide compromise without ever directly logging into a domain controller interactively.

When this applies, and when it does not

This applies when

  • A privileged account, service account, or domain controller shows signs of unauthorized access.
  • Ransomware or another intrusion reached systems with cached domain administrator credentials.
  • Unusual replication activity or unexpected certificate issuance was identified during monitoring.
  • An organization needs confidence that remediation has fully removed attacker access before resuming normal operations.

This does not apply when

  • The environment has no on premises or hybrid Active Directory component, in which case Entra ID focused analysis applies instead.
  • The incident is confined to a single standalone workstation with no domain trust relationship.
  • No domain controller logging of any kind survived and no image was taken before rebuild, severely limiting what can be reconstructed.

How Elite Digital Forensics helps

We are retained by businesses, managed service providers, and cyber insurance carriers to investigate suspected Active Directory compromise, from a single Kerberoasted service account to full domain administrator takeover. Our examiners work alongside internal IT and security teams to acquire domain controller evidence correctly, trace the true scope of compromise, and validate that remediation was complete.

Domain controller acquisition

Forensically sound imaging of domain controllers and export of security, directory service, and certificate services logs.

Credential compromise scoping

Determination of whether Kerberoasting, DCSync, or ticket forging occurred, and which accounts must be treated as compromised.

AD CS abuse review

Analysis of certificate templates, permissions, and issuance logs for signs of certificate based privilege escalation.

Eradication verification

Independent confirmation that remediation steps, including krbtgt resets and credential rotation, actually terminated attacker access.

Timeline and root cause reporting

A defensible written account of the escalation chain for counsel, carriers, and regulators.

Expert witness testimony

Court qualified examiners able to explain Kerberos, replication abuse, and certificate services attacks under cross examination.

Problems we solve

  • You do not know whether an attacker who reached one server ever obtained domain administrator level access.
  • A domain controller was compromised and you need to know whether every account hash must be treated as exposed.
  • Your team reset passwords after an incident but access to the network persisted afterward.
  • A certificate authority in your environment may have been abused to issue a privileged credential.
  • Your carrier or counsel needs an independent assessment of whether eradication was actually complete.

Talk with a forensic examiner about your incident

Consultations are confidential. We work directly with affected businesses, with outside counsel, and with cyber insurance carriers and brokers nationwide.

About Elite Digital Forensics

Elite Digital Forensics is an independent digital forensics firm serving businesses, attorneys, and insurers nationwide. Our examiners include former law enforcement forensic examiners who have testified as court qualified expert witnesses in state and federal proceedings. We do not sell security software and we do not manage client networks, so our findings carry no conflict of interest when the question is whether an environment was adequately secured.

Every engagement follows documented chain of custody, defensible acquisition methods, and reporting written for attorney review, insurer submission, regulator response, or courtroom use. Work performed at the direction of counsel is generally treated as attorney work product prepared in anticipation of litigation. Call (833) 292-3733 or request a confidential consultation.

Frequently asked questions

What is the difference between Kerberoasting and DCSync?

Kerberoasting targets service accounts by requesting their service tickets and attempting to crack the resulting hash offline to recover a password, requiring only a standard authenticated user. DCSync abuses directory replication permissions to pull password hashes directly from a domain controller for any account, and typically requires a more privileged compromised account or misconfigured permissions to execute.

Why does a golden ticket survive a normal password reset?

A golden ticket is forged using the krbtgt account hash rather than any individual user credential, so resetting user passwords has no effect on it. Eradicating a golden ticket requires resetting the krbtgt account password twice, since Kerberos retains the previous password for a grace period.

How can an organization tell if DCSync was used against its domain?

Detecting DCSync requires directory service access auditing to be enabled, watching for replication requests originating from a source that is not a legitimate domain controller. Without this auditing configured beforehand, DCSync activity is very difficult to detect after the fact.

What is Active Directory Certificate Services abuse?

It refers to exploitation of misconfigured certificate templates or permissions within an organization certificate authority, allowing a low privileged account to request a certificate that can be used to authenticate as a highly privileged account, such as a domain administrator, bypassing normal password based controls entirely.

How do examiners prove domain wide compromise rather than a single host compromise?

By correlating authentication logs, endpoint telemetry, replication events, and certificate issuance records across multiple systems and accounts to trace lateral movement and privilege escalation, rather than relying on any single log source or a single compromised host as evidence of the full scope.

Is it enough to rebuild the compromised domain controller?

Not by itself. If credentials, the krbtgt account, or certificate authority integrity were compromised, rebuilding one server does not remove attacker access gained through forged tickets or abused certificates elsewhere in the domain. A full remediation plan grounded in the investigation findings is required.

References and authoritative sources

  1. MITRE ATT&CK Enterprise Matrix — https://attack.mitre.org/matrices/enterprise/
  2. NIST SP 800-86, Guide to Integrating Forensic Techniques into Incident Response — https://csrc.nist.gov/pubs/sp/800/86/final
  3. NIST SP 800-61 Rev. 3, Incident Response Recommendations (April 2025) — https://csrc.nist.gov/pubs/sp/800/61/r3/final
  4. Microsoft, Event ID 4624 and logon type reference — https://learn.microsoft.com/windows/security/threat-protection/auditing/event-4624
  5. Federal Rule of Civil Procedure 37(e), Failure to Preserve Electronically Stored Information — https://www.law.cornell.edu/rules/frcp/rule_37
  6. Verizon Data Breach Investigations Report — https://www.verizon.com/business/resources/reports/dbir/

#DigitalForensics #ComputerForensics #CellPhoneForensics #ExpertWitness #DigitalForensicExperts #EliteDigitalForensics #ForensicInvestigation #DataBreachResponse #DataBreachInvestigation #IncidentResponse #CyberForensics #ActiveDirectory #KerberosSecurity #DomainCompromise #IdentitySecurity

This content is for educational and informational purposes only and does not constitute legal advice. Elite Digital Forensics provides independent digital forensic services and expert witness testimony; we do not provide legal representation. Every case is fact specific; outcomes depend on the evidence, jurisdiction, and counsel. Retain qualified legal counsel for advice about your matter.

Assistant Icon Elite Digital Forensics Assistant
πŸ‘‹ Live Chat Now!
Free Virtual Consultation 24/7
Chat Now!

By submitting this form, you consent to be contacted by email, text, or phone. Your information is kept secure and confidential. Reply Stop to opt out at anytime.Β 

IMPORTANT: Please remember to check your spam or junk folder