<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cynative blog</title>
    <link>https://cynative.com/blog/</link>
    <description>Notes from the Cynative team on security agents, trust boundaries and sovereign models.</description>
    <language>en</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://cynative.com/blog/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Securing AI Agents on AWS: One HTTP Tool, One Action Gateway</title>
      <link>https://cynative.com/blog/aws-agent-action-gateway/</link>
      <guid isPermaLink="true">https://cynative.com/blog/aws-agent-action-gateway/</guid>
      <pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate>
      <author>contact@cynative.com (Yuri Shapira)</author>
      <description>Why Cynative gives security agents one HTTP tool, uses AWS-maintained models to follow API changes, and checks IAM actions before signing requests.</description>
    </item>
    <item>
      <title>Building Security Agents That Cannot Escape Their Trust Boundary</title>
      <link>https://cynative.com/blog/agent-trust-boundaries/</link>
      <guid isPermaLink="true">https://cynative.com/blog/agent-trust-boundaries/</guid>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
      <author>contact@cynative.com (Shaked Zin)</author>
      <description>Live access to production infrastructure, read-only by construction, with no path for the agent to widen it at runtime.</description>
    </item>
  </channel>
</rss>
