OSITC.016 explains how Windows records process launches and how IT technicians can use those records to investigate suspicious activity. A running process is not automatically malicious. The useful questions are which executable started, when it started, which account launched it, and what parent process created it. Two important sources are Windows Security event 4688 and Microsoft Sysmon event 1. Both depend on logging configuration; neither guarantees a complete history after the fact.
Earlier OSITC.004 introduced Event Viewer, while OSITC.015 explored a different security-control design. Process auditing provides evidence about endpoint behavior rather than blocking all harmful programs.
Event 4688: the operating system’s audit record
When Audit Process Creation success auditing is enabled, Windows can write event ID 4688 to the Security log. Fields can include new process name, process identifier, creator process, subject account and elevation details. The command-line field may be absent or blank unless the separate Include command line in process creation events setting is enabled. Microsoft’s event reference and auditing configuration guide document those requirements.
Command-line recording can expose credentials, access tokens or personal information passed as program arguments. Access control, retention and centralized log handling therefore matter. A missing 4688 record may mean collection was disabled, the log rotated, permissions are insufficient or the event falls outside the selected time window.
Read-only inspection with PowerShell
On an authorized Windows system with appropriate Security-log access, the command below lists up to ten recent process-creation events. It does not enable auditing or modify running processes:
Get-WinEvent -FilterHashtable @{
LogName='Security'; ID=4688;
StartTime=(Get-Date).AddHours(-1)
} -MaxEvents 10 |
Select-Object TimeCreated, Id, Message
If no matching events exist, the command may return a no-events error; that alone proves nothing about endpoint compromise. Windows Command #54 covers alternative Event Log queries. Windows Command #55 explains how authorized teams preserve logs for later review.
Sysmon Event 1 adds correlation context
Microsoft Sysmon is a separate system-monitoring capability. Its Process Create event 1 appears in the Sysmon Operational channel when enabled and permitted by its filtering configuration. The event can include executable path, command line, parent information, hashes and a ProcessGuid useful for correlation when Windows later reuses numeric process IDs. Microsoft’s Sysmon documentation explains installation and event semantics; deployment or rule changes require approved change control.
Separate normal automation from genuinely suspicious execution
An office application launching a shell may merit investigation, but software updates, management agents and approved scripts also create process trees. Check executable path, signer, account context, timing, host role and an established baseline before drawing conclusions. A hypothetical workstation recording 240 process starts in five minutes averages 240 ÷ 5 = 48 launches per minute; volume alone is not an indicator of compromise.
Review OSPowerShell.007 for safe iteration over returned objects. For a classroom exercise, compare anonymized 4688 and Sysmon records from the same authorized test machine, identify an expected parent–child pair, and record fields missing from each source. Do not disable logging, execute suspicious payloads or install agents on production hosts without approval.
Lesson conclusion: process creation telemetry provides a valuable timeline, not a verdict. Reliable investigation depends on collection settings, correlation, privacy safeguards and corroborating evidence.

Leave a Reply