<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cedar on The road</title><link>https://kane.mx/tags/cedar/</link><description>Recent content in Cedar on The road</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 06 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kane.mx/tags/cedar/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Tenant Bedrock Agents Security with Cedar</title><link>https://kane.mx/posts/2026/multi-tenant-agent-security-blueprint/</link><pubDate>Sat, 06 Jun 2026 00:00:00 +0000</pubDate><guid>https://kane.mx/posts/2026/multi-tenant-agent-security-blueprint/</guid><description>
&lt;h2 id="tldr-30-second-read">TL;DR (30-Second Read)&lt;/h2>
&lt;p>With Amazon Bedrock AgentCore now generally available — including &lt;strong>AgentCore Identity&lt;/strong> for agent authentication and &lt;strong>AgentCore Policy&lt;/strong>, which enforces Cedar rules by intercepting every tool call before execution — the security design for multi-tenant SaaS on Bedrock Agents has reached an inflection point. This blueprint addresses the hardest problem in agentic SaaS: a Large Language Model (LLM) that, through prompt injection or hallucination, crosses tenant boundaries or escalates privileges. The answer is a &lt;strong>zero-trust, low-latency, two-layer authorization architecture with real-time quota enforcement&lt;/strong>, built on Amazon Verified Permissions (AVP) and the Cedar policy engine.&lt;/p>
&lt;p>&lt;a href="https://kane.mx/posts/2026/multi-tenant-agent-security-blueprint/">Read More&lt;/a>&lt;/p></description></item></channel></rss>