惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

小众软件
小众软件
博客园_首页
博客园 - 聂微东
T
Tailwind CSS Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks
The Cloudflare Blog
aimingoo的专栏
aimingoo的专栏
Martin Fowler
Martin Fowler
D
Docker
人人都是产品经理
人人都是产品经理
WordPress大学
WordPress大学
博客园 - 三生石上(FineUI控件)
Microsoft Azure Blog
Microsoft Azure Blog
Recent Announcements
Recent Announcements
Apple Machine Learning Research
Apple Machine Learning Research
阮一峰的网络日志
阮一峰的网络日志
B
Blog RSS Feed
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Microsoft Security Blog
Microsoft Security Blog
L
LangChain Blog
Jina AI
Jina AI
博客园 - Franky
D
DataBreaches.Net

Cerbos - All Posts

Authentik vs Keycloak: Self-hosted IdP comparison Mapping business requirements to authorization policy for automotive Fine-grained authorization for AI gateways EIC 2026: Stop counting agents, protect what they can touch Agent skill for writing authorization policies in Claude Desktop Identity security in 2026 EIC 2026 takeaways: the identity stack built for humans will not hold up for AI agents Already have authentication? Here's the authorization layer you still need. Tokens are authorization decisions: a guide to policy-driven token issuance What is a Runtime Authorization Platform It's a dimmer switch, not a kill switch. How CISOs are rethinking AI agent governance From maps to bitmaps (and from bitmaps to bitmaps) AuthZEN, Shared Signals, SCIM Events, IPSIE: Notes from the OpenID Enterprise Panel How do you update authorization policies without redeploying your application? IIW42 recap: Where agent authorization got real Cerbos PDP v0.52.0/v0.53.0: Engine performance, security hardening, and CEL path functions Authorization Management Platforms: what they do, how they work, and where they fit PocketOS AI coding agent deleted a production database in 9 seconds Non-Human Identity management still has a blind spot Supabase alternative in 2026: Best open source auth options Benefits of on-premise authorization: Why enterprises are moving toward self-hosted Authorization policies: How to write, test, and validate them (faster with AI) Agent skill for writing authorization policies How much does it cost to build authorization in-house? Why centralized authorization governance reduces incident response time OPA alternative Why AI agents make authorization a right now problem Modernizing legacy application authorization: why it’s your biggest security blind spot How to add authorization to legacy applications without code changes 5 authorization blind spots auditors find, and how to fix them
Access control for RAG and LLMs - live demo
Alex Olivier · 2024-11-15 · via Cerbos - All Posts

As more businesses adopt Retrieval Augmented Generation (RAG) models to enhance their AI systems, managing access control becomes increasingly crucial. In a recent CNCF Live demo session, Alex Olivier walked viewers through how to implement authorization in RAG architectures using Cerbos PDP, an open-source authorization solution.

This blog unpacks the live, providing insights into RAG architecture, its security challenges, and how Cerbos ensures secure and efficient authorization. If you're looking for ways to install guardrails around your AI systems - read on.

Understanding RAG and its components

RAG is a powerful architecture for augmenting large language models (LLMs) with external data. Here’s a quick breakdown:

  • The vector store stores vectorized representations of your data.
  • The embedding model converts raw data into vector embeddings.
  • The LLM generates responses based on augmented prompts.

Alex emphasized that most RAG setups lack context-awareness regarding user permissions. This creates a risk where AI agents might retrieve and serve data users shouldn't access.

Security challenges in RAG architectures

Alex highlighted several key risks that RAG architectures introduce. Chief among them being unauthorized data exposure. Without proper access controls, LLMs can inadvertently retrieve and provide sensitive information to users who lack the necessary permissions.

This risk is exacerbated by the need for dynamic data access, where LLMs must filter information in real time based on factors like user roles, geographic regions, and specific business rules.

Additionally, traditional role-based access control (RBAC) systems often struggle to scale in modern enterprises, where complex organizational structures and rapidly changing access requirements demand more flexible and granular authorization models.

Why access control matters + demo highlights

As Alex explained, Cerbos acts as a gatekeeper, allowing context-aware authorization decisions at various stages of the RAG pipeline, from initial query processing to final response generation.

Here’s how it works:

  • When a user asks a question to an AI chatbot - Cerbos enforces existing permission policies to ensure the user has permission to invoke an agent.
  • Before retrieving data, Cerbos creates a query plan that defines which conditions must be applied when fetching data to ensure it is only the records the user can access based on their role, department, region, or other attributes.
  • Then Cerbos provides an authorization filter to limit the information fetched from your vector database or other data stores.
  • Allowed information is used by LLM to generate a response, making it relevant and fully compliant with user permissions.

Conclusion

Implementing access control for RAG and LLM architectures is no longer optional—it's a necessity. Cerbos can be used for this purpose. It helps safeguard sensitive data, meet compliance requirements, and maintain AI performance.

Ready to enhance your RAG security? Explore Cerbos, and our documentation.