Connector

Intruder

API credential, entered client by client.

Hosted external vulnerability scanning. Vigicap reads how many targets exist, how many are unscanned (never scanned, or past the licence quota), how many are scanned with authentication, and the count per severity. COVERAGE decides first: a target that is present and unscanned makes any conclusion about exposure impossible, however many vulnerabilities were found elsewhere. A target whose scan a web application firewall blocked is flagged — its clean result proves nothing.

What to create in the tool

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

Portail Intruder > Settings > Account > API Access Tokens > saisissez un nom, laissez l'expiration vide pour un jeton permanent, puis confirmez avec votre mot de passe. Le jeton n'est affiché qu'une fois. L'API n'est pas incluse dans l'offre gratuite.

Minimum role

Jeton d'accès personnel créé dans le portail Intruder (Settings > Account > API Access Tokens). Toutes les lectures de ce connecteur sont des GET ; aucune écriture n'est effectuée. Attention : Intruder ne propose pas de compte de service — « les jetons d'autorisation sont des jetons d'accès personnels, liés à votre compte utilisateur Intruder ». Le connecteur cessera donc de fonctionner si la personne qui a créé le jeton quitte l'organisation. Laissez le champ d'expiration vide pour un jeton permanent, ou prévoyez son renouvellement.

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.

Jeton d'accès APIsecret
Créé dans Settings > Account > API Access Tokens. Lié à un compte utilisateur, pas à un compte de service.

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.

#5 Maîtrise des systèmes d'informationControl 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

The API is public and documented, but it can only be reached with a paid subscription the vendor issues no trial for: there is no instance we can obtain to run it against. This is not “not yet done” — it would take a customer lending us their tenant.

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