Enforce fine-grained, topic-level access control on your Kafka cluster using the same Cerbos policies that govern your application.
Cerbos speaks Kafka's native protocol, no custom glue code required
The same CEL-based policies that govern your application layer extend to your infrastructure
Authorization at every layer of your stack, managed from a single control plane
Apache Kafka provides a native integration point for Cerbos, extending policy-driven authorization to another layer of your stack without custom glue code.
Cerbos policies are written in human-readable YAML supporting RBAC, ABAC, and conditional rules. The same policies that govern your application layer now extend to Apache Kafka, enforced consistently everywhere.
A unified control plane means one set of policies, one audit trail, and one management workflow, regardless of how many services and infrastructure layers your system spans.
Apache Kafka powers event-driven architectures across industries. But securing who can produce to or consume from specific topics is often limited to ACLs that are difficult to manage at scale and disconnected from your application's authorization model.
Cerbos brings the same fine-grained, attribute-based policies you use in your application layer to your Kafka cluster. Define who can access which topics based on roles, departments, data classification, or any custom attribute, all in human-readable YAML.
Kafka's built-in ACL system requires you to manage allow/deny lists per principal and resource. Cerbos replaces this with declarative policies that can express complex rules: engineers in the payments team can produce to payments.* topics, while data analysts can only consume from analytics.* topics in read-only consumer groups.
Cerbos authorization for Apache Kafka is available as part of Cerbos enterprise. Talk to us to learn more about securing your Kafka cluster with Cerbos policies.
Cerbos integrates with Kafka's pluggable authorizer interface. When a client attempts to produce, consume, or administer a topic, Kafka delegates the authorization decision to Cerbos, which evaluates your policies against the principal, the Kafka resource (topic, consumer group, cluster), and the operation.
Any operation Kafka's authorization framework surfaces, produce, consume, create/delete topics, alter configs, manage consumer groups, and transactional operations. Cerbos policies let you write rules based on topic names, client identity, consumer group, and custom attributes.
Yes. Cerbos supports scoped policies and resource-level rules. You can write policies that apply only to specific topics, topic prefixes, or environments, and version them alongside your application policies.
What is Cerbos?
Cerbos is an end-to-end enterprise authorization software for Zero Trust environments and AI-powered systems. It enforces fine-grained, contextual, and continuous authorization across apps, APIs, AI agents, MCP servers, services, and workloads.
Cerbos consists of an open-source Policy Decision Point, Enforcement Point integrations, and a centrally managed Policy Administration Plane (Cerbos Hub) that coordinates unified policy-based authorization across your architecture. Enforce least privilege & maintain full visibility into access decisions with Cerbos authorization.