Repository navigation
feat(soc): every Windows agent reads the Sysmon channel (#1035) - #1036
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The shared configuration, mounts, and documentation are consistent, while deployment proof is explicitly deferred without closing the tracking issue.
0 open findings
What changed in this PR
Adds centralized Sysmon event collection for all default-group Windows Wazuh agents.
Changes:
- Adds and mounts a shared Windows
agent.confin SOC and scratch stacks. - Documents synchronization and alert verification.
- Corrects historical issue references while preserving ADR history.
| File | Description |
|---|---|
stacks/soc/wazuh/manager/shared/default/agent.conf |
Collects the Sysmon event channel. |
stacks/soc/README.md |
Documents the shared configuration file. |
stacks/soc/compose.yaml |
Mounts the configuration into Wazuh. |
stacks/scratch/compose.yaml |
Reuses the configuration in scratch. |
docs/runbooks/build-the-soc-guest.md |
Documents synchronization and alert checks. |
docs/runbooks/build-the-lab-domain.md |
Records that Wazuh now reads Sysmon. |
docs/changelog.md |
Adds the dated implementation record. |
docs/adr/0080-record-the-lab-domain-with-sysmon-and-capture-on-demand-with-pktmon.md |
Adds a historical correction note. |
ansible/roles/sysmon/defaults/main.yml |
Updates the channel-retention comment. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The default group's shared agent.conf, mounted into the manager through /wazuh-config-mount as ossec.conf already is, adds an eventchannel localfile for Microsoft-Windows-Sysmon/Operational to Windows agents. The manager's ruleset already decodes it; the MSI's ossec.conf never collected it. stacks/scratch mounts the same file. ADR-0080 gets a note: it said this belonged to #266, which was the Wazuh build and is closed. The role comment and the lab runbook are corrected in place. Refs #1035 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gerrrt
force-pushed
the
gerrrt/wazuh-sysmon-channel-1035
branch
from
October 7, 2026 17:01
572856c to
696b1fe
Compare
Gerrrt
enabled auto-merge (squash)
October 7, 2026 17:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #1035. This is authored ahead of the proof. #1035 closes once a Sysmon event from a domain guest shows up as an alert on
odin, and that has to wait for #448's rebuild to bring the six back.What
stacks/soc/wazuh/manager/shared/default/agent.confis thedefaultgroup's shared agent config. Under<agent_config os="Windows">it adds oneeventchannel<localfile>forMicrosoft-Windows-Sysmon/Operational./wazuh-config-mount/etc/shared/default/agent.conf. That is the image's own mechanism:cp -rover/var/ossecon every start, the same wayossec.confarrives. Copying onto the existing placeholder keeps itswazuh:wazuh 0660.ansible/roles/soc_agentsdoes not change. A rebuilt guest gets it when it enrols.stacks/scratchmounts the same file, so a Windows agent enrolled there reads Sysmon as it would onodin.build-the-soc-guest.md§11 says what each agent reads, and how to check an agent is synced (agent_groups -S -i <id>) and that Sysmon alerts arrive (rule.groups: sysmon).[!NOTE]. It had said Wazuh reading the channel "belongs to Run Wazuh on Saruman — the heaviest component in ADR-0007 #266"; Run Wazuh on Saruman — the heaviest component in ADR-0007 #266 was running Wazuh, and it was already closed. The same wrong reference in the role's comment and in the lab runbook is corrected in place.Read on
odinbefore writing it (2026-10-07)0595-win-sysmon_rules.xml, plus0800–0950for events 1, 3, 7, 8, 10, 11, 13 and 20.shared/default/agent.confwas upstream's empty placeholder.verify-agent-conf -fon this file, inside the running manager:OK.Not done here: deploy and proof
odinafter merge withmake up STACK=soc. odin's checkout was last left on a Harden the Wazuh and lab-store containers, and bound and healthcheck the soc and sensor Alloys #845 branch, so checkgit statusthere first.agent_groups -S -ishows each agent synced;whoami /allon an endpoint arrives inwazuh-alerts-*as Sysmon event 1, matched by asysmonrule group, with its command line.Checks run locally
check_docs.pypasses;check_compose_health.pypasses on soc and--cross-stack;check_image_pins.pypasses;check_close_keywords.pypasses on the body and the commit.🤖 Generated with Claude Code