KnowBe4

Import training results and phishing-simulation results from KnowBe4, and use completed training as evidence for your controls.

KnowBe4 is a security awareness training platform. The connector reads your KnowBe4 account every night and brings training enrolments, per-person completion status and scores, and phishing-simulation results into Security awareness. Completed training then becomes evidence (the proof a control works) on your awareness and training controls. Aegis only reads from KnowBe4; it never changes anything there.

At a glance

Direction Into Aegis.
What it brings in Training enrolments, per-person completion status and scores, and phishing-simulation results.
Where it lands Training records in Security awareness; phishing results appear there as phishing-simulation campaigns. Completed training is linked to the matching controls as evidence.
Credentials and permissions A KnowBe4 Reporting API key (Account Settings → API) and the base address of your region (US, EU or UK).
Owner of imported records The employee who completed the training, matched by email. A trainee without an Aegis account is counted as unresolved and gets no evidence.
When it runs Every night at 02:00 UTC by default, for each KnowBe4 connector whose status is Connected. A manual Sync Now is also available in Security awareness.
Set it up /connectors/knowbe4, by an Admin or Manager, on a plan that includes the connector module.

Who uses it

What's on this screen

No screenshot of this page was captured for this edition of the guide. The description below follows the page as it is built today.

Connect KnowBe4

  1. In the KnowBe4 admin console, go to Account Settings → API and generate a Reporting API key. Copy it.
  2. In Aegis, open /connectors/knowbe4 and paste the key into API Key. The field masks what you type.
  3. Check API Base URL. It starts on https://us.api.knowbe4.com; change it to https://eu.api.knowbe4.com or https://uk.api.knowbe4.com if your KnowBe4 account lives in that region.
  4. Select Save Configuration. Aegis checks the address, stores the key encrypted, and Test Connection appears in the Connection Status panel. A new or changed configuration is saved as not connected.
  5. Select Test Connection. Aegis asks KnowBe4 for your training campaigns. On success the badge turns Connected and a line gives the number of training campaigns found; on failure the badge reads Connection Failed with the reason.
Saving alone does not start syncing

The nightly sync only runs for a connector whose status is Connected, and only a successful Test Connection (or sync) sets that status. Test after every change to the key or the address.

Sync on demand

  1. Open Security awareness and select Sync Now (Admin and Manager only). The button shows a spinner while the sync runs.
  2. Wait for the message. A success message gives the number of records imported and the number linked to controls. A warning says the sync finished without importing anything; an error explains that no KnowBe4 connector is configured, that it is not connected, or that the sync run failed and you should check the connector. If the run takes longer, Aegis says it is still running and asks you to refresh in a moment.
  3. After a completed run, the training table and the statistics cards refresh with the new records.

Disconnect KnowBe4

  1. On /connectors/knowbe4, select Disconnect. A confirmation dialog opens.
  2. Confirm. Aegis deletes the stored configuration and API key, plus the sync schedules and mappings that use it, and syncing stops. Records already imported stay in Aegis. You can configure the connector again later.

How imported records are handled

Tips and limits

Where this connects

Training results are followed up in Security awareness. Linked training appears in Evidence. For the full list of connectors, see Connectors.