CyberKit

Event IDs

Sysmon event 5

Process terminated

Channel: Microsoft-Windows-Sysmon/Operational. Category: Process Termination.

What it records

Reports when a process ends, providing the UtcTime, ProcessGuid, and ProcessId of the process.

Why it matters

Paired with its corresponding Event 1, it lets an analyst establish the full lifetime of a process, which is useful for building an accurate process-execution timeline during a reconstruction.

What triggers it

Normal process exit on completion, user- or admin-initiated termination, or a short-lived malicious process (e.g. a dropper) exiting after spawning a payload.

Fields that carry the answer

Key fields
FieldWhat it tells you
ImageThe path of the process that exited. Pair with the matching Event 1 to see what actually ran before it terminated.
ProcessGuidThe unique identifier used to pivot to the matching Event 1 (creation) and compute the process's exact lifetime: critical for spotting short-lived droppers that launch a payload and immediately exit.
ProcessIdThe OS process ID at time of exit, useful for correlating same-session events, though it can be reused later so ProcessGuid is the more reliable pivot.

In practice

ProcessGuid ties back to a prior Event ID 1 for Image C:\Users\jsmith\AppData\Local\Temp\payload.exe; comparing the two UtcTime values shows the process ran for only a few seconds, consistent with a dropper that executes, spawns a child, and exits immediately.

Sample record

Process terminated:
RuleName: -
UtcTime: 2024-01-15 14:32:11.982
ProcessGuid: {5a8f3c2b-7e46-65b0-1400-000000001d00}
ProcessId: 5566
Image: C:\Users\jsmith\AppData\Local\Temp\payload.exe
User: CORP\jsmith

Sources

Paste a record into Event XML or open a log in EVTX Reader.