Local Administrator vs Domain Administrator: Boundaries and Escalation Paths
Concept
Section titled โConceptโA frequent source of critical misjudgments during incident triage is the ambiguous usage of the title โAdministratorโ:
- Local Administrator: Holds total control over a single operating system instance. Its blast radius terminates strictly at the host boundary.
- Domain Administrator: Holds administrative authority over the central Active Directory database and, by default configuration, over member hosts that trust the domain.
Why This Matters in DFIR
Section titled โWhy This Matters in DFIRโIncident responders must answer two vital triage questions:
- Question 1: โThe adversary gained local administrator access on WEB01. Is the domain compromised?โ
- Answer: Not automatically. The host is compromised, but the attacker has zero direct directory rights.
- Question 2: โWhat technical mechanisms allow the attacker to pivot from local host administrator to Domain Administrator?โ
- This is the essence of lateral movement. The adversary abuses local administrative control to harvest credentials (LSASS memory dumps, cached Kerberos TGTs, DPAPI secrets) deposited by domain administrators logging into the compromised host.
How It Works
Section titled โHow It WorksโThe Default Group Nesting Chain
Section titled โThe Default Group Nesting ChainโWhy does a Domain Admin have administrative rights on a member workstation?
When an endpoint joins a domain:
- The Windows client connects to the Domain Controller.
- The domain security group
DOMAIN\Domain Adminsis automatically nested inside the hostโs localBUILTIN\Administratorsgroup. - If an administrator removes
Domain AdminsfromBUILTIN\Administratorson an endpoint, domain admins lose local administrative control on that specific machine.
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Active Directory โโ โโ [Group: Domain Admins] (RID 512) โโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโ โ (Nested during domain join) โผโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ Member Host (FS01) โโ โโ [Local Group: Administrators] (544) โโ โโโ LOCAL\Administrator (RID 500) โโ โโโ DOMAIN\Domain Admins (RID 512)โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโLateral Escalation: From Local Admin to Domain Dominance
Section titled โLateral Escalation: From Local Admin to Domain DominanceโLocal Host Compromise (Host A) โ โโโบ 1. LSASS Harvesting (Dumping plaintext / hashes / tickets of logged-on Domain Admins) โโโบ 2. Pass-the-Ticket (Extracting active Kerberos TGTs from memory) โโโบ 3. Credential Reuse (Identical local administrator passwords across the fleet) โโโบ 4. Service Account Abuse (Extracting T1/T0 service tokens or unconstrained delegation)- LSASS In-Memory Harvesting: If a Domain Admin connects via RDP (Logon Type 10) or interactive logon (Type 2), their Kerberos tickets or NTLM hashes reside in
lsass.exe. The local admin extracts them usingMimikatzorlsassy. - Fleet-Wide Pass-the-Hash (LAPS Absences): If local
Administratorshares a single password across endpoints, the adversary moves laterally host-by-host until discovering an active Domain Admin session. - Unconstrained Kerberos Delegation: If the host has
TRUSTED_FOR_DELEGATIONenabled, any domain user connecting to it deposits a forwardable TGT into host memory.
What Is Possible
Section titled โWhat Is Possibleโ- Stripping Domain Admins from Endpoints: Under clean Tiering models, domain admins must never be permitted to log into Tier 2 workstations.
- Network Sniffing by Local Admins: Local admins can deploy packet sniffers or ARP spoofers to intercept domain authentication handshakes on the wire.
- Targeted Host Quarantine: Incident responders can disable the hostโs
COMPUTER$account on the DC, cutting all domain Kerberos tickets.
What Is Not Possible
Section titled โWhat Is Not Possibleโ- Querying
ntds.ditas Local Admin: Outbound RPC/SMB requests from a local admin account reach the DC as anonymous or fail authentication. - Injecting Local Hashes into a DC: The Domain Controller rejects SAM hashes originating from foreign machine SIDs.
- Local Password Changes Affecting Active Directory: Modifying a local SAM user password has zero impact on domain user accounts.
Forensic Artifacts
Section titled โForensic Artifactsโ- Event ID 4624 (Logon Type 2 or 10): High-priority indicator when
TargetDomainName == DOMAINand user is aDomain Adminon an unhardened endpoint. - Sysmon Event ID 10: Process access events targeting
lsass.exefrom suspicious callers (procdump.exe,rundll32.exe,powershell.exe).
Key Takeaways
Section titled โKey Takeawaysโ- A local administrator has zero direct rights over Active Directory.
- The presence of a Domain Admin on an untrusted endpoint bridges local compromise into domain takeover.
- Enterprise Tiering models strictly prohibit high-privilege credentials on lower-tier assets.
- LAPS neutralizes lateral movement via local password reuse.