Security event 4658
The handle to an object was closed
Channel: Security. Category: Object Access: Audit Handle Manipulation (spans Audit File System / Audit Kernel Object / Audit Registry / Audit Removable Storage).
What it records
Generated when a previously opened handle to an audited object (file, registry key, etc.) is closed, provided Success auditing is enabled for the Audit Handle Manipulation subcategory. Records only the Handle ID and process information, not the object's name.
Why it matters
By itself Microsoft's own guidance notes it typically has 'little to no security relevance'. Its DFIR value comes from correlating its Handle ID back to the earlier 4656 (and 4663) event on the same handle, which lets an analyst determine how long a sensitive object stayed open.
What triggers it
Any process finishing its use of a file/registry/other audited object and releasing the handle: a routine, high-volume event tied to ordinary application I/O far more often than malicious activity.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Handle ID | Correlates back to the 4656 (and 4663) event for the same object: the only way to know which object's handle closed and, combined with timestamps, how long it stayed open. |
| Process Name | The process that closed the handle. |
In practice
A 4656 shows PID 4104 (svchost.exe) opening Handle ID 0xa88 on a share-hosted spreadsheet; minutes later a matching 4658 with the same Handle ID and Process Name svchost.exe confirms the handle closed. Read alone the 4658 says nothing. It's the pairing with the earlier 4656 (and any 4663 access events on that Handle ID) that lets an analyst bound how long the file stayed open.
Sample record
The handle to an object was closed. Subject: Security ID: S-1-5-21-3457937927-2839227994-823803824-1104 Account Name: jdoe Account Domain: CORP Logon ID: 0x3E4B2 Object: Object Server: Security Handle ID: 0x18A8 Process Information: Process ID: 0xEF0 Process Name: C:\Windows\explorer.exe
Sources
Paste a record into Event XML or open a log in EVTX Reader.