Skip to main content
Vigicap
Try it
Back to the connector catalogue

Connector

KnowBe4

API credential, entered client by client.

SaaS security-awareness training platform widely deployed by MSPs: training campaigns assigned to staff and phishing simulations. Vigicap reads the Reporting API read-only to evaluate the ReCyF objective « Sensibilisation » — number of campaigns, training completion rate and simulation click-through rate. The training content, the frequency of campaigns and the actual coverage of the workforce are not verified.

Beta

01

What to create in the tool

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

In the KnowBe4 console: click your email address (top right) > Account Settings > Account Integrations > API, then "Create New API Token" on the Reporting API tab. The URL is that of your region's API: https://eu.api.knowbe4.com (Europe) or https://us.api.knowbe4.com (United States) — these are the only two publicly documented regions.

Minimum role

Jeton généré dans la console « Reporting API » uniquement (et non « User Event API ») : l'API Reporting ne déclare que des opérations GET et ne peut donc rien écrire. KnowBe4 n'offre en revanche aucun périmètre plus fin — ce jeton lit l'ensemble des données de formation et de phishing du compte.

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.

  • Reporting API keysecret

    Account Settings > Account Integrations > API > Reporting API > Create New API Token. This key is read-only.

    Jeton de l'API Reporting KnowBe4

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

This connector was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.

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