<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Tim&#39;s Tech Thoughts</title>
    <link>https://cloudy.dev/tags/security/</link>
    <description>Recent content in Security on Tim&#39;s Tech Thoughts</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Mar 2026 10:32:00 -0400</lastBuildDate>
    <atom:link href="https://cloudy.dev/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Amazon Bedrock&#39;s Security Model: What Enterprises Actually Need to Know</title>
      <link>https://cloudy.dev/article/amazon-bedrock-security/</link>
      <pubDate>Sat, 07 Mar 2026 10:32:00 -0400</pubDate>
      <guid>https://cloudy.dev/article/amazon-bedrock-security/</guid>
      <description>&lt;p&gt;One of the most common blockers I hear from enterprise teams evaluating generative AI isn&amp;rsquo;t about model quality — it&amp;rsquo;s about trust. &lt;em&gt;Where does our data go? Can AWS see our prompts? Will our inputs be used to train someone else&amp;rsquo;s model? Can we meet our compliance requirements?&lt;/em&gt; These are the right questions to ask, and Amazon Bedrock has spent considerable engineering effort making sure the answers are satisfying.&lt;/p&gt;&#xA;&lt;p&gt;This post walks through the core pillars of Bedrock&amp;rsquo;s security model: how inference stays private, what AWS commits to around your data, how to keep traffic off the public internet, what compliance certifications are in place, how IAM gives you fine-grained access control, and how AgentCore&amp;rsquo;s Cedar policies extend that control to the level of individual agent tool calls.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
