<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by scripts/generate-seo-assets.ts. Do not edit by hand. -->
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Kite Logik — Blog</title>
    <link>https://www.kitelogik.com/blog</link>
    <description>OPA/Rego policy enforcement at the tool execution layer. Deterministic. Auditable. Infrastructure-level.</description>
    <language>en</language>
    <lastBuildDate>Tue, 04 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://www.kitelogik.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agent lifecycle attacks: what prompt-injection firewalls can&apos;t see</title>
      <link>https://www.kitelogik.com/blog/agent-lifecycle-attacks</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/agent-lifecycle-attacks</guid>
      <description>Four AI agent attack classes that live in the action layer — delegation, plans, budgets, and memory — and why input/output guardrails structurally miss them.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Threat model</category>
      <category>Agent lifecycle</category>
      <category>OPA</category>
    </item>
    <item>
      <title>Your model can be jailbroken. What happens next is the part you control.</title>
      <link>https://www.kitelogik.com/blog/jailbreak-under-policy-enforcement</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/jailbreak-under-policy-enforcement</guid>
      <description>A jailbroken agent controls what it asks for, not what executes. Where that boundary actually falls — and the four things a successful jailbreak still buys an attacker.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Prompt injection</category>
      <category>Threat model</category>
      <category>HITL</category>
    </item>
    <item>
      <title>The OWASP Agentic Top 10, scored against a policy engine</title>
      <link>https://www.kitelogik.com/blog/owasp-agentic-top-10-scored</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/owasp-agentic-top-10-scored</guid>
      <description>Which of the ten 2026 agentic risks a deterministic policy layer actually enforces: three fully, six partially, and one it arguably makes worse.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>OWASP</category>
      <category>Threat model</category>
      <category>Policy as code</category>
    </item>
    <item>
      <title>188 incidents, no attacker</title>
      <link>https://www.kitelogik.com/blog/agent-incidents-no-attacker</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/agent-incidents-no-attacker</guid>
      <description>The most expensive AI agent failures on record had no adversary — the agent did what it was told. What that means for a security model built on keeping attackers out.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Incidents</category>
      <category>Agent safety</category>
      <category>Budgets</category>
    </item>
    <item>
      <title>MCP tool poisoning: why an allowlist beats a scanner</title>
      <link>https://www.kitelogik.com/blog/mcp-tool-poisoning-allowlist</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/mcp-tool-poisoning-allowlist</guid>
      <description>A peer-reviewed benchmark found more capable models are more vulnerable to tool poisoning, not less. You cannot train your way out of this one.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>MCP</category>
      <category>Tool poisoning</category>
      <category>Supply chain</category>
    </item>
    <item>
      <title>The AI Act delay doesn&apos;t delay your evidence problem</title>
      <link>https://www.kitelogik.com/blog/ai-act-delay-evidence-problem</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/ai-act-delay-evidence-problem</guid>
      <description>High-risk obligations moved to December 2027. The event logging Article 12 requires still takes longer to retrofit than the extension buys you.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>EU AI Act</category>
      <category>Audit trail</category>
      <category>Record-keeping</category>
    </item>
    <item>
      <title>Your first agent policy, in YAML</title>
      <link>https://www.kitelogik.com/blog/your-first-agent-policy</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/your-first-agent-policy</guid>
      <description>Write an agent policy in a constrained YAML DSL, compile it to Rego, unit-test it, and dry-run a single event — without learning Rego first.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Rego</category>
      <category>Getting started</category>
      <category>Policy as code</category>
    </item>
    <item>
      <title>Where to put the gate: decorator, toolbox, or adapter</title>
      <link>https://www.kitelogik.com/blog/where-to-put-the-gate</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/where-to-put-the-gate</guid>
      <description>Three ways to wire policy enforcement into a Python agent — and the failure-mode difference that actually decides which one you want.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Architecture</category>
      <category>Python</category>
      <category>Integration</category>
    </item>
    <item>
      <title>Budgets are a security control, not a billing feature</title>
      <link>https://www.kitelogik.com/blog/budgets-are-a-security-control</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/budgets-are-a-security-control</guid>
      <description>A ceiling that fires on magnitude halts a runaway agent without diagnosing it — and the counter feeding it is part of your trust boundary.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Budgets</category>
      <category>Denial of wallet</category>
      <category>Agent safety</category>
    </item>
    <item>
      <title>Multi-agent handoffs are an unguarded trust boundary</title>
      <link>https://www.kitelogik.com/blog/multi-agent-handoffs-trust-boundary</link>
      <guid isPermaLink="true">https://www.kitelogik.com/blog/multi-agent-handoffs-trust-boundary</guid>
      <description>Most frameworks treat an agent-to-agent handoff as a function call. It is a privilege transfer, and almost nothing checks it before it happens.</description>
      <dc:creator>Louis Bryson</dc:creator>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <category>Multi-agent</category>
      <category>Delegation</category>
      <category>OWASP</category>
    </item>
  </channel>
</rss>
