Skip to main content

​
Overview

The KnowBe4 integration enables ThreatAware to collect data from your KnowBe4 deployment, providing visibility into security awareness training progress and phishing simulation results across your organisation.
Connection Method: API Setup Time: 10 minutes Access Required: KnowBe4 Administrator account

​
Data collected

The KnowBe4 integration provides:
  • Security awareness training status
  • Phishing simulation results
  • User training progress
  • Compliance metrics
  • Security event data

​
Use cases

Training Compliance

Track security awareness training completion and progress

Phishing Metrics

Monitor phishing simulation results and user susceptibility

Risk Assessment

Identify users at risk from phishing and social engineering

Compliance Reporting

Generate reports on training and awareness metrics

​
Setup instructions

1

Log in to KnowBe4 Console

Access the KnowBe4 Console with your administrator account.
2

Identify Your Console Region

Note the console region from your KnowBe4 URL:
  • Check the URL in your browser address bar
  • Look for the region identifier (e.g., eu.knowbe4.com or us.knowbe4.com)
  • Copy this region for use in ThreatAware
Example regions:
  • us.knowbe4.com (United States)
  • eu.knowbe4.com (Europe)
  • ap.knowbe4.com (Asia Pacific)
3

Navigate to Account Settings

In the KnowBe4 Console:
  • Click on your account menu
  • Select Account Settings
  • Go to Account Integrations and API
4

Enable Reporting API Access

In the API section:
  • Find the Reporting API option
  • Check the box labelled “Enable Reporting API Access”
  • Click Save Changes at the bottom of the screen
5

Copy Your API Token

After enabling API access:
  • Your API Token will be displayed
  • Copy the complete token value
  • Store it securely
The API token provides access to KnowBe4 data. Treat it as a sensitive credential.
6

Enter Credentials in ThreatAware

In ThreatAware:
  • Navigate to Settings > Integrations
  • Search for and select KnowBe4
  • Enter the required details:
    • API Token: The token you copied
    • Console Region: The region you identified (e.g., eu.knowbe4.com)
7

Connect and Verify

Click the Authorize button to complete the connection.Verify the connection status shows Active in ThreatAware.

​
Required credentials

Field Name: KnowBe4 API Token Type: Password (encrypted) Description: The Reporting API token generated in KnowBe4 account settings
Store this credential securely in your organisation’s password manager.
Field Name: KnowBe4 Region Type: String Description: The region identifier from your KnowBe4 console URLExamples:
  • eu.knowbe4.com (Europe)
  • us.knowbe4.com (United States)
  • ap.knowbe4.com (Asia Pacific)

​
Verification and testing

After setup, verify the integration is working correctly:
  1. Check Integration Status
    • Navigate to Settings > Integrations in ThreatAware
    • Confirm the KnowBe4 integration shows Active status
  2. Verify Data Collection
    • Wait up to 1 hour for the initial data sync
    • Check that KnowBe4 training and simulation data appears
    • Verify user training progress metrics are visible
  3. Test Queries
    • Create a test query to filter by training compliance status
    • Verify phishing simulation results are displayed
    • Test filtering by user risk levels

​
Troubleshooting

Symptoms: Connection fails with authentication errorSolutions:
  • Verify the API Token is entered completely and accurately
  • Ensure the Console Region matches your KnowBe4 URL exactly
  • Confirm API access is enabled in KnowBe4 account settings
  • Generate a new API token if needed
Symptoms: Cannot find API token or connection fails immediatelySolutions:
  • Log into KnowBe4 and navigate to Account Settings > Account Integrations and API
  • Check the box for “Enable Reporting API Access”
  • Click Save Changes
  • Refresh and copy the API token that appears
Symptoms: Integration fails to connect or times outSolutions:
  • Verify the KnowBe4 service is online and accessible
  • Confirm the console region URL is correct and reachable
  • Check firewall rules allow outbound HTTPS access to KnowBe4
  • Test connectivity by visiting the console URL in a browser
Symptoms: Integration shows active but no KnowBe4 data appearsSolutions:
  • Verify there is training and simulation data in KnowBe4
  • Check that users are enrolled in KnowBe4
  • Wait up to 1 hour for the initial data sync
  • Review ThreatAware integration logs for errors
  • Verify API access token has reporting permissions

​
Additional resources

KnowBe4 Documentation

Official KnowBe4 documentation and support

ThreatAware Support

Contact ThreatAware support for integration assistance

​
Best practices

Credential Management
  • Store the API token securely in your organisation’s password manager
  • Rotate API tokens annually or per your security policy
  • Monitor for authentication failures in ThreatAware logs
  • Document the console region for future reference
Security Considerations
  • Only use read-only API access
  • Limit API token usage to ThreatAware only
  • Review KnowBe4 audit logs periodically to monitor API usage
  • Follow your organisation’s least privilege principles