Skip to main content
Back to the connector catalogue

Connector

Wazuh

API credential, entered client by client.

Wazuh is an open-source SIEM/XDR platform. Vigicap authenticates against the Wazuh server API (port 55000 by default) and reads the breakdown of agents (active, disconnected, never connected): the share of active agents, which actually send their logs, serves as evidence both for centralised logging and for incident detection.

01

What to create in the tool

The access is created in Wazuh, not in Vigicap.

Where to generate it

Create a dedicated API user in Wazuh (the read-only 'agent:read' role is enough) from Wazuh Dashboard > Administration > Security, or via wazuh-apid. Important: the instance must present a valid, trusted TLS certificate — Wazuh's default self-signed certificate will be rejected by Vigicap (there is no option to disable TLS verification, for security reasons).

Minimum role

Utilisateur API dédié dont la seule policy RBAC autorise l'action « agent:read » sur les ressources « agent:id:* » et « agent:group:* » — aucune autre action n'est nécessaire.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

  • API usernamesecret

    Dedicated Wazuh API account, read-only if possible.

    wazuh-vigicap

  • Passwordsecret

    Password for this API account.

03

Per-client routing

The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.

04

What it does, and what it does not do

ISO 27001 controls covered

This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.

  • 5.7 Threat intelligence
  • 8.7 Protection against malware
  • 8.15 Logging
  • 8.16 Monitoring activities
  • 8.17 Clock synchronization

ReCyF objectives it pre-fills

A reading feeds 2 objectives of the ANSSI ReCyF framework. It PROPOSES them: a level only counts once a consultant has confirmed it.

  • #12 Identification et réaction aux incidents de sécuritéIdentification of and response to security incidents
  • #20 Supervision de la sécurité des systèmes d'informationSecurity monitoring of the information systems

Read-only

Vigicap writes nothing to the tool while reading.

How Vigicap handles your credentials.

Verification

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

What this connector reads, exactly

  • The Wazuh server's agent distribution: active, disconnected, never connected. The three categories are read separately.
  • The share of active agents — those actually shipping their logs — serves as evidence for both centralised logging and incident detection.
  • Two ReCyF objectives from a single measurement: it is the only connector in this list in that position.

What it does not read

Log content, detection rules and alerts. Vigicap authenticates against the Wazuh server's API (port 55000 by default) and reads an agent count — none of the stream itself passes through.

What these signals do not prove

  • Active agents prove logs are arriving. They prove neither that the right sources are covered, nor that the detection rules are fit, nor that anyone reads the result.
  • "Never connected" is the most instructive of the three categories: it counts declared agents that have never shipped anything, which a bare activity rate would hide.
Why two objectives from a single reading?
Because an agent shipping its logs is both evidence of logging and a precondition for detection. Honesty means saying it is one measurement seen twice, not two measurements.
Does port 55000 have to be opened to Vigicap?
The server's API must be reachable. That port is the default; an instance that changed it works just as well.