Connectors
Every connector page in this section follows the same layout so you can find what you need without hunting for it: what data it provides, how it authenticates, and exactly what permissions to grant are always in a table at the top, before any setup steps.
Supported connectors
| Connector | Data provided | Authentication |
|---|---|---|
| Tenable | Devices, Vulnerabilities | API key (Access Key + Secret Key) |
| Device42 | Devices | Username + password |
| Microsoft Entra ID | Devices, Users | OAuth2 (Azure app registration) |
| Microsoft Intune | Devices | OAuth2 (Azure app registration) |
| Microsoft Defender | Devices, Users, Vulnerabilities, Software | OAuth2 (Azure app registration) |
| Okta | Users, Devices | API token |
| CrowdStrike | Devices, Users, Vulnerabilities | OAuth2 (API client) |
A note on the three Microsoft connectors
Entra ID, Intune, and Defender are three separate connectors, each configured with its own Azure app registration and credentials. You don’t need to connect all three, and connecting one doesn’t require or affect the others. If you already use one Azure app registration for multiple purposes, you can reuse the same tenant ID / client ID / secret across more than one of these connectors, but each is still added and credentialed independently in Navigator.
Connecting more than one instance of the same tool
If you manage more than one instance of the same tool (for example, two separate Okta organizations), you can add the same connector type more than once. Just give each one a distinct connection name when you set it up. See Managing Connectors for details.
Don’t see your tool listed?
Let us know at support@chartingcyber.com. New connectors are added regularly.