Repository navigation
feat(soc): enrol garuda in odin's Wazuh and Velociraptor (ADR-0092) - #1163
Merged
Merged
Conversation
Phase 2 of the analyst workstation, the first Linux guest in either. - ADR-0092: two Debian packages staged on odin and served on 8448, which now also answers garuda (.62); enrolment by garuda's runbook, as ADR-0077 keeps Linux guests out of ansible/. - stacks/soc/linux-agents.yaml: the Wazuh agent 4.14.8 .deb, pinned by version and sha256. The hash agrees with Wazuh's apt index, covered by a good signature on InRelease from the Wazuh Signing Key. - stage-agent-msis.sh: also stages that .deb, and a Velociraptor client .deb the server builds with its config inside (kept per server version, its sha256 printed). - WazuhAgentsNotConnected: garuda's agent is expected while garuda's Alloy is up; three promtool cases. - garuda's runbook section 12, phase 2: fetch, check both hashes, install, enrol with the password on standard input only. Teardown becomes section 13. - ADR-0030's port table, security.md's 8448 row, the SOC README, roadmap, architecture, network and changelog say who is served now. Refs #921. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ol-921 # Conflicts: # docs/changelog.md
There was a problem hiding this comment.
🟡 Changes recommended
Reused Debian packages bypass validation, and several documentation and ADR inconsistencies remain.
5 open findings
Validate reused deb artifacts before publishing · New Preserve accepted ADR history and document Garuda consumers separately · New Resolve conflicting first-start package initialization documentation · New Complete threat-model updates for the newly allowed deb path · New Update operator references for deb staging and the expanded allowlist · New
What changed in this PR
Enrols garuda in odin’s Wazuh and Velociraptor services as issue #921 phase 2.
Changes:
- Stages and serves pinned Linux agent packages.
- Extends Wazuh monitoring to
garuda. - Adds ADR-0092 and deployment documentation.
| File | Description |
|---|---|
stacks/soc/README.md |
Documents Linux agent packages. |
stacks/soc/linux-agents.yaml |
Pins the Wazuh Debian package. |
stacks/soc/Caddyfile |
Allows garuda to fetch packages. |
stacks/lab/prometheus/tests/soc.test.yaml |
Tests garuda agent alerts. |
stacks/lab/prometheus/rules/soc.rules.yaml |
Monitors garuda through Alloy. |
scripts/stage-agent-msis.sh |
Stages Debian agent packages. |
README.md |
Updates the ADR count. |
docs/security.md |
Updates the package threat model. |
docs/runbooks/provision-lab-guests.md |
Corrects the teardown section reference. |
docs/runbooks/build-the-analyst-workstation.md |
Adds agent installation instructions. |
docs/roadmap.md |
Records phase 2’s ADR. |
docs/network.md |
Documents SOC traffic from garuda. |
docs/changelog.md |
Records the authored change. |
docs/architecture.md |
Records garuda’s enrolment. |
docs/adr/0092-enrol-garuda-in-odins-soc-with-debian-packages-staged-on-odin.md |
Defines the enrolment decision. |
docs/adr/0091-put-a-kali-purple-analyst-workstation-on-saruman.md |
Links the deferred phase to ADR-0092. |
docs/adr/0030-give-the-security-tooling-its-own-guest-and-its-own-stack.md |
Updates historical port consumers. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- stage-agent-msis.sh: a Velociraptor .deb kept from an earlier run gets the same checks as a fresh build (non-empty, a Debian package, and version equal to the server's) before it is served and its hash printed. - ADR-0030: its port table is back as accepted; a dated note points to ADR-0092, per ADR-0001. - The first-start claim that Velociraptor built "MSI, deb and rpm" is corrected in compose.yaml and build-the-soc-guest.md to what odin's datastore holds: an MSI and an RPM, no Debian package. - security.md's 8448 row: the ADR link is relative to docs/, the row covers both Velociraptor packages and the seven addresses, and rotation includes rebuilding the staged .deb. - build-the-soc-guest.md section 11, scripts/README.md and group_vars say 8448 answers garuda and that staging includes the two .debs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 10, 2026
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 #921 (phase 2).
garudabecomes the first Linux guest enrolled inodin's Wazuh and Velociraptor. ADR-0092 records the decision that ADR-0091 deferred.What changes
stacks/soc/Caddyfile:8448now also answers10.0.30.62/32.stacks/soc/linux-agents.yaml: pins the Wazuh agent.debat 4.14.8, the manager's version, by sha2566ed202e2…8967.wazuh-agent 4.14.8-1.dists/stable/InRelease, which has a good signature from the Wazuh Signing Key (0DCF CA55 47B1 9D2A 6099 5060 96B3 EE5F 2911 1145).scripts/stage-agent-msis.sh: besides the six's MSIs, it now stages:.deb, refused if it doesn't match the pin;.debbuilt by the server,config clientthendebian client. A trial build insoc-velociraptorproducedvelociraptor_client_0.77.3_amd64.deb. Builds aren't reproducible, so one already staged for the running server version is kept, and its sha256 is printed for the install to check against.WazuhAgentsNotConnected:up{job=~"windows|garuda-alloy"}is now the set of guests that must have an Active agent. garuda's Alloy stands in for its missingwindows_exporter, and the match is still by name.eden's Alloy alone stays quiet.Garuda's runbook §12, phase 2:
authd.passfrom stdin, restart, and remove the file once enrolled;.deb.The teardown section becomes §13.
Docs: ADR-0030's port table,
security.md's 8448 row, the SOC README, the roadmap,architecture.md,network.md, the changelog and a note on ADR-0091.Checks
check_docs.py, lint,check_sops_rules.py, andbash -non the staging script all pass. The pin parser reads both pin files correctly.check rulesandtest rulesonsocpass.Deploy, after merge
odin:git pull, thenmake up STACK=socto reload Caddy, thensudo scripts/stage-agent-msis.sh.alexander:make up STACK=lab, so the lab Prometheus loads the changed rule.garuda: runbook §12, then check that the agent is Active onodinand the client appears in Velociraptor.🤖 Generated with Claude Code