Sysmon Event ID 10: process access
What Sysmon Event ID 10 (process access) means, the fields to check, what is normal and what is suspicious, with PowerShell and KQL queries to find it.
Sysmon Event ID 10 records one process opening another. Most of that is noise, but one target matters a lot: lsass.exe, which holds credentials in memory. Credential dumping tools have to open LSASS, and Event ID 10 is where that shows.
The fields that matter
| Field | What it tells you |
|---|---|
| SourceImage | The process that opened the other one. |
| TargetImage | The process that was opened. Focus on C:\Windows\System32\lsass.exe. |
| GrantedAccess | The rights requested. 0x1010, 0x1410, 0x1438, 0x143a and 0x1fffff are common in dumping tools. |
| CallTrace | The modules in the call stack. dbghelp.dll or dbgcore.dll, or UNKNOWN entries, are red flags. |
What is normal
Security products, Windows services and management agents opening LSASS for legitimate reasons.
When Sysmon Event ID 10 is suspicious
- An unsigned program, or one in a user or temp folder, opening LSASS.
rundll32.exewithcomsvcs.dll(the MiniDump trick),procdump, or Task Manager creating a dump.- CallTrace with
UNKNOWN, which suggests injected or unbacked code.
Common false positive: Antivirus and EDR products open LSASS constantly. Exclude their exact paths and signatures rather than broad names.
Find Sysmon Event ID 10 with PowerShell
Get-WinEvent -FilterHashtable @{LogName='Microsoft-Windows-Sysmon/Operational'; Id=10; StartTime=(Get-Date).AddDays(-7)} -MaxEvents 50 |
ForEach-Object {
$d = [ordered]@{ Time = $_.TimeCreated; Computer = $_.MachineName }
([xml]$_.ToXml()).Event.EventData.Data | ForEach-Object { $d[$_.Name] = $_.'#text' }
[pscustomobject]$d
} | Format-List
Microsoft Sentinel (KQL)
Event
| where TimeGenerated > ago(7d) and Source == "Microsoft-Windows-Sysmon" and EventID == 10
| project TimeGenerated, Computer, RenderedDescription, EventData
| order by TimeGenerated desc
Related events
- Sysmon Event ID 1: process creation
- Event ID 4688: New process created
- Event ID 4624: Successful logon
FAQ
Why is Sysmon Event ID 10 so noisy?
Processes open each other all the time. Most configurations log only access to a few sensitive targets such as LSASS.
How do I protect LSASS?
Turn on LSA protection (RunAsPPL) and Credential Guard, and the attack surface reduction rule that blocks credential stealing from LSASS.
Windows Event Triage reads a CSV, EVTX-to-JSON or XML export in your browser and flags brute force, new admins, suspicious services and log clearing.
IOC Triage, our free browser extension: right-click it for a verdict from 15 threat-intel sources, then copy a ready ticket note.