Detecting Malicious Activity with Sysmon
What you'll learn: How to leverage Sysmon's rich telemetry to identify common attack patterns including lateral movement, credential dumping, and persistence mechanisms.
Understanding Attack Detection Through Sysmon
Now that you've configured Sysmon for comprehensive monitoring, you can use its detailed logs to spot malicious activity that would otherwise hide in plain sight. Sysmon acts like a security camera with x-ray vision—capturing not just what processes run, but how they behave, who spawned them, and what they touch.
Common Attack Patterns to Detect
Lateral Movement
Watch for Event ID 3 (Network Connection) combined with Event ID 1 (Process Creation). Suspicious patterns include:
psexec.exeorwmic.exespawning processes remotely- Unusual parent-child relationships like
svchost.exespawning command shells - SMB connections (port 445) from unexpected processes
Credential Dumping
Monitor Event ID 10 (Process Access) for tools trying to read lsass.exe memory:
- Non-system processes accessing LSASS with
PROCESS_VM_READpermissions - Known dumping tools like
mimikatz,procdump, or suspicious PowerShell accessing LSASS
Persistence Mechanisms
Track Event ID 13 (Registry Modification) and Event ID 11 (File Creation):
- Modifications to Run keys or services in the registry
- New scheduled tasks or startup folder entries
- DLL hijacking through file creation in system directories
Analysis Approach
Think of Sysmon data like puzzle pieces. Individual events might seem benign, but correlating multiple events reveals the attack story: a process creation followed by registry modification and network connection could indicate malware establishing persistence and phoning home.
Key Takeaway: Sysmon detection requires correlating multiple event types—lateral movement, credential access, and persistence mechanisms all leave distinct telemetry signatures that reveal attacker behavior when analyzed together.