Skip to main content

Connect KnowBe4 to Anzenna

Integrate Anzenna with KnowBe4 to monitor employee security awareness training completion, phishing simulation results, and overall security posture.

Prerequisites​

  • KnowBe4 account administrator access
  • Anzenna account
  • Ability to create API tokens in KnowBe4

Overview​

The integration provides:

  • Training completion tracking
  • Phishing simulation results
  • User risk scores
  • Campaign effectiveness metrics
  • Compliance reporting data

Step-by-Step Instructions​

Part 1: Access KnowBe4 Dashboard​

  1. Log into your KnowBe4 account

  2. Navigate to the Dashboard

Part 2: Access Account Settings​

  1. Click on your username in the top menu

  2. Select Account Settings from the dropdown

Part 3: Navigate to API Section​

  1. In Account Settings, go to Account Integrations

  2. Click on the API section

  3. Select Reporting API option

Part 4: Create API Token​

  1. Click Create New API Token

  2. Enter a descriptive name for the token:

    Anzenna

  3. Click Create or Confirm to generate the token

Part 5: Copy API Token​

  1. Copy the Reporting API Token immediately

Save Token

The token is only displayed once. Store it securely in a password manager.

  1. Click Accept or OK to acknowledge and close the dialog

Part 6: Connect in Anzenna​

  1. Log into Anzenna at

    app.anzenna.ai

  2. Navigate to Settings > Integrations

  3. Search for knowbe4 in the integrations list

  4. Toggle the KnowBe4 integration switch to enable it

  5. Paste the API token you copied from KnowBe4

  6. Enter your API URL:

    https://us.api.knowbe4.com

    7. Regional API URLs

    Use the URL that matches your KnowBe4 region.

  7. Click Save to establish the connection

  8. Verify integration shows as Connected

Verification​

  1. Check integration status shows Connected

  2. Wait 15-30 minutes for initial sync

  3. Navigate to Anzenna's Training dashboard

  4. Verify training completion data is appearing

  5. Check phishing campaign results are visible

What Data is Collected​

Training Data​

  • Course enrollments
  • Completion status
  • Training scores
  • Module progress
  • Time spent in training
  • Certificate dates
  • Overdue training

Phishing Simulation Results​

  • Campaign participation
  • Click rates
  • Reporting rates
  • Failure patterns
  • Repeat offenders
  • Improvement trends

User Metrics​

  • Individual risk scores
  • Security awareness levels
  • Phish-prone percentage
  • Baseline assessments
  • Progress tracking

Organizational Metrics​

  • Aggregate completion rates
  • Department-level statistics
  • Campaign effectiveness
  • Trend analysis
  • Compliance status

Using the Integration​

Monitor Training Compliance​

  • Track in Anzenna:

    • Employee training completion
    • Overdue training notifications
    • Department completion percentages
    • Compliance trending

Analyze Phishing Campaigns​

  • View:

    • Latest campaign results
    • Click-through rates by user
    • Improvement over time
    • High-risk users identification

Generate Reports​

  • Create reports for:

    • Executive summaries
    • Board presentations
    • Compliance audits
    • Department comparisons

Correlate with Security Events​

  • Cross-reference:

    • Training status with security incidents
    • Phishing failures with real attacks
    • Risk scores with access levels

Troubleshooting​

Connection Fails​

  • Verify API token copied correctly (no spaces)

  • Check token wasn't revoked
  • Ensure API URL matches your region
  • Confirm admin permissions in KnowBe4

No Data Appearing​

  • Wait 30 minutes for initial sync
  • Verify users exist in KnowBe4
  • Check training campaigns are active
  • Ensure Reporting API access is enabled
  • Review API rate limits

API URL Errors​

  • Verify correct regional URL
  • Check HTTPS protocol is used
  • Ensure no typos in URL
  • Confirm URL is accessible from network

Token Errors​

  • Regenerate token if compromised
  • Verify token type is "Reporting API"
  • Check token wasn't accidentally deleted
  • Ensure sufficient permissions

Security Considerations​

  • API token security - Treat as sensitive credential

  • Read-only access - Integration only reads data

  • Reporting API - Specific API type for analytics

  • Audit logging - All API access logged

  • Regional data - Data stays in selected region

Best Practices​

  1. Use correct region - Match your KnowBe4 region

  2. Secure token storage - Use password manager

  3. Regular monitoring - Check sync status weekly

  4. Correlate data - Cross-reference with security events

  5. Report regularly - Create executive dashboards

  6. Act on insights - Target high-risk users for additional training

  7. Document setup - Record region and configuration

Integration Maintenance​

Regular Checks​

Perform monthly:

  • Verify connection active
  • Check data freshness
  • Review sync timestamps
  • Test sample queries

Token Management​

Best practices:

  • Store securely
  • Document token creation date
  • Set annual rotation reminder
  • Have backup admin access

Data Validation​

Quarterly:

  • Compare Anzenna data with KnowBe4 reports
  • Verify user counts match
  • Check training completion accuracy
  • Validate phishing metrics

API Rate Limits​

KnowBe4 enforces API rate limits:

  • Varies by account plan
  • Anzenna respects rate limits
  • Automatic retry on throttling
  • Contact KnowBe4 support if issues persist

Regional Deployment​

API URL by Region​

RegionAPI URL
United Stateshttps://us.api.knowbe4.com
Europehttps://eu.api.knowbe4.com
Canadahttps://ca.api.knowbe4.com
United Kingdomhttps://uk.api.knowbe4.com

Use the URL matching your KnowBe4 data center.

Need help? Contact

Anzenna Support

for assistance.