Sysmon (Microsoft-Windows-Sysmon/Operational)
10 ProcessAccess
A process opened another process. With lsass.exe as the target, it is how credential theft from memory shows up.
- SysmonLog
- Microsoft-Windows-SysmonSource
- 3Cases and alerts that use it
Fields to read
| Field | What it tells you |
|---|---|
SourceImage | The process that asked for access. |
TargetImage | The process that was opened (watch for lsass.exe). |
GrantedAccess | The rights: masks with 0x0010 (PROCESS_VM_READ), such as 0x1010 or 0x1FFFFF, can read memory. |
CallTrace | The modules on the call stack; unknown modules are a warning sign. |
Normal
- Antivirus, EDR and crash reporting reading lsass.exe from their own signed folders.
Suspicious
- Any other program reading lsass.exe memory, especially from Temp or a user folder, or through comsvcs.dll.
Find it
Microsoft Sentinel (KQL)
Sysmon
| where EventID == 10Splunk (SPL)
index=sysmon source="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=10Table, index and source names as CyberSim uses them; your workspace may name them differently (Sysmon in Sentinel is a parser function over the Event table, not a built-in table).
Where you meet it in CyberSim
Cases
- Aggressive scanning and a blocked LSASS access Intermediate · Endpoint
- Exposed RDP, credential dumping and shadow copies deleted Advanced · Endpoint
Alerts in the shift
- Credential-store access (LSASS)
The L3 war room
- Kerberoasting to DCSync
- Macro to domain takeover
- Web shell to domain ransomware
ATT&CK techniques it can show
In the glossary
Other Sysmon events
- 1 Process creation
- 3 Network connection
- 11 FileCreate
- 13 RegistryEvent (Value Set)
- 22 DNSEvent (DNS query)
Source: Microsoft Learn: Sysmon