Openness & Interoperability
Philosophy
A security tool should not be one more dashboard your team has to babysit. The goal of Cerbera AI is the opposite: surface signals where you already work and let you automate the rest. The less time anyone spends inside the Cerbera app, the better the product is doing its job.
That means everything Cerbera AI produces (inventory, alerts, rule matches) is designed to flow out into your existing stack, and everything it consumes (configuration, policies) is designed to be driven programmatically.
OpenTelemetry export
Stream alerts and rule matches into your SIEM
MCP
Govern MCP servers today; connect your own AI client on the roadmap
API endpoints
Read inventory and alerts, manage rules and policies
Webhooks
Push events to your own automations as they happen
OpenTelemetry
Every alert and rule match is available in OpenTelemetry format, exported directly from the device to an endpoint you configure, the primary path for getting Cerbera AI signals into a SIEM where they can be correlated with the rest of your telemetry. See OpenTelemetry Export.
MCP
Cerbera addresses the Model Context Protocol on both sides of the AI workflow: MCP governance discovers, risk-scores, and lets you allow or block the MCP servers your employees connect to (available today), and connecting your own AI client to Cerbera to run workflows on your behalf is on the roadmap. See the MCP section.
API Endpoints
Cerbera AI exposes API endpoints to read the AI tool inventory, alerts, and rule matches, and to manage rules and default policies programmatically, instead of clicking through the UI. See API Endpoints.
Webhooks
Webhooks push events to your own automations the moment they happen, for example routing a new alert into a workflow engine or a Slack channel. On the roadmap; see Webhooks.
What's Available Today
| Capability | Status |
|---|---|
| OpenTelemetry export to SIEM | Available |
| MCP governance | Available |
| API endpoints | Available |
| MCP client integration (Connect to Cerbera) | Roadmap |
| Webhooks | Roadmap |
| Infrastructure-as-code configuration | Roadmap |
Where something is not available yet, it is a question of sequencing and payload design, not direction. Until self-service matures, Cerbera handles much of the integration work for you and progressively hands control back.