Security event 4660
An object was deleted
Channel: Security. Category: Object Access (Audit File System / Audit Kernel Object / Audit Registry).
What it records
Generated when an object that has 'Delete' auditing set in its SACL is actually deleted. Contains only the Handle ID (not the object's name): the name must be resolved by correlating back to the 4656 event that shares the same Handle ID.
Why it matters
Confirms a genuine delete operation occurred, as distinct from 4663 (which also fires for other operations such as renames): valuable for anti-forensic/evidence-destruction investigations, e.g., an intruder deleting logs, dropped tools, or staged data. Microsoft's own guidance actually recommends using 4663 with DELETE access instead, since it captures the object name directly.
What triggers it
Routine file/registry cleanup by users or applications, or deliberate anti-forensic deletion by malware or an intruder covering their tracks. Requires 'Delete' auditing to be explicitly configured in the object's SACL: not enabled by default.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Handle ID | Correlates back to the 4656 event sharing the same handle, required to resolve which object was actually deleted, since 4660 itself doesn't carry the object name. |
| Process Name | The process that performed the delete, which identifies the tool or application responsible. |
| Transaction ID | Groups this delete with other transactional operations (e.g. the matching 4656) sharing the same transaction. |
In practice
A 4660 with Handle ID 0x1f90 and Process Name cmd.exe fires seconds after a 4656 opened the same Handle ID against C:\Windows\Temp\stager.exe with Delete auditing configured on that folder's SACL: confirming the file was actually deleted, not just renamed, consistent with an intruder removing a dropped tool. Because 4660 itself never carries the object name, an analyst has to pivot to the 4656 sharing that Handle ID to know what was deleted.
Sample record
An object was deleted.
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: 0x1678
Process Information:
Process ID: 0xEF0
Process Name: C:\Windows\explorer.exe
Transaction ID: {00000000-0000-0000-0000-000000000000}Sources
Paste a record into Event XML or open a log in EVTX Reader.