Connector

Hornetsecurity

A single agency-level credential, for the whole portfolio.

E-mail security. A single key reads all of your clients: protected domains, anti-spam and anti-malware filtering, ATP and DKIM signing, plus the state of strong authentication on the Control Panel.

Beta

What to create in the tool

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

Control Panel > paramètres de l'utilisateur > jetons d'accès API : créez un jeton pour un utilisateur administrateur. L'App-ID n'est nécessaire que pour les intégrations basées sur un jeton de connexion — laissez-le vide si vous utilisez un jeton d'accès API.

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.

Jeton d'accès APIsecret
Créé depuis les paramètres utilisateur du Control Panel. Une date d'expiration est facultative.
App-IDsecretoptional
Uniquement si votre intégration utilise un jeton de connexion. Inutile avec un jeton d'accès API.

Per-client routing

The credential itself is not repeated: one, entered once at agency level, covers the whole portfolio — the difference you feel with forty clients rather than four.

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.