Security event 4688
A new process has been created
Channel: Security. Category: Detailed Tracking (Audit Process Creation).
What it records
Generates every time a new process starts. Records the new process's PID and full image path, the parent/creator process, the account under which it ran, the token elevation type, and, only if the 'Include command line in process creation events' Group Policy is enabled, the full command line (empty by default).
Why it matters
One of the single most valuable DFIR events on a Windows host: process-execution timelines are reconstructed from it, letting an analyst see exactly what ran, who ran it, from what parent, and (with command-line auditing enabled) with what arguments. Critical for spotting living-off-the-land binary abuse and suspicious parent-child chains (e.g., an Office app spawning cmd.exe/powershell.exe).
What triggers it
Any executable launch: ordinary user/application activity as well as malware execution, script interpreters, and LOLBins. Command-line capture must be explicitly enabled via Group Policy; it is not logged by default.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| New Process Name | Full path of the executable that just launched: the base signal for building a process-execution timeline and spotting suspicious binaries or LOLBins. |
| Process Command Line | Full command line including arguments, only populated if 'Include command line in process creation events' Group Policy is enabled, but when present it's the richest field for spotting malicious script/PowerShell invocations. |
| Creator Process Name | The parent process that spawned this one, which exposes suspicious parent-child chains (e.g. winword.exe spawning cmd.exe or powershell.exe). |
| New Process ID | PID of the new process, used to correlate forward to its matching 4689 exit event. |
| Token Elevation Type | Whether the process ran with a full, elevated, or limited UAC token, which flags unexpected elevation (Type 2 / %%1937) on a standard user account. |
| Account Name (Creator/Target Subject) | The account that launched the process. Microsoft notes it's unusual for either field to show a local account rather than a domain or service identity. |
In practice
A 4688 shows New Process Name C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe, Creator Process Name C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE, and (with command-line auditing enabled) Process Command Line powershell.exe -enc <base64> for Account Name CORP\jsmith: a Word document spawning an encoded PowerShell command is a classic macro-malware execution chain an analyst would flag immediately from the parent-child pairing alone.
Sample record
A new process has been created. Creator Subject: Security ID: S-1-5-21-3457937927-2839227994-823803824-1104 Account Name: jdoe Account Domain: CORP Logon ID: 0x3E4B2 Target Subject: Security ID: S-1-0-0 Account Name: - Account Domain: - Logon ID: 0x0 Process Information: New Process ID: 0x1A44 New Process Name: C:\Windows\System32\cmd.exe Token Elevation Type: TokenElevationTypeLimited (3) Mandatory Label: Mandatory Label\Medium Mandatory Level Creator Process ID: 0xF68 Creator Process Name: C:\Windows\explorer.exe Process Command Line: C:\Windows\System32\cmd.exe /c whoami Token Elevation Type indicates the type of token that was assigned to the new process in accordance with User Account Control policy. Type 1 is a full token with no privileges removed or groups disabled. A full token is only used if User Account Control is disabled or if the user is the built-in Administrator account, service account, or local system account. Type 2 is an elevated token with no privileges removed or groups disabled. An elevated token is used when User Account Control is enabled and the user chooses to start the program using Run as administrator. An elevated token is also used when an application is configured to always require administrative privilege or to always require maximum privilege, and the user is a member of the Administrators group. Type 3 is a limited token with administrative privileges removed and administrative groups disabled. The limited token is used when User Account Control is enabled, the application does not require administrative privilege, and the user does not choose to start the program using Run as administrator.
Sources
Paste a record into Event XML or open a log in EVTX Reader.