Description
Problem
ansible/roles/soc_agents has no standing download location for its two installers. soc_agents_wazuh_msi_url and soc_agents_velociraptor_msi_url have no default, on purpose: *.msi is gitignored and no URL was ever decided. The role's defaults say so, and it fails with a clear message when a guest needs an installer and the URL is unset.
On the hand-built domain this never came up, because the role adopted agents that the deploy GPOs had installed. On a rebuild it does. #448's rebuild stopped at --tags soc on all six:
Wazuh is not installed and soc_agents_wazuh_msi_url is unset. …
Velociraptor is not installed and soc_agents_velociraptor_msi_url is unset. …
The next licence rebuild (#440, around 2027-03) will stop at the same place.
What #448 did, once
- Velociraptor: the 0.77.2 MSI repacked by
Server.Utils.CreateMSI, with the client config inside. It sits in odin's datastore at/srv/soc-data/velociraptor/clients/server/collections/F.DASIDL6DB26AC/uploads/scope/Org_%3Croot%3E_velociraptor-v0.77.2-windows-amd64.msi. Its sha256 matches the role's pin,e945e798…. - Wazuh: the official
https://packages.wazuh.com/4.x/windows/wazuh-agent-4.14.7-1.msi. Its sha256 matches the role's pin,e967f36b…. - Serving: both were served from a temporary
python3 -m http.server 8448 --bind 10.0.30.60on odin, and passed with-efor the run only. The server was stopped and removed afterwards.
To decide
- Where the two MSIs live, served to VLAN 30 only. For example, a small static-file service on odin beside the SOC stack, or a path on an existing web server. The Velociraptor MSI carries the client config (server URL, CA, enrolment nonce), so it should not be public. The Wazuh MSI is a public file, so its URL could stay the vendor's. The open question is whether the guests may fetch from the internet at all.
- How a version bump moves. Today one edit moves the version, product code and sha256 together in
roles/soc_agents/defaults/main.yml. The MSI on the server has to move with them, and the Velociraptor one is rebuilt on odin with each server upgrade. The runbook should say who puts it in place, and where. - Setting the URLs. Once the location is decided, set both in
group_vars/all.yaml. The rebuild runbook (build-the-lab-domain.md, "Rebuild from the pipeline") then needs no-eand no temporary server.
Also pending: the Wazuh pin is still 4.14.7 while the manager is 4.14.8, per the role's own note. That bump would move the MSI too.
Done when
ansible-playbook lab-domain.yml --tags soc installs both agents on a fresh guest with no extra variables, and the runbook names where the MSIs come from.
🤖 Generated with Claude Code
Activity
fix(soc): name the MSI server caddy, fix its port, stage into the sta…
feat(soc): serve the lab pipeline's agent MSIs from odin, to the six …
fix(soc): keep NET_BIND_SERVICE on the MSI server, for the exec (#1068)…
Gerrrt commentedon Oct 8, 2026
2026-10-08: deployed on odin, and the role's fetch path proved. #1071 and #1072 are on
main(33c278d).Staged:
sudo scripts/stage-agent-msis.shon odin gave PASS for both files against the role's pins. The Velociraptor MSI was found by hash in the datastore. Both files are in/srv/soc-data/agent-msi.Serving:
make up STACK=socbrought upsoc-agent-msi, healthy on0.0.0.0:8448.exec caddy failed: Operation not permitted): the image's binary carriescap_net_bind_serviceas a file capability.NET_BIND_SERVICEto fix that.Who can fetch. The Caddyfile only allows the six domain addresses, so this also proves Docker keeps the client's source address:
.52/and a missing file.70.110The role's own fetch. From phoenix, with no
-e,ansible.windows.win_get_urlran against titan with the role's checksums and thegroup_varsURLs (http://10.0.30.60:8448/wazuh-agent-4.14.7.msi,…/velociraptor-client-0.77.2.msi). Both downloaded and both checksums matched. The test files were then deleted.Not yet seen:
--tags socinstalling both agents on a guest that has neither. All six already have them. That is the last line of "Done when", and the next rebuild or a fresh guest will show it.🤖 Generated with Claude Code
Gerrrt commentedon Oct 8, 2026
Closed at Garrett's call, on the evidence above: odin serves both MSIs to the six only, and the role's fetch with checksums works from phoenix with no extra variables. A fresh-guest
--tags socinstall hasn't been seen yet; the next rebuild exercises it.🤖 Generated with Claude Code
ci: boot the SOC stack's MSI server under its hardening (#1068) (#1074)
fix(soc): the Wazuh dashboard and Velociraptor GUI answer Hicks only,…