Vigicap
Connector
SoSafe
API credential, entered client by client.
Security-awareness training and phishing simulation (German vendor). The level rests on BEHAVIOUR before training completion: finishing a module says someone sat through it, clicking a simulated phish says what they do under the conditions of a real attack. Reporting is counted separately from clicking — a population that clicks little but reports nothing has learned to ignore, not to escalate. A campaign recorded but never sent does not count.
01
What to create in the tool
The access is created in SoSafe, 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 manager SoSafe : créez une clé d'API et notez À LA FOIS la clé et son identifiant (keyId, de la forme SSKI…). Les deux sont nécessaires : la clé part dans un en-tête, l'identifiant dans le corps de la requête de connexion. L'accès à l'API est une option premium du contrat.
Minimum role
Clé d'API SoSafe créée dans le manager, avec son identifiant de clé (keyId). Toutes les lectures de ce connecteur sont des GET sur les données d'e-learning et de simulation de phishing. L'API SoSafe est une option premium : si la clé est refusée avec un code 403 plutôt que 401, c'est l'autorisation d'accès à l'API qui manque et non la clé qui est fausse.
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.
- Clé d'APIsecret
La valeur secrète de la clé, envoyée dans l'en-tête x-api-key.
- Identifiant de la clé (keyId)
L'identifiant de la clé, distinct de la clé elle-même. SoSafe l'exige dans le corps de la requête de connexion : une clé sans son identifiant ne permet pas de s'authentifier.
SSKI2d4605a43f207403e45
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.
- #4 Intégration de la sécurité numérique dans la gestion des ressources humainesIntegration of digital security into human resources management
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.