Windows Security Log Event ID 4673
| Operating Systems |
Windows 2008 R2 and 7
Windows 2012 R2 and 8.1
Windows 2016 and 10
Windows Server 2019 and 2022
|
Category
• Subcategory | Privilege Use
• Sensitive Privilege Use |
|
Type
|
Success
|
Corresponding events
in Windows
2003
and before |
577
|
4673: A privileged service was called
On this page
Event 4673 indicates that the specified user exercised the user right specified in the Privileges field.
Note: "User rights" and "privileges" are synonymous terms used interchangeably in Windows.
Some user rights are logged by this event - others by 4674. Still other, ""high-volume"" rights are not logged when they are exercised unless you enable the security option "Audit: Audit the use of Backup and Restore privilege".
Unfortunately, Microsoft has overloaded these privileges so that each privilege may govern your authority to perform many different operations and which privilege is required for which operations is not well documented. Therefore seeing that a privilege was exercised doesn't really tell you much. In Win2008 this has been improved with better information in the Server: and Service Name: fields. In general though, I still classify these events as noise. Microsoft admits: "These are high volume events, which typically do not contain sufficient information to act upon since they do not describe what operation occurred."
Note: 4673 and 4674 do not log any activity associated with Logon Rights such as the SeNetworkLogonRight. Do not confuse events 4673 and 4674 with events 4717 and 4718 which document rights assignment changes as opposed to the exercise of rights which is the purpose of events 4673 and 4674.
Subject:
The ID and logon session of the user that excercised the right.
- Security ID: The SID of the account.
- Account Name: The account logon name.
- Account Domain: The domain or - in the case of local accounts - computer name.
- Logon ID is a semi-unique (unique between reboots) number that identifies the logon session. Logon ID allows you to correlate backwards to the logon event (4624) as well as with other events logged during the same logon session.
Service:
These fields help you narrow down what the user exercised the the right for.
- Server: The system component affected
- Service Name: The operation affected
Start a discussion below if you have information on these fields!
Process Information:
These fields tell you the program that exercised the right. The Process Name identifies the program executable. Process ID is the process ID specified when the executable started as logged in 4688.
Service Request Information: Privileges: The names of the privileges just exercised
Free Security Log Resources by Randy
Subject:
- Security ID: %1
- Account Name: %2
- Account Domain: %3
- Logon ID: %4
Service:
- Server: %5
- Service Name: %6
Process:
- Process ID: %8
- Process Name: %9
Service Request Information:
Supercharger Enterprise
Load Balancing for Windows Event Collection
A privileged service was called.
Subject:
Security ID: SYSTEM
Account Name: WIN-R9H529RIO4Y$
Account Domain: WORKGROUP
Logon ID: 0x3e7
Service:
Server: NT Local Security Authority / Authentication Service
Service Name: LsaRegisterLogonProcess()
Process:
Process ID: 0x238
Process Name: C:\Windows\System32\lsass.exe
Service Request Information:
Privileges: SeTcbPrivilege
Top 10 Windows Security Events to Monitor
Free Tool for Windows Event Collection