Skip to main content

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, exceptions) is designed to be driven programmatically.

OpenTelemetry

Every alert and rule match is available in OpenTelemetry format, 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 supports the Model Context Protocol on both sides of the AI workflow: the Cerbera MCP server lets AI clients run Cerbera workflows on your behalf, and MCP governance discovers, allows, and blocks the MCP servers your employees connect to. Available today. 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, policies, and exceptions 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

CapabilityStatus
OpenTelemetry export to SIEMAvailable
MCP server and governanceAvailable
API endpointsAvailable
WebhooksRoadmap
Infrastructure-as-code configurationRoadmap

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.

Next Steps