Connector

Cisco Duo

API credential, entered client by client.

Second authentication factor bolted onto existing access (VPN, RDP, Windows logon, web applications). Vigicap reads how many Duo users exist, how many have a usable factor and how many are on bypass, to assess the ReCyF objective on multi-factor authentication. Duo protects only the access paths attached to it.

What to create in the tool

The access is created in Cisco Duo, 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 panneau d'administration Duo : Applications > Protect an Application > Admin API. Relevez l'Integration key, la Secret key et le nom d'hôte API (de la forme api-xxxxxxxx.duosecurity.com), qui est l'URL à saisir ici. L'horloge de votre serveur doit être à l'heure : Duo signe chaque requête avec sa date et refuse celles qui s'en écartent trop.

Minimum role

Dans Applications, créez une application « Admin API » et donnez-lui la permission « Grant read resource » UNIQUEMENT. Ce connecteur n'appelle que GET /admin/v1/users. N'accordez ni « Grant write resource », ni « Grant read log », ni « Grant settings » : aucune n'est utilisée, et la première permettrait de modifier vos utilisateurs.

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.

Integration key
Affichée sur la fiche de l'application Admin API.
DIXXXXXXXXXXXXXXXXXX
Secret keysecret
Affichée à côté de l'Integration key. À traiter comme un mot de passe.

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

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.