<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>bearhug AWS security blog</title>
    <link>https://bearhug.cloud/blog</link>
    <description>Recent cloud security incidents explained in plain English, with the checks a small AWS team can run today.</description>
    <language>en-gb</language>
    <lastBuildDate>Mon, 16 Nov 2026 17:00:00 +0000</lastBuildDate>
    <atom:link href="https://bearhug.cloud/blog/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>484,000 open buckets: what the 2026 Cloud Exposure Index means for small AWS teams</title>
      <link>https://bearhug.cloud/blog/cloud-exposure-index-2026-open-buckets</link>
      <description>New research counts 484,142 publicly listable buckets and 80,495 exposed .env files. Three S3 checks to run today, in plain English.</description>
      <pubDate>Mon, 16 Nov 2026 17:00:00 +0000</pubDate>
      <guid isPermaLink="true">https://bearhug.cloud/blog/cloud-exposure-index-2026-open-buckets</guid>
    </item>
    <item>
      <title>When a trusted vendor becomes the way in: lessons from the Qubole AWS incident</title>
      <link>https://bearhug.cloud/blog/qubole-aws-trusted-access-incident</link>
      <description>An attacker used a vendor&apos;s AWS access to reach dozens of customer accounts. What happened, and three checks any small AWS team can run today.</description>
      <pubDate>Mon, 16 Nov 2026 00:00:00 +0000</pubDate>
      <guid isPermaLink="true">https://bearhug.cloud/blog/qubole-aws-trusted-access-incident</guid>
    </item>
  </channel>
</rss>
