Connector integrations

Connect the tools your customers already use

Osinet Command ingests data from the security, backup, endpoint, and network vendors your customers have deployed. Each connector is backed by a typed module registry that controls which dashboard cards appear — no empty tiles for tools a customer does not have.

Identity & Cloud Productivity

Microsoft 365

Live

Per-customer identity posture: MFA registration, risky users, Conditional Access, inactive licensed users, sign-in anomalies, and admin user audit.

MFA coverage
Risky users
Conditional Access
Inactive users
Service health
License utilization

Google Workspace

Roadmap

Identity module equivalent for Google Workspace tenants. Admin audit, 2FA coverage, suspended accounts.

Identity posture — planned

Okta / JumpCloud

Roadmap

SSO and directory provider integration for identity posture data beyond Microsoft environments.

Identity posture — planned

Backup & Disaster Recovery

Acronis Cyber Protect

Live

Per-customer backup posture: workload protection status, failed jobs (24h/7d), last successful backup, immutable backup verification, and task-level results.

Backup health
Failed job counts
Last backup timestamp
Workload protection
Immutable backup status

Veeam

Roadmap

Backup health and job monitoring equivalent for Veeam-protected environments.

Backup health — planned
Backup jobs — planned

Cove / N-able / Datto BCDR

Roadmap

Additional backup vendors in the module registry possibleVendors list.

Backup health — planned

Endpoint Security & EDR

ESET Protect

Live

Per-customer AV and endpoint coverage: device groups, devices with issues, vulnerability counts, detection availability, telemetry level, and protection status.

Antivirus protection
Device inventory
Detection counts
Vulnerability counts

SentinelOne

Live

Per-customer EDR posture: agent count, active threats, infected agents, offline agents, site-level mapping, and threat detection severity.

EDR / Threat detections
Agent count
Active threats
Device inventory

Sophos / Microsoft Defender / CrowdStrike

Roadmap

Additional endpoint and EDR vendors in the possibleVendors list for future implementation.

Endpoint security — planned
EDR — planned

Email & Network Security

Check Point Harmony Email & Collaboration

Live

Per-customer email security events via HEC: total events, quarantine count, links replaced, suspicious or blocked count. Domain and account-level mapping.

Email security events
Quarantine count
Links replaced
Suspicious count

FortiGate

Live

Firewall health monitoring module. Currently shows connection status; detailed traffic and policy data on the module roadmap.

Firewall status

Palo Alto / Cisco Meraki / Mimecast

Roadmap

Additional network security and email security vendors planned for future connector releases.

Firewall / network — planned
Email security — planned
Connector module framework

How new connectors are added

Each connector registers its dashboard modules in a typed registry (connector-modules.ts). The registry records which module keys (e.g., edr_threats, backup_health) each connector supplies, which vendors are currently implemented, and which are planned. The dashboard renderer reads from this registry to determine card visibility based on org-level connector availability — no hardcoded dashboard changes are needed to add a new vendor.

Step 1
Register the module

Add the connector's module keys to connector-modules.ts with possibleVendors and currentImplementedVendors.

Step 2
Implement the sync

Add a connector sync route that fetches and stores snapshot data in Supabase via the snapshot store.

Step 3
Enable for your organization

Enable the connector in your org's connector settings. The dashboard card appears automatically once enabled.

Accuracy note

Connectors marked Live are currently in production and producing real data when configured. Connectors marked Roadmap are named in the module registry's possibleVendors field as planned future implementations — they are not yet connected and will not appear in the dashboard until implemented and enabled. Additional connectors not listed here can be scoped on request.

Ready to connect your first vendor?

Sign in and go to Integrations to enter your connector credentials.