Windows Event ID 4673 — Privileged Service Called
Logged when a process or user attempts to use a sensitive privilege such as SeDebugPrivilege, SeImpersonatePrivilege, or SeTakeOwnershipPrivilege. High-volume or unexpected 4673 events indicate privilege abuse.
MITRE ATT&CK
T1134 · Access Token Manipulation
Privilege Escalation
Why It Matters
Certain privileges allow an attacker to bypass security controls, inject into processes, or take ownership of protected files. SeDebugPrivilege in particular is required for credential dumping tools like Mimikatz to read LSASS memory. A sudden surge of 4673 events from an unexpected process or account is a strong indicator of active exploitation.
Key Fields
Investigation Tips
- 1.SeDebugPrivilege requests from non-system processes (e.g. cmd.exe, powershell.exe, unknown binaries) are high-risk — this privilege is required for LSASS memory access.
- 2.SeImpersonatePrivilege abuse is a common local privilege escalation technique (token impersonation, named pipe attacks) — check the process name and its parent.
- 3.Correlate with Event ID 4663 (object access) on lsass.exe — if 4673 precedes a 4663 on lsass.exe, credential dumping is likely in progress.
- 4.Check whether the requesting process is signed, where it lives on disk, and whether it is a known good binary.
- 5.High-volume 4673 events in a short window indicate automated tooling (e.g. Mimikatz, CobaltStrike) rather than a human interaction.
Go deeper: the full Privilege Escalation — Gaining Admin and Domain Access guide
Explore the related technique, investigation steps, and evidence to consider alongside this event.
Read the Privilege Escalation — Gaining Admin and Domain Access guide →See Event ID 4673 in your logs
Copy the event details as XML and inspect them in your browser. No file upload or hosted analysis is needed.
Decode an event →