Integration coverage,
stated per capability.
Connecting to a system is not the same as governing it. For each connector we state separately whether it can discover access, evaluate it, make approved changes, validate the result and export evidence.
What each connector does today.
Each cell reflects a review of the product's code and its automated tests on 19 October 2026. Implemented means the capability is built against the provider's own API and covered by automated tests; partial means it covers only part of what the column describes. No connector has yet been verified end to end against a live customer or test tenant, and changes to connected systems are not enabled in the hosted service until that verification is complete. For an evaluation we confirm the exact scope for your systems in writing first.
| Connector | Discovery | Evaluation | Approved writes | Validation | Evidence export |
|---|---|---|---|---|---|
| Microsoft Entra IDIdentity | Implemented | Implemented | Implemented | Partial | Partial |
| Microsoft 365SaaS and licensing | Implemented | Implemented | Implemented | In development | In development |
| Microsoft AzureCloud resources | Partial | Partial | In development | In development | In development |
| OktaIdentity | Partial | In development | Partial | In development | Partial |
| GitHubDeveloper platform | Partial | In development | Partial | In development | Partial |
| Google WorkspaceIdentity and SaaS | In development | In development | Partial | In development | In development |
| Amazon Web ServicesCloud, findings import | In development | In development | In development | In development | In development |
| Google CloudCloud, findings import | In development | In development | In development | In development | In development |
| Edge agent (Linux)Host inventory, read-only | Partial | In development | Not offered | Not offered | Implemented |
What the columns mean
- Discovery: reads users, groups, roles and licenses from the system
- Evaluation: applies defined rules to what was read and raises findings
- Approved writes: makes a change in the system through an approval-controlled plan; changes that do not go through approval are not counted here
- Validation: reads the system again to confirm an approved change took effect
- Evidence export: records the related request, approval and action in a signed evidence package
Restricted and disconnected networks
The edge agent runs on Linux inside your network, makes outbound connections only and performs read-only collection, so it suits restricted networks that allow outbound traffic. Networks with no outbound path at all need a separate transfer procedure, which is not offered today. We will not describe a deployment as air-gapped unless that procedure exists and has been tested with you.