About

The KnowBe4 integration brings security awareness training completion into ControlMap automatically. ControlMap connects to one training campaign in your client's KnowBe4 account and collects whether each enrolled user has completed the training. This gives you evidence for auditors that the people with access to your client's systems have been trained.

When it scans, the integration does these things:

• Creates a user account for each user enrolled in the campaign, with the provider KnowBe4.
• Counts a user's training as complete when their KnowBe4 enrollment has the status "Passed".
• Matches KnowBe4 users to people already in ControlMap by email address and turns on the Security Training flag for active people whose enrollment is Passed.
• Keeps a dated history entry for each person with the campaign name and enrollment status.
• Runs one compliance check: Completion status of Security Awareness Training (SAT) in KnowBe4.
• Leaves out users whose KnowBe4 status is inactive, disabled or archived, and lists them as excluded with the reason "Inactive account".

Before you start

Have these ready:

• Setting up integrations from the client portal is part of the Pro plan. For details, see the Free, Essentials and Pro plans article.
• Your client's KnowBe4 account.
• A KnowBe4 API bearer token generated for ControlMap from that account. The token is entered as a hidden value during setup.
• The region of your client's KnowBe4 instance.
• The name of the training campaign you want ControlMap to follow.
• Email addresses in KnowBe4 that match the email addresses of the people in ControlMap, if you want training status linked to those people.

Connect KnowBe4

1. Go to Monitor › Integrations and select Add Integration.
2. Search for KnowBe4. Its card shows the category Security Awareness Training and the description "Sync users into ControlMap from KnowBe4".
3. Select the KnowBe4 card. The setup page opens on the Connection step.

4. In Knowbe4 API Bearer Token, paste the token generated for ControlMap from your client's KnowBe4 account.
5. In Region of Knowbe4 instance, choose the region of your client's KnowBe4 instance. US (United States) is selected by default.
6. Select Next: Checks. ControlMap checks the token against KnowBe4 and saves the connection.
7. When the Training Campaigns list appears, choose the campaign whose users you want ControlMap to sync, then select Next: Checks again. ControlMap collects training completion for the campaign you choose.
8. Complete the remaining steps as described in the Connect an integration article.

The setup page also shows a help panel on the right that describes what the connector does.

What you'll see after connecting

ControlMap collects KnowBe4 data on the schedule you chose, and shows it in these places:

• User Accounts in Monitor: one account for each user enrolled in the campaign, with the provider KnowBe4.
• Compliance Checks in Monitor: the check Completion status of Security Awareness Training (SAT) in KnowBe4. It shows No Data until the first scan finishes.
• People: the Security Training flag for matched people whose enrollment is Passed.

Disconnect or change settings

To change the schedule, watchers or other settings, go to Monitor › Integrations and select the KnowBe4 card. See the Connect an integration article for the tabs on the connection's page. To change the token or region, use Update Connection on the Connection tab.

The KnowBe4 connection's page also has an Exclusions tab with one setting, Exclude inactive and disabled accounts. Select Save rules to save a change.

To remove the connection, select the bin icon on the KnowBe4 card and choose Yes to confirm. Deleting an integration also deletes all of its assets and their compliance status.