KnowBe4 Integration

Learn how to collect evidence from KnowBe4 using Strike Graph's flexible Bridge integration

Written By Micah

What is the KnowBe4 Integration?

The KnowBe4 integration allows you to use Strike Graph's Bridge-style integration to collect evidence directly from the KnowBe4 Reporting API for your compliance needs. This integration uses an API key generated in your KnowBe4 console, giving you access to training campaign results, user enrollment data, phishing simulation outcomes, and more.

Security awareness training is a common requirement across compliance frameworks, and the KnowBe4 integration makes it easy to collect and maintain evidence that your organization's training program is active and effective.

With this integration, you can gather evidence from KnowBe4, including:

  • User enrollment and training status
  • Training campaign details and completion rates
  • Phishing simulation campaigns and results
  • Group membership and organizational structure
  • Account-level configuration

Evidence collection is read-only: Strike Graph uses the KnowBe4 Reporting API, which provides data access only and cannot modify your KnowBe4 account or training configurations.

Two Ways to Collect Evidence from KnowBe4

The KnowBe4 integration supports two evidence collection methods:

KnowBe4 API requests let you call specific KnowBe4 Reporting API endpoints and collect the response as evidence. This approach gives you full control over exactly which endpoint to call and what parameters to include.

Script Runner provides curated, pre-built scripts that handle common evidence collection scenarios. Scripts can combine multiple API calls, filter and format the output, and produce evidence that is ready for auditor review. Script Runner is equally powerful to direct API requests and is often the faster path to well-formatted evidence.

If your organization has access to Script Runner, both options appear as tabs when you attach evidence using this integration.

Setting Up the KnowBe4 Integration

Prerequisites

  • A KnowBe4 account with access to generate Reporting API keys
  • Appropriate permissions within Strike Graph to manage integrations

Step 1: Generate a Reporting API key in KnowBe4

  1. Sign in to your KnowBe4 console.
  2. Navigate to Account Settings.
  3. Locate the API section and generate a new Reporting API key.
  4. Copy the API key. You will need it in the next step.

For more information on generating API keys, see the KnowBe4 API documentation.

Step 2: Connect KnowBe4 in Strike Graph

  1. Navigate to Integrations in the main Strike Graph menu.
  2. Find the KnowBe4 integration card and click Add Integration.
  3. Select the Region that serves your KnowBe4 account. KnowBe4 hosts tenants in different regions, so this must match where your account is provisioned:
    • United States (us.api.knowbe4.com)
    • Europe (eu.api.knowbe4.com)
    • Canada (ca.api.knowbe4.com)
    • United Kingdom (uk.api.knowbe4.com)
    • Germany (de.api.knowbe4.com)
  4. Paste your API Key into the provided field.
  5. Click Save.

Once connected, your KnowBe4 integration will appear in the integration list with an "Active" status. The integration name will include your selected region (for example, "KnowBe4 (US)").

Collecting Evidence Using KnowBe4 API Requests

Step 1: Select an evidence object

  1. Navigate to the evidence object where you want to add KnowBe4 data.
  2. Click the Attach button to open the attachment options (or configure Automated Collection).
  3. Select your KnowBe4 integration from the list of available sources.

Step 2: Configure your API request

The KnowBe4 evidence collection form has two main components:

HTTP Method

KnowBe4 evidence collection supports GET requests only, since the Reporting API is read-only.

API Route

Enter the KnowBe4 Reporting API route you want to access. Review the KnowBe4 Reporting API documentation for the full list of available endpoints. The base URL is handled by the integration (based on your selected region), so you only need to provide the route.

Example API routes:

  • v1/users — Get all users in your KnowBe4 account
  • v1/groups — Get all groups
  • v1/training/campaigns — Get training campaigns
  • v1/training/enrollments — Get training enrollment records
  • v1/phishing/campaigns — Get phishing simulation campaigns
  • v1/phishing/security_tests — Get phishing test results
  • v1/account — Get account-level information

Step 3: Submit your request

  1. Click Submit to execute the API request.
  2. Strike Graph will process your request and collect the data.
  3. Once complete, the evidence will be attached to your evidence object.

Collecting Evidence Using Script Runner

If your organization has Script Runner enabled, a Scripts tab will appear alongside the KnowBe4 tab when attaching evidence.

Script Runner provides pre-built scripts tailored to common compliance evidence needs. To use Script Runner:

  1. Navigate to the evidence object and open the attachment options.
  2. Select your KnowBe4 integration.
  3. Switch to the Scripts tab.
  4. Search for a script that matches your evidence needs, or describe what you're looking for.
  5. Select a script to preview its details and expected output.

The integration's region is already stored from setup, so Script Runner scripts will automatically connect to the correct regional host without requiring you to select it again at run time.

For more details on using Script Runner, see the Script Runner overview.

Troubleshooting

Invalid API key

If you receive an authentication error, your API key may have been revoked or regenerated in the KnowBe4 console.

  1. Click the Reconnect button next to your KnowBe4 integration in the Integrations Manager.
  2. Enter your current API key and region.
  3. Try your evidence collection again.

Wrong region

If you receive errors when making API requests, verify that the region you selected matches where your KnowBe4 account is hosted. Each region has a separate API host, and using the wrong one will result in authentication failures. If you need to correct the region, reconnect the integration with the correct value.

Missing or incomplete data

If your evidence collection succeeds but doesn't include the data you expected:

  • Check if you need a different API endpoint. The KnowBe4 Reporting API has separate endpoints for users, training campaigns, enrollments, phishing campaigns, and more.
  • Some endpoints support query parameters for filtering. Refer to the KnowBe4 API documentation for available filters.
  • Verify that your API key has the necessary permissions to access the requested data.

Need More Help?

If you encounter any issues with your KnowBe4 Bridge integration or have questions about specific API endpoints, please contact our support team through the in-app messenger. We're here to help you make the most of your compliance automation.