Connector

Vade

API credential, entered client by client.

Mail filtering gateway published by Vade, a French company based in Hem (Hauts-de-France): clients' e-mail flows remain processed by a sovereign solution, a decisive argument for entities subject to the « cloud de confiance » doctrine. Vigicap reads the inbound filtering log, read-only, to evaluate the ReCyF objective « Sécurité de la messagerie » — volume of messages analysed, threats detected and the share actually blocked. Outbound filtering and SPF/DKIM/DMARC posture are not evaluated.

Beta

What to create in the tool

The access is created in Vade, 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

Use an "Admin" account on the Vade Cloud console (the username is the account's email address). The URL is that of your admin console, most commonly https://cloud.vadesecure.com.

Minimum role

The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.

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.

Vade Cloud usernamesecret
Email address of an "Admin" account on the Vade Cloud console.
admin@exemple.fr
Passwordsecret

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 one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.

#9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code

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 was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.

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