Connector

Heimdal

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

Endpoint security suite (Danish vendor): DNS filtering, antivirus, third-party and OS patching, privilege elevation, application control. A single reseller key reads every one of your customer accounts. Levels rest on the MODULES ACTUALLY RUNNING on each endpoint rather than on the licences held — a module bought and never deployed is reported as exactly that. Where a module is neither running nor licensed, no reading is published: absence from Heimdal is not absence from the estate.

What to create in the tool

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

Dans le Dashboard Heimdal : onglet Guide > Your Heimdal API Key > générer. Pensez ensuite à ajouter l'adresse IP de sortie de Vigicap aux adresses fiables du compte (section Accounts) : sans cela, l'API répond « non autorisé » même avec une clé valide. L'identifiant à saisir ici est l'ID client de votre compte revendeur (visible dans l'URL du Dashboard).

Minimum role

Clé d'API personnelle générée dans le Dashboard Heimdal (onglet Guide > Your Heimdal API Key). Toutes les lectures de ce connecteur sont des GET. La clé HÉRITE des droits du compte Dashboard qui l'a générée et il n'existe aucune portée plus fine : créez-la depuis un compte dont le rôle se limite à la consultation des clients concernés, et non depuis le compte super-admin. Heimdal n'accepte les appels d'API QUE depuis les adresses IP déclarées comme fiables sur ce compte (section Accounts) — l'adresse de sortie de Vigicap doit y figurer, sinon la clé est refusée sans que la réponse le dise.

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.

Clé d'API personnellesecret
Dashboard Heimdal > Guide > Your Heimdal API Key. Elle n'est affichée qu'à la génération.
ID client revendeur
L'ID numérique de votre compte revendeur. Heimdal l'exige sur chaque appel et ne propose aucun moyen de le découvrir : il figure dans l'URL du Dashboard.
229584

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

#5 Maîtrise des systèmes d'informationControl of the information systems
#9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
#11 Maîtrise de l'administration des systèmes d'informationControl of the administration 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 was written from the vendor's documented API and has not yet been run against a real instance.

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