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
- Admin and Manager open the page, save the API key and region, test the connection, disconnect the connector, and start a manual sync from Security awareness.
-
Contributor and
Viewer cannot open
/connectors/knowbe4; Aegis sends them away with an access-denied notice. They still see the imported records in Security awareness as their role allows.
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.
-
Header — A breadcrumb back to
Connectors, the titleKnowBe4 Security Awarenessand a one-line description. -
Configuration — Two information boxes come first: a blue
KnowBe4 Integrationbox listing what is synced, and a yellowAPI Key Requiredbox saying where to generate the key. Below them are theAPI Keyfield (hidden as you type; shows********once a key is stored), theAPI Base URLfield (pre-filled with the US address, with the EU and UK addresses in the hint) andSave Configuration. -
Connection Status — A status badge such as
Not Tested,ConnectedorConnection Failed. If the connector has failed before, aLast recorded errorbox shows the reason and when it was recorded. Before anything is saved, the panel readsConfigure settings below to connect.; after a save,Test Connectionappears. -
Disconnect — A
Disconnect connectorsection with aDisconnectbutton. -
Setup Instructions and Data Synced — Six numbered setup steps, and a list of
what the nightly sync brings in:
Training campaign enrollments,Per-user completion status and scores,Phishing simulation resultsandAutomatic evidence linking to compliance controls.
Connect KnowBe4
-
In the KnowBe4 admin console, go to
Account Settings → APIand generate a Reporting API key. Copy it. -
In Aegis, open
/connectors/knowbe4and paste the key intoAPI Key. The field masks what you type. -
Check
API Base URL. It starts onhttps://us.api.knowbe4.com; change it tohttps://eu.api.knowbe4.comorhttps://uk.api.knowbe4.comif your KnowBe4 account lives in that region. -
Select
Save Configuration. Aegis checks the address, stores the key encrypted, andTest Connectionappears in the Connection Status panel. A new or changed configuration is saved as not connected. -
Select
Test Connection. Aegis asks KnowBe4 for your training campaigns. On success the badge turnsConnectedand a line gives the number of training campaigns found; on failure the badge readsConnection Failedwith the reason.
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
-
Open Security awareness and select
Sync Now(Admin and Manager only). The button shows a spinner while the sync runs. - 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.
- After a completed run, the training table and the statistics cards refresh with the new records.
Disconnect KnowBe4
-
On
/connectors/knowbe4, selectDisconnect. A confirmation dialog opens. - 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
- Evidence — Each completed training record becomes one evidence item named after the course and the trainee, tagged with the course and score. It is linked to every published control whose title contains "awareness" or "training", in the frameworks your organisation can see. Retired controls and frameworks your plan does not include get no new links.
- Deleted evidence stays deleted — If someone deletes a training evidence item, later syncs do not bring it back.
- Phishing results — Each KnowBe4 phishing campaign appears as a phishing-simulation campaign, with one record per recipient. A recipient who clicked the link, replied, opened the attachment or entered data is recorded as failed; anyone else is recorded as completed. Phishing records carry no score, because KnowBe4 does not give one. Up to 200 phishing campaigns are processed per run.
- Re-syncing updates, it does not duplicate — Records are matched on their KnowBe4 identifiers, so each nightly run refreshes what is already there.
Tips and limits
- A score outside 0–100 is not stored, so it can never raise a low-score finding.
- A score with a fraction is rounded to the nearest whole number.
- Trainees are matched to Aegis users by email, ignoring letter case. Give external trainees an Aegis account if you need their training as evidence.
- If no published control has "awareness" or "training" in its title, training is still imported but nothing is linked as evidence.
- The API base address must be a public KnowBe4 address; Aegis refuses one that points at a private or internal network.
Where this connects
Training results are followed up in Security awareness. Linked training appears in Evidence. For the full list of connectors, see Connectors.