5 Sysmon log · Process Terminated info severity very-high volume

Sysmon Event ID 5 — Process terminated

A process has terminated. Complements Event 1 for process lifetime analysis.

Why event 5 matters

Short-lived processes (created and terminated within seconds) indicate payload execution. Compare Sysmon 1 (create) + Sysmon 5 (terminate) timestamps.

How to detect it

No standalone alerting. Calculate process lifetimes for forensic timelines.

Log source
Microsoft-Windows-Sysmon/Operational
Requires Sysmon installed with a config that logs this event (e.g. SwiftOnSecurity / Olaf Hartong).
Fields to pivot on
ImageCommandLineParentImageUserHashes

Detection queries

Starting points — adapt the log source, projected fields and thresholds for your environment.

Sentinel / Defender KQL
Event
| where EventLog == "Microsoft-Windows-Sysmon/Operational" and EventID == 5   // Process terminated
// EventData holds: Image, CommandLine, ParentImage, User, Hashes
| project TimeGenerated, Computer, RenderedDescription
| sort by TimeGenerated desc
Splunk SPL
index=* sourcetype="WinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=5
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count   `# Process terminated — add EventData fields: Image, CommandLine, ParentImage, User`
Hunt event 5 in Sentinel/Defender →
Build a KQL query for this event in the KQL Query Builder.
Search all event IDs →
Open the interactive Windows Event ID lookup.

Frequently asked questions

What is Sysmon Event ID 5?

Process terminated. A process has terminated. Complements Event 1 for process lifetime analysis.

Which log records event 5?

Event 5 is written to the Microsoft-Windows-Sysmon/Operational channel by Microsoft-Windows-Sysmon. Requires Sysmon installed with a config that logs this event (e.g. SwiftOnSecurity / Olaf Hartong).

How do you detect activity around event 5?

No standalone alerting. Calculate process lifetimes for forensic timelines.