Security event 4673
A privileged service was called
Channel: Security. Category: Privilege Use (Audit Sensitive Privilege Use / Audit Non Sensitive Privilege Use).
What it records
Generated when an attempt is made to perform a privileged system-service operation: e.g., using SeTcbPrivilege, SeSystemtimePrivilege, or SeCreateGlobalPrivilege. A Failure event is logged if the privileged service call fails.
Why it matters
Records the moment a held privilege is actually exercised. That pinpoints when and how a sensitive privilege such as SeDebugPrivilege or SeTcbPrivilege was used, which can indicate credential-dumping tooling, time-stomping (SeSystemtimePrivilege), or other privileged tampering. 4672 records a privilege being assigned at logon; this one records it being used. The Process Name/ID ties the call back to the specific executable responsible.
What triggers it
Normal OS/service operations (e.g., LSASS calling LsaRegisterLogonProcess() using SeTcbPrivilege) as well as abuse of a held privilege by administrative tools or malware.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Server (Service\Server) | The Windows subsystem that serviced the privileged call (e.g. NT Local Security Authority/Authentication Service, SC Manager), which scopes which part of the OS the privilege was exercised against. |
| Service Name | The specific privileged function invoked (e.g. LsaRegisterLogonProcess()), which identifies exactly what operation used the privilege. |
| Privileges | The specific privilege used (e.g. SeDebugPrivilege, SeTcbPrivilege, SeSystemtimePrivilege). SeSystemtimePrivilege use is notable for time-stomping, SeDebugPrivilege for credential-dumping tooling. |
| Process Name | The process that made the privileged call, which ties the privilege use to a specific executable. |
In practice
A 4673 with Process Name lsass.exe, Service Name LsaRegisterLogonProcess(), and Privileges SeTcbPrivilege is routine. LSASS legitimately exercises SeTcbPrivilege on every logon. A 4673 instead showing an unexpected Process Name using SeSystemtimePrivilege is notable, since that privilege is what lets a process alter the system clock, a technique sometimes used to time-stomp file metadata.
Sample record
A privileged service was called. Subject: Security ID: S-1-5-18 Account Name: DC01$ Account Domain: CORP Logon ID: 0x3E7 Service: Server: NT Local Security Authority / Authentication Service Service Name: LsaRegisterLogonProcess() Process: Process ID: 0x1F0 Process Name: C:\Windows\System32\lsass.exe Service Request Information: Privileges: SeTcbPrivilege
Sources
Paste a record into Event XML or open a log in EVTX Reader.