KnowBe4
Collect security awareness training and phishing simulation evidence from KnowBe4 read APIs.
Security operations
Evidence coverage
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- User inventory
- Group inventory
- Phishing campaigns metadata
- Phishing security tests data
- Training campaigns metadata
- Training enrollments progress and completion data
Least privilege
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Auth header value(secret credential)
- API base URL
- Auth header name
- Evidence endpoints (JSON)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
KnowBe4 evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in KnowBe4 evidence
Get a guided demo, or start by scanning any domain for free.