Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Sysmon is a free Microsoft Sysinternals tool that adds detailed, security-focused telemetry to Windows: process creation with hashes and parentage, network connections, image loads, and more.

What Is Sysmon?
Windows records a great deal about itself and surprisingly little of what a security analyst needs. Sysmon — System Monitor, part of the Microsoft Sysinternals suite — fills that gap. It installs a driver and a service that watch system activity and write richly detailed events to their own log channel, giving defenders endpoint telemetry of a quality that otherwise requires a commercial agent. It is free, it is supported by Microsoft, and it has become the de facto baseline for Windows detection engineering.
The headline capability is process creation with full context: the command line, the parent image and parent command line, the user, the current directory, and hashes of the executable. That single event type underpins most of what a Security Operations Centre does with Windows data.
| ID | Event | Why it matters |
|---|---|---|
| 1 | Process creation | Command lines, hashes, and parentage for process tree analysis |
| 3 | Network connection | Links an outbound connection to the process that opened it |
| 7 | Image loaded | Detects DLL side-loading and unsigned modules in trusted processes |
| 8 | Remote thread created | A core indicator of process injection |
| 10 | Process access | Catches access to the LSASS process for credential theft |
| 11 | File created | Payload drops, staging directories, and persistence artefacts |
| 12-14 | Registry activity | Run keys, service creation, and configuration tampering |
| 22 | DNS query | Resolution attributed to a process, which DNS server logs cannot do |
| 23, 26 | File delete | Anti-forensic activity, with optional archiving of the deleted file |
| 25 | Process tampering | Process hollowing and image replacement |
Events 15, 17, 18, and 19 to 21 add alternate data stream hashes, named pipe activity, and WMI event subscriptions, the last of which is a favourite persistence mechanism that almost nothing else records. Sysmon for Linux, released in 2021, provides an equivalent subset on Linux hosts.
Installing Sysmon without a configuration file achieves very little: the default captures a fraction of what is available while generating noise from the parts that are. The configuration is an XML document of include and exclude rules, applied per event type, and it is where all the engineering effort goes.
Two public configurations are the standard starting points. The SwiftOnSecurity configuration is heavily commented and built around excluding known-good activity, which makes it a good way to learn the schema. Olaf Hartong’s sysmon-modular splits rules into files mapped to ATT&CK techniques, which suits teams that want to reason about coverage. Either way, treat the file as a starting point, hold it in version control, and tune it for your estate — a build server, a domain controller, and a call centre workstation have very different normal behaviour.
Watch the volume as you go. Image loads and network connections are by far the heaviest event types, and an unfiltered configuration on a busy server can produce tens of gigabytes a day on its own, which turns straight into SIEM cost.
Sysmon installs with a single command and takes its configuration from a file, so Group Policy startup scripts, Intune, or any configuration management tool can deploy it. Updating the configuration later is a separate command, and the usual operational failure is an estate running three different configuration versions because nobody built a mechanism to push changes.
Events land in Microsoft-Windows-Sysmon/Operational and must be forwarded off the host — through Windows Event Forwarding or a log agent — both so they can be correlated and so they survive an attacker with local administrator rights. Raise the channel size on hosts where forwarding may be interrupted.
Sysmon records; it does not block. There is no prevention, no quarantine, and no response capability, so it complements rather than replaces endpoint protection. It is also not tamper-proof: an attacker with SYSTEM privileges can stop the service, unload the driver, or alter the configuration. Renaming the service and driver at install time raises the bar slightly, and alerting on Event ID 16 — configuration change — plus the absence of expected events from a host catches most interference. Forwarding events as they occur matters more than any of this, because an event already in the SIEM cannot be deleted from the endpoint.
For organisations running endpoint detection and response products, much of this telemetry is already collected, and running both doubles the volume. Sysmon earns its place where licences do not reach, where a vendor-independent copy in your own SIEM is wanted, or where a specific event the product does not expose is needed. At Privia Security, we design and tune Windows telemetry of this kind through our SOC maturation services.
Yes. Sysmon is part of the Microsoft Sysinternals suite and is free to download and use, including in commercial environments, under the Sysinternals licence terms. The cost is not the software but the work around it: building and maintaining the configuration, forwarding the events, and paying for the storage and licensing of the volume it produces.
Modest with a sensible configuration, typically low single-digit CPU overhead on normal workloads. The strain usually appears in event volume rather than host performance. Image load and network connection events generate the most, so filter them carefully on busy servers and test any configuration change on a representative host before deploying it widely.
A well-maintained public configuration such as SwiftOnSecurity’s or sysmon-modular, then tune it. Both reflect a great deal of community experience and are far better than starting from nothing. What neither can know is your environment, so budget time for excluding your own legitimate software and for revisiting the file whenever major applications change.
Yes. Sysmon and the built-in Windows logs cover different ground. Authentication events, Kerberos ticket activity, group membership changes, audit policy changes, and service installation are recorded in the Security and System channels, not by Sysmon. A complete Windows detection capability collects both, with Sysmon adding depth on process, network, and file activity.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.