Detecting Sysmon on the Victim Host
Exploring ways to detect Sysmon presence on the victim system

PS C:\> Get-Process | Where-Object { $_.ProcessName -eq "Sysmon" }
Note: process name can be changed during installation

Get-CimInstance win32_service -Filter "Description = 'System Monitor service'"
# or
Get-Service | where-object {$_.DisplayName -like "*sysm*"}
Note: display names and descriptions can be changed

reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Sysmon/Operational

PS C:\> fltMC.exe
Note how even though you can change the sysmon service and driver names, the sysmon altitude is always the same - 385201

ls HKCU:\Software\Sysinternals

Once symon executable is found, the config file can be checked like so:
sysmon -c

If you are lucky enough, you may be able to find the config file itself on the disk by using native windows utility findstr:
findstr /si '<ProcessCreate onmatch="exclude">' C:\tools\*

A powershell tool by @mattifestation that extracts sysmon rules from the registry:
PS C:\tools> (Get-SysmonConfiguration).Rules
As an example, looking a bit deeper into the ProcessCreate rules:
We can see the rules almost as they were presented in the sysmon configuration XML file:
A snippet from the actual sysmonconfig-export.xml file:

Since Get-SysmonConfiguration gives you the ability to see the rules sysmon is monitoring on, you can play around those.
Another way to bypass the sysmon altogether is explored here:

Operating Offensively Against Sysmon
Shell is Only the Beginning
PSSysmonTools/SysmonRuleParser.ps1 at master · mattifestation/PSSysmonTools
Allocated filter altitudes - Windows drivers
GitHub - GhostPack/Seatbelt: Seatbelt is a C# project that performs a number of security oriented host-survey "safety checks" relevant from both offensive and defensive security perspectives.
Copy link
On this page
Windows Events
Sysmon Tools + Accepted Eula
Sysmon -c
Config File on the Disk
Bypassing Sysmon