CyberKit

Event IDs

Security event 4689

A process has exited

Channel: Security. Category: Detailed Tracking (Audit Process Termination).

What it records

Generates every time a process exits. Records the process name and PID, the account that requested termination, and the process's exit status code.

Why it matters

Closes out a process's lifetime in the timeline started by 4688, which helps confirm when a suspicious process stopped running, supports dwell-time analysis of a tool/implant, and its Process ID can be correlated back to the matching 4688 New Process ID.

What triggers it

Normal completion of any process: a user closing an app, a script finishing, a process being killed via Task Manager/taskkill, or malware self-terminating after execution.

Fields that carry the answer

Key fields
FieldWhat it tells you
Process NameFull path/name of the process that exited. Correlate back to its 4688 launch event to bound the process's runtime.
Process IDPID of the terminated process: the key for correlating back to the matching 4688 New Process ID.
Exit StatusHex exit code: application-specific, but an unusual code can indicate a crash, a killed process, or a tool failing partway through execution.

In practice

A 4689 records Process Name C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, Process ID 6820, and Exit Status 0x0 for account CORP\jsmith, correlating the Process ID back to the matching 4688 launch event lets an analyst bound exactly how long that PowerShell instance ran before it exited cleanly.

Sample record

A process has exited.

Subject:
	Security ID:		S-1-5-21-3457937927-2839227994-823803824-1104
	Account Name:		jsmith
	Account Domain:		CORP
	Logon ID:		0x2A9F31

Process Information:
	Process ID:		0x1a6c
	Process Name:		C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
	Exit Status:		0x0

Sources

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