Integrations / Reusable adapters
CyberPass is designed as a universal layer. Infrastructure differences are expressed through configuration and adapter types, not a separate codebase for every customer.
These interfaces already exist in the product. Compatibility with a specific IdP, LDAP schema, PKI and SIEM endpoint is validated in customer infrastructure.
Public and Private LLMs through a configurable base URL, encrypted provider key, connection test and model discovery.
OIDC with PKCE and signed ID-token validation; LDAP/AD bind, group-to-role mapping and managed auto-provisioning.
CEF over UDP, TCP or verified TCP/TLS, optional mTLS, delivery counters, an async queue and DLQ.
Device enrollment, loopback proxy and managed browser-extension channel.
Customer-specific values—URLs, credentials, CAs, aliases, groups and mappings—remain configuration. Code changes only for a new reusable protocol adapter.
We do not promise compatibility with a specific product until its version, claims/schema, network path and acceptance criteria are validated.
| Integration | Status | Approach |
|---|---|---|
| OIDC / SSO | Baseline | Authorization Code + PKCE, signed ID token and group-to-role mapping; the IdP defines MFA and lifecycle. |
| LDAP / Active Directory | Baseline | LDAPS/StartTLS, service bind, user bind and configurable attributes/filter. |
| SIEM over TLS | Available | Verified TCP/TLS, customer CA and optional client certificate. |
| KMS / HSM / external secret store | Optional | The current baseline is local AES-256-GCM; an external backend is selected during the pilot. |
| MCP tools | Baseline | Streamable HTTP tools/list and tools/call, allow/block/approval, argument DLP and metadata-only audit. Resources, prompts and sampling are not yet proxied. |
An integration assessment needs the endpoint contract, authentication, network path and acceptance criteria.
Discuss integrations →