CyberKit

Process Creation Auditing

Also called Event ID 4688, Process Tracking.

Logging every new process start, ideally with its full command line.

What it is

A Windows audit capability that writes an event each time a process is created, capturing the executable, the parent process, and (when command-line auditing is also enabled), the full arguments. It corresponds to Security log Event ID 4688 and must be turned on through audit policy.

Why it matters

Process creation events with command lines are foundational for incident response: they reveal what ran, what launched it, and exactly how it was invoked, which exposes both malware and abuse of legitimate tools. Without command-line capture enabled, defenders see that something ran but not what it actually did.

In practice

A 4688 event showing certutil.exe launched with -urlcache and a remote URL, flagging a built-in binary being abused to download a payload.

What to look for

  • Event 4688 with the command line field filled in.
  • Parent and child process pairs.
  • Processes started from temp, downloads or public folders.

Common mistake

Enabling 4688 without command line logging. The process name alone rarely tells you enough.

Use it in CyberKit

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Splunk Enterprise Security Commercial

    A SIEM where these logs are searched with SPL and turned into correlation searches.

  • Microsoft Sentinel Commercial

    Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.

  • Elastic Security Commercial

    A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.

  • Wazuh Open source

    An open source platform that collects, decodes and alerts on host and log data.

Read next

  • Sysmon: Free Windows driver that logs rich process, network, and file telemetry.
  • PowerShell Logging: Recording PowerShell commands, scripts, and pipeline activity for audit.
  • Telemetry Gap: A blind spot where the data needed to detect activity isn't collected.

Sources