VigicapConnector
OVHcloud
API credential, entered client by client.
European host. Vigicap reads whether the client's OVHcloud account is protected by an active second factor (TOTP or SMS), to assess the ReCyF objective on multi-factor authentication. That account can delete the whole hosted estate. A factor declared but never confirmed is not counted as active, and the phone number behind an SMS factor is never read.
01
What to create in the tool
The access is created in OVHcloud, 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
Rendez-vous sur https://eu.api.ovh.com/createToken/ en étant connecté au compte du client : renseignez une description, choisissez « Illimité » pour la validité, et n'autorisez que les routes GET listées ci-dessus. Vous obtiendrez trois valeurs — Application Key, Application Secret et Consumer Key — à reporter ici. Laissez l'URL vide pour l'endpoint européen.
Minimum role
Créez une application sur https://eu.api.ovh.com/createToken/ en n'autorisant QUE les routes en lecture dont ce connecteur a besoin : GET /me, GET /me/accessRestriction/totp, GET /me/accessRestriction/totp/*, GET /me/accessRestriction/sms et GET /me/accessRestriction/sms/*. N'accordez aucune route en écriture et surtout pas GET /* : la clé de consommateur porte exactement les droits que vous cochez à sa création, et c'est là que se joue le moindre privilège.
Taken from the vendor's own role model, and checked before publication.
02
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.
- Application Key
Identifiant public de l'application créée sur createToken.
- Application Secretsecret
Secret de l'application. À traiter comme un mot de passe.
- Consumer Keysecret
Clé liant l'application au compte du client, portant les droits cochés à sa création.
03
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.
04
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.