Cerbos AI agent security hero background
Features

|

AI gateway authorization

Govern every AI gateway request, agent, and delegation

Control which LLMs, tools, and agents each identity can reach through your AI gateway.

Security

Engineering

IAM

Prove what every agent did, on what resource, on whose behalf

Prove what every agent did, on what resource, on whose behalf

Every model call, tool use, agent-to-agent request runs through one policy layer. Auditors get one trail across humans, services & agents, in the same format as your app audit log.

No standing privilege for non-human identities

No standing privilege for non-human identities

Agents and service accounts only get the access the policy allows at the moment of the request. Pull access on the next call, no token rotation, no redeploy.

Regulator-ready evidence by default

Regulator-ready evidence by default

Decision, policy version, principal, resource, and delegation chain captured for every AI request. SOC 2, ISO 27001, HIPAA, NIS2, and DORA traceability without manual reconstruction.

Prove what every agent did, on what resource, on whose behalf
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner
Cerbos identity provider integration partner

AI gateways route the traffic. Authorization decides what gets through.

Your AI gateway authenticates the caller. It doesn't decide what that caller can do. Those decisions live inside applications, where identity and security teams have no visibility and no way to change them.

Your gateway authenticates. Your apps authorize.

Your gateway authenticates. Your apps authorize.

Once a request passes the gateway, every authorization decision lives in application code. Identity and security teams have no visibility into it and no way to change it.

The human behind the agent disappears.

The human behind the agent disappears.

When an agent acts on a user's behalf, the user vanishes from the audit trail. Auditors see a service account, not the person who triggered the action.

Sub-agents inherit everything.

Sub-agents inherit everything.

When one agent hands work to another, the second one picks up the full authority of the first. Capabilities expand silently, far beyond what the original request justified.

Revoking access is a fire drill.

Revoking access is a fire drill.

Without one policy layer, pulling an agent's permissions means rotating credentials, editing gateway config, or redeploying. Until that's done, the agent keeps acting on the access you're trying to revoke.

icon

Build your AI gateway authorization strategy

Control access for every AI interaction, at any scale

Govern every model call, tool invocation, MCP method, and agent-to-agent delegation the gateway routes, with the same policies that govern the APIs and data systems behind it.

Cerbos consistent access control across apps APIs and AI systems
Cerbos policy lifecycle management with Git and CI/CD
Cerbos Zero Trust runtime authorization for AI services
Cerbos compliance audit trail for authorization decisions
Cerbos authorization policy engine features overview
customer-testimonial-tertiary

How Utility Warehouse achieved continuous compliance across thousands of services and millions of NHIs with Cerbos.

SOC 2 & ISO audit-ready

AI agents secured

Threat detection

“We can trace every permission, investigate suspicious behavior, and answer questions about who did what, when, and why. We’ve gone from guesswork to forensic-level auditing across humans, machines, and everything in between.”

Read customer story
customer-testimonial-tertiary-mobile

Rob Crowe

Principal Engineer, Utility Warehouse

Put a policy engine alongside your AI gateway

Identity systems establish who someone is. Cerbos decides what they are allowed to do, at the moment the gateway enforces it.

How Cerbos authorization works - policy decision point architecture diagram

1

Every AI request goes through Cerbos first

When a user invokes an agent, an agent calls a tool or a model, or one agent delegates to another over A2A, the gateway sends the request to Cerbos before routing the call upstream - through a native authorization hook, a pre-request plugin, or an external authorization filter.

2

Cerbos evaluates the full picture

It pulls in who is calling, on whose behalf, what they want to do, which model or tool is involved, and the surrounding context, identity, resource attributes, risk, and the delegation chain, through the IdP, IGA, and data sources you already run.

3

The gateway enforces the decision

Allow or deny lands at the gateway before the request reaches the provider, and every decision is logged with the policy version that produced it. For high-capability agents, the gateway fails closed if the policy layer is unreachable.

Authorization for AI trafficand every other use case

Cerbos is an authorization management platform that
scales with your business.

Authorization for AI systems

Authorization for enterprise software

Authorization software that scales with your business

icon

ABAC

icon

RBAC

icon

ReBAC

icon

PBAC

icon

Runtime

icon

Event-time

icon

Admin-time

icon

Audit-time

icon

Legacy systems

icon

Cloud

icon

Self-hosted

icon

On-premise

icon

Air-gapped

Prove every AI decision,
not just every API call

SOC 2
SOC 2 verified badge

SOC 2

SOC 3
SOC 3 verified badge

SOC 3

HIPAA
HIPAA verified badge

HIPAA

ISO 27001
ISO 27001 verified badge

ISO 27001

GDPR
GDPR verified badge

GDPR

FedRAMP
FedRAMP verified badge

FedRAMP

PCI DSS
PCI DSS verified badge

PCI DSS

NIS2
NIS2 verified badge

NIS2

DORA
DORA verified badge

DORA

Capture every decision for all identities

Capture every decision for all identities

Log requests, actions, resources, access outcomes, and service-to-service authorization calls for both humans and machines.

Trace policy lineage

Trace policy lineage

See the exact policy, version, and release behind each decision for complete traceability.

Monitor with context

Monitor with context

Review detailed logs, policy versions, and real-time metrics across all PDPs and environments.

Simplify audits and compliance

Simplify audits and compliance

Maintain centralized, structured logs on-premise to support audits and demonstrate readiness for FedRAMP, SOC 2&3, ISO 27001, HIPAA, PCI DSS, and GDPR.

icon

Seamless integration

Works with every AI gateway, MCP server, LLM provider and SDK

ecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logoecosystem-logo
icon

Fine-grained identity security

Why teams choose Cerbos

Learn more about AI gateway authorization

Governing AI coding agents with Cerbos Synapse
Article icon

Article

Governing AI coding agents with Cerbos Synapse

Dynamic authorization for AI agents. A guide to fine-grained permissions in MCP servers
Guide icon

Guide

Dynamic authorization for AI agents. A guide to fine-grained permissions in MCP servers

Zero Trust for AI: Securing MCP Servers
Ebook icon

Ebook

Zero Trust for AI: Securing MCP Servers

Securing AI agents and non-human identities in enterprises
Ebook icon

Ebook

Securing AI agents and non-human identities in enterprises

Authorization for AI, enterprise software, and everything in between

Externalized, policy-based, runtime authorization for your AI gateway, agents, apps, and services.