Knowbe4
Visualize Knowbe4 users, groups, training campaigns, and modules, and monitor changes through queries and alerts.
- Installation guide
- Knowbe4 data model
Installation
For you to use this integration, JupiterOne requires the regional site for where your account is located and a Knowbe4 API key configured for use in JupiterOne.
Configuration in Knowbe4
You can generate a new key in your KnowBe4 account settings under the API section. Be sure to request a key for the Reporting API, not for the User Event API. Select the Enabled Reporting API Access option, and click Save Changes. Refresh the page to ensure that the changes were saved. Then, copy the API Token to use in JupiterOne.
KnowBe4 APIs are available to Platinum and Diamond customers only. See the KnowBe4 API Reference Guide for more information.
Configuration in JupiterOne
To install the Knowbe4 integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Knowbe4. Click New Instance to begin configuring your integration, providing the following:
Account Name used to identify the Knowbe4 account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
option is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Site of your KnowBe4 account, either
US
orEU
.API Key configured in your KnowBe4 account.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
KnowBe4 Account | knowbe4_account | Account |
KnowBe4 Group | knowbe4_user_group | UserGroup |
KnowBe4 Phishing Campaign | knowbe4_phishing_campaign | Training |
KnowBe4 Phishing Security Test | knowbe4_phishing_security_test | Assessment |
KnowBe4 Phishing Security Test Results | knowbe4_phishing_security_test_result | Record |
KnowBe4 Training Campaign | training_campaign | Training |
KnowBe4 Training Module | training_module | Training, Module |
KnowBe4 User | knowbe4_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
knowbe4_account | HAS | knowbe4_phishing_campaign |
knowbe4_account | HAS | training_campaign |
knowbe4_account | HAS | knowbe4_user |
knowbe4_account | HAS | knowbe4_user_group |
knowbe4_phishing_campaign | CONTAINS | knowbe4_phishing_security_test |
knowbe4_user_group | HAS | knowbe4_user |
knowbe4_user | HAS | knowbe4_phishing_security_test_result |
knowbe4_phishing_security_test | CONTAINS | knowbe4_phishing_security_test_result |
training_campaign | ASSIGNED | knowbe4_user_group |
training_campaign | HAS | training_module |
training_module | ASSIGNED | knowbe4_user |
knowbe4_user | COMPLETED | training_module |