Skip to content

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

Open

Description

@Gerrrt

Finding

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:

  1. Download the 4.14.10 Wazuh agent MSI and the 0.77.3 Velociraptor MSI from upstream.
  2. Record each one's sha256sum.
  3. Read each one's ProductCode, for example with msiinfo export <msi> Property | grep ProductCode (msitools).
  4. Move soc_agents_*_version, _product_id and _msi_sha256 together, in one commit.
  5. 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.

Source: Phase 1 audit, finding #16.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    socstacks/soc on odin (VLAN 30)

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions