Connector

Dashlane

API credential, entered client by client.

Business password manager (French vendor). Vigicap reads the second-factor METHOD actually in place for each member — a stronger fact than a policy setting — and the team's password health. Dashlane publishes no activity log, no group membership and no second-factor enforcement setting: nothing is claimed about those.

What to create in the tool

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

Console d'administration > Integrations > Developer Access > Create API key. La clé a la forme DLP_<teamUuid>_<accessKey>_<secretKey> et n'est affichée qu'une fois. Elle n'expire pas. Disponible sur toutes les offres professionnelles.

Minimum role

Clé d'API créée dans la console d'administration Dashlane (Integrations > Developer Access > Create API key). Dashlane déclare son API publique en lecture seule et ne propose aucune portée plus fine : la même clé donne accès aux quatre points de lecture. À noter pour votre propre journal d'audit : Dashlane indique ne pas consigner qui crée les clés ni quand l'API est appelée — les lectures de ce connecteur ne sont donc pas auditables côté éditeur.

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'APIsecret
Générée dans Integrations > Developer Access. Elle contient l'identifiant de votre équipe : une clé par client.
DLP_…_…_…

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.

#10 Gestion des identités et des accès des utilisateurs aux systèmes d'informationManagement of user identities and of user access to 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.