You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SOC agents lag the servers: Wazuh agent 4.14.7 vs manager 4.14.10, Velociraptor client 0.77.2 vs server 0.77.3 #1439
ansible/roles/soc_agents pins the six domain guests' agents at Wazuh 4.14.7 and Velociraptor 0.77.2. stacks/soc/compose.yaml runs the manager at 4.14.10 and the server at 0.77.3. The role's comment said the manager was 4.14.8, so the gap went unnoticed. Wazuh supports older agents, but the SIEM is the instrument for the exercises, and a skewed agent can decode or report differently from what the manager's rules expect.
Evidence
ansible/roles/soc_agents/defaults/main.yml:20-30; stacks/soc/compose.yaml:174, 428 (on main).
Fix: needs the MSIs in hand, so not done in the audit session
The audit PR only corrects the comment (it now says to read the compose pin and points here). The bump itself, per version:
Download the 4.14.10 Wazuh agent MSI and the 0.77.3 Velociraptor MSI from upstream.
Record each one's sha256sum.
Read each one's ProductCode, for example with msiinfo export <msi> Property | grep ProductCode (msitools).
Move soc_agents_*_version, _product_id and _msi_sha256 together, in one commit.
Run --tags soc from phoenix against the six, then check the agents report the new versions in Wazuh and Velociraptor.
The audit session couldn't download upstream binaries, and step 5 runs on the lab.
Activity
docs: the roadmap and changelog after the tracker pass, and ragnarok'…