| 1 | --- |
| 2 | title: Sysmon config (Windows) |
| 3 | description: Centralized Sysmon configuration management for Windows telemetry collected by Wazuh. |
| 4 | --- |
| 5 | |
| 6 | # Sysmon config (Windows) |
| 7 | |
| 8 | **Menu:** Agents → Sysmon Config |
| 9 | |
| 10 | Sysmon (System Monitor) is a Microsoft Sysinternals tool that logs high-value system activity to the **Windows Event Log**. We use it on Windows endpoints to collect richer telemetry (process, network, file, etc.) that improves detections and investigations. |
| 11 | |
| 12 | In the CoPilot stack: |
| 13 | - **Sysmon** generates telemetry on the Windows endpoint |
| 14 | - The **Wazuh agent** collects Sysmon events |
| 15 | - The **Wazuh manager** is the source of truth and forwards that telemetry into the SIEM |
| 16 | |
| 17 |  |
| 18 | |
| 19 | --- |
| 20 | |
| 21 | ## Why we use Sysmon |
| 22 | |
| 23 | Windows Security logs are useful, but Sysmon provides additional, security-relevant telemetry that is widely adopted in SOC environments. |
| 24 | |
| 25 | Benefits: |
| 26 | - higher-fidelity investigation data (what ran, how it ran, what it talked to) |
| 27 | - better detection coverage for common attacker techniques |
| 28 | - consistent event schemas when you standardize a baseline configuration |
| 29 | |
| 30 | --- |
| 31 | |
| 32 | ## What this page is |
| 33 | |
| 34 | A centralized place to manage Sysmon configuration files so you can: |
| 35 | - keep Windows telemetry consistent across endpoints |
| 36 | - tune noise (exclude expected/benign activity) |
| 37 | - roll out changes per customer/group |
| 38 | |
| 39 |  |
| 40 | |
| 41 | --- |
| 42 | |
| 43 | ## How Sysmon config management works in CoPilot (high level) |
| 44 | |
| 45 | Based on the workflow in the video: |
| 46 | |
| 47 | 1) You maintain a Sysmon config (XML) |
| 48 | 2) CoPilot writes the config into the appropriate Wazuh shared group directory (typically per Windows customer group) |
| 49 | 3) Endpoints receive the updated file via Wazuh agent group sync |
| 50 | 4) A reload mechanism applies the new Sysmon config without requiring a reboot (implementation depends on your environment) |
| 51 | |
| 52 | --- |
| 53 | |
| 54 | ## Step 1 — Review and edit the Sysmon config |
| 55 | |
| 56 |  |
| 57 | |
| 58 | Operator/engineer tips: |
| 59 | - Make small, intentional changes |
| 60 | - Track versions and keep a rollback path |
| 61 | - Prefer customer/group-specific configs when environments differ (EDR tools, server roles, etc.) |
| 62 | |
| 63 | --- |
| 64 | |
| 65 | ## Step 2 — Apply / reload the config |
| 66 | |
| 67 |  |
| 68 | |
| 69 | A practical pattern is to reload Sysmon after pushing a new config so changes take effect quickly. |
| 70 | |
| 71 | Why this matters: |
| 72 | - you can respond to noise quickly (exclude noisy, expected software) |
| 73 | - you can add coverage quickly when a new detection need appears |
| 74 | |
| 75 | --- |
| 76 | |
| 77 | ## Using Sysmon to reduce SIEM noise |
| 78 | |
| 79 | Sysmon configs can be very detailed. A common problem is “too much telemetry.” |
| 80 | |
| 81 | Use this page to: |
| 82 | - exclude known-benign software that generates high event volume |
| 83 | - reduce ingestion costs (compute + storage) |
| 84 | - keep detections focused on high-signal telemetry |
| 85 | |
| 86 | Example from the video context: |
| 87 | - if an endpoint is running an EDR tool and Sysmon is generating noisy events around specific event IDs, you can add exclusions so you don’t ingest bloat into the SIEM. |
| 88 | |
| 89 | Video context: |
| 90 | - https://www.youtube.com/watch?v=XT1d49HTqQw |
| 91 | |
| 92 | --- |
| 93 | |
| 94 | ## Gotchas |
| 95 | |
| 96 | - Sysmon configs can be complex—test changes on a small set of endpoints first. |
| 97 | - Any change can shift event volume dramatically—coordinate with index/retention planning. |
| 98 | - A broken config may fail to apply; keep validation and rollback procedures. |