Skip to content
CyberSimStart training

Windows Security log

4688 A new process has been created.

A process started. The command line is only included when the policy "Include command line in process creation events" is on, which is why many SOCs rely on Sysmon event 1 instead.

Fields to read

FieldWhat it tells you
NewProcessNameThe program that started.
CommandLineIts arguments (with the policy on).
ParentProcessNameThe program that started it.
SubjectUserNameThe account.
TokenElevationType%%1936 full token (UAC off or built-in admin), %%1937 elevated, %%1938 limited.

Normal

  • Thousands per hour on every host: installers, updaters, scripts by IT.

Suspicious

  • Office, a PDF reader or a browser starting cmd.exe, PowerShell or a script host.
  • PowerShell with -enc or a download cradle; certutil, mshta or rundll32 with a URL.

Find it

Microsoft Sentinel (KQL)

SecurityEvent
| where EventID == 4688

Splunk (SPL)

index=wineventlog source="XmlWinEventLog:Security" EventCode=4688

Table, index and source names as CyberSim uses them; your workspace may name them differently.

Where you meet it in CyberSim

Cases

Alerts in the shift

In the glossary

Other Security events

Source: Microsoft Learn: event 4688