Sysmon
Named by 18 kept items in this workspace.
11 items name it under tools, 6 under classification.technologies and 1 under affected products.
Search every workspace for Sysmon. It matches the name as written, so it can find other things that share it.
The items that name it 18
Used for detection via Event ID 10 (ProcessAccess) to identify unexpected processes obtaining handles to lsass.exe
Endpoint telemetry (Event IDs 1, 3, 7) suggested for detecting AppxPackage registration, outbound connections, and DLL loads from AppX package paths
Logging tool whose processes (sysmon.exe, sysmon64.exe) were killed, services stopped/deleted, and later frozen via IFEO debugger settings
Endpoint monitoring; Event ID 13 for registry modification detection (WDigest, SSP, Password Filter, NetworkProvider keys), Event ID 11 for file creation detection of new DLLs in System32.
Endpoint telemetry tool compared against MDE telemetry (via Olaf Hartong's Sysmon vs MDE overview)
Cited as a tool that adopted ETW as a tracing source
Logging tool used to observe file creation events revealing the TfsStore\Tfs_DAV cache directory
Used by the author to capture Process Create and File Create events showing the infection chain (command lines, parent command lines)
Installed to determine execution vector of malicious code, capturing process creation and parent-child relationships
SysInternals tool for monitoring registry key creation (event ID 13, e.g. Run keys), file write events in AppData, and network connections with destination/port/application
Endpoint logging tool used to capture process creation and other events (e.g., Event Code 1) for detection of Cobalt Strike activity
Recommended install on Windows hosts to generate detailed events for detection
All technologies in this workspace.