KnowBe4
DLH.io documentation for KnowBe4
KnowBe4 is a security awareness training and simulated phishing platform. Replicating its Reporting API into your data cloud lets security and compliance teams track phishing test results, training enrollment and user, group and account risk scores over time.
Setup Instructions
Follow the setup steps guide for configuring your KnowBe4 connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Recent phishing tests are re-read |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Not captured automatically (use a historical re-sync) | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
This connection is read only and never writes data back to KnowBe4. Be sure to also check the change log and notes page from time to time for any changes.
- KnowBe4 offers no way to ask only for changed records, so accounts, users, groups, campaigns, training data and the risk score history are read in full on every run.
- Phishing security tests and their recipients keep collecting opens, clicks and reports after a test starts, so each later run re-reads the tests that started in the 30 days before the previous run. Older tests are refreshed by a historical re-sync.
- Without a Historical Start Date, the first synchronization reads the phishing security tests that started in the last three years, with their recipients.
- Anything deleted in KnowBe4 is picked up by a historical re-sync.
Request Limits
KnowBe4 allows 50 Reporting API requests a minute and 2,000 requests a day plus one for each licensed user. DLH.io paces its requests to one every 1.2 seconds and reads 500 records per request. The group members, recipients and the user and group risk score history tables need one request for each group, security test, user or group, so on an account with many users, uncheck USER_RISK_SCORE_HISTORY if you do not need it.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following 14 entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
ACCOUNTACCOUNT_RISK_SCORE_HISTORYUSERSUSER_RISK_SCORE_HISTORYGROUPSGROUP_MEMBERSGROUP_RISK_SCORE_HISTORYPHISHING_CAMPAIGNSPHISHING_SECURITY_TESTSPHISHING_RECIPIENTSTRAINING_STORE_PURCHASESTRAINING_POLICIESTRAINING_CAMPAIGNSTRAINING_ENROLLMENTS
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.