Security & Compliance
Lynx Compliance - Connectors (External Data Sources)
Generic connector framework for pulling compliance evidence from external systems (cloud providers, IdPs, SIEMs). Pluggable per-system implementations.
lynx_compliance_connectors
· v19.0.1.0.0
· Premium
What this solves
Lynx Compliance - Connectors
Pluggable framework that lets compliance evidence collectors pull data from any external system - cloud providers, identity providers, SIEMs - through a saved connection and a unified result shape.
Most evidence lives outside Odoo: the IdP knows who has MFA, the cloud provider knows what storage is encrypted, the SIEM knows what logs were forwarded. Rather than hard-coding one connector per provider, this module ships a small framework: a saved connection record, a Python registry of connector types, a test-connection action, and a hook into the external_api collector path. Provider modules register their own type and answer collector queries.
Key Features
Connection registry - lynx.compliance.connector stores credentials and config, one record per external system instance.
Pluggable types - connector types are a Python registry; each provider module (AWS, Patrii Cloud, Azure...) registers its own implementation.
Test-connection action - one-click connectivity check from the connection form.
Collector wiring - external_api collectors call a registered connector and receive a unified result shape suitable for evidence storage.
Read-only credentials - encryption at rest for secrets; collectors run with least-privilege calls only.
Integrates With
lynx_compliance_evidence_collectors - this is the channel for external_api collectors.
lynx_compliance_connector_patrii, lynx_compliance_connector_aws - provider-specific implementations.
Try Lynx Compliance - Connectors (External Data Sources) on your team.
Free trial, no credit card. Talk to sales when you're ready.