Course contentsShow
← Security
Lesson 1513 of 3,05230. Operating System Security - MonitoringFree lesson

Sysmon Process and Network Monitoring

Tracking process creation, termination, network connections, and parent-child relationships with Sysmon events.

Sysmon Process and Network Monitoring

You'll learn how to track process creation, termination, network connections, and parent-child relationships using Sysmon events.

What Sysmon Tracks

Sysmon (System Monitor) creates detailed events that capture the full lifecycle of processes and their network activity. Think of it as a security camera system for your operating system — it records who did what, when, and how they're connected.

Core Process Monitoring

Sysmon's Event ID 1 (Process Creation) logs every new process, including:

  • Full command line with arguments
  • Parent process (which program launched it)
  • User account executing it
  • Process integrity level and hashes

Event ID 5 (Process Termination) records when processes end, letting you track execution duration and abnormal exits.

The parent-child relationship is crucial: if explorer.exe spawns powershell.exe, you see that chain. But if winword.exe unexpectedly launches cmd.exe, that's suspicious — documents shouldn't create command shells.

Network Connection Tracking

Event ID 3 (Network Connection) captures:

  • Source and destination IP addresses and ports
  • Protocol used (TCP/UDP)
  • Which process initiated the connection
  • Connection direction (inbound/outbound)

This reveals hidden communications. A text editor shouldn't make network connections to foreign IP addresses — that could indicate malware exfiltrating data.

Why This Matters

Traditional Windows logs tell you "something happened." Sysmon tells you the complete story: which user ran what command, what child processes it spawned, and where data was sent over the network. This process genealogy is essential for detecting lateral movement, privilege escalation, and data exfiltration.

Key Takeaway: Sysmon's process and network events provide detailed visibility into program execution chains and network behavior, enabling detection of suspicious parent-child relationships and unauthorized network communications that standard Windows logging misses.