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.

What to create in the tool

The access is created in Wazuh, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.

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.

What to enter in Vigicap

The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.

The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.

API usernamesecret
Dedicated Wazuh API account, read-only if possible.
wazuh-vigicap
Passwordsecret
Password for this API account.

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.

What it does, and what it does not do

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

The reads are read-only: Vigicap writes nothing into the tool while reading it.

What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.

Verification

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

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.