Event ID 4690
An attempt was made to duplicate a handle to an objectAn attempt was made to duplicate a handle to an object.
Subject:
Security ID: %1
Account Name: %2
Account Domain: %3
Logon ID: %4
Source Handle Information:
Source Handle ID: %5
Source Process ID: %6
New Handle Information:
Target Handle ID: %7
Target Process ID: %8This event generates if an attempt was made to duplicate a handle to an object.
Auditing: Rarely This event has little security relevance.
| Name | Field | Insertion String | OS | Example | |
|---|
| Security ID | SubjectUserSid | %1 | Any | S-1-5-18 |
| Account Name | SubjectUserName | %2 | Any | DC01$ |
| Account Domain | SubjectDomainName | %3 | Any | DOMAIN |
| Logon ID | SubjectLogonId | %4 | Any | 0x3e7 |
| Source Handle ID | SourceHandleId | %5 | Any | 0x438 |
| Source Process ID | SourceProcessId | %6 | Any | 0x674 |
| Target Handle ID | TargetHandleId | %7 | Any | 0xd9c |
| Target Process ID | TargetProcessId | %8 | Any | 0x4 |
SID of account that made an attempt to duplicate a handle to an object. Event Viewer automatically tries to resolve SIDs and show the account name. If the SID cannot be resolved, you will see the source data in the event.
Note A security identifier (SID) is a unique value of variable length used to identify a trustee (security principal). Each account has a unique SID that is issued by an authority, such as an Active Directory domain controller, and stored in a security database. Each time a user logs on, the system retrieves the SID for that user from the database and places it in the access token for that user. The system uses the SID in the access token to identify the user in all subsequent interactions with Windows security. When a SID has been used as the unique identifier for a user or group, it cannot ever be used again to identify another user or group.
The name of the account that made an attempt to duplicate a handle to an object.
Subject’s domain or computer name. Formats vary, and include the following:
Domain NETBIOS name example: DOMAIN
Lowercase full domain name: domain.local
Uppercase full domain name: DOMAIN.LOCAL
For some well-known security principals, such as LOCAL SERVICE or ANONYMOUS LOGON, the value of this field is “NT AUTHORITY”.
For local user accounts, this field will contain the name of the computer or device that this account belongs to, for example: “ComputerName”.
Hexadecimal value that can help you correlate this event with recent events that might contain the same Logon ID, for example, “4624: An account was successfully logged on.”
Hexadecimal value of a handle which was duplicated. This field can help you correlate this event with other events, for example “4663: An attempt was made to access an object” in Audit File System, Audit Kernel Object, Audit Registry, Audit Removable Storage or Audit SAM subcategories.
Hexadecimal Process ID of the process which opened the Source Handle ID before it was duplicated.
Hexadecimal value of the new handle (the copy of Source Handle ID). This field can help you correlate this event with other events, for example “4663: An attempt was made to access an object” in Audit File System, Audit Kernel Object, Audit Registry, Audit Removable Storage or Audit SAM subcategories.
Hexadecimal Process ID of the process which opened the Target Handle ID. Process ID (PID) is a number used by the operating system to uniquely identify an active process. You can also correlate this process ID with a process ID in other events, for example, “4688: A new process has been created” Process Information\New Process ID field.
Lookup Audit Policy Configuration Settings
C:\> AuditPol.exe /get /subcategory:"Handle Manipulation"
Legacy Events:
594Correlated Events:
4663
LEFT/RIGHT arrow keys for navigation
Back to List