<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Access Control</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Access Control feed</description>
    <item>
      <title>Wiz Discloses CosmosEscape, and Practitioners Debate What Customers Could Have Done</title>
      <link>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Access+Control</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/08/cosmosescape-master-key/en/headerimage/generatedHeaderImage-1785835623595.jpg"/&gt;&lt;p&gt;Wiz Research disclosed CosmosEscape, a chain that escaped Azure Cosmos DB's Gremlin sandbox and reached a platform-wide key granting read and write access to every database on the service. Microsoft blocked the entry point within two days but took until July 2026 to remove the key. Practitioners debated shared responsibility and what that rearchitecture actually cost.&lt;/p&gt; &lt;i&gt;By Steef-Jan Wiggers&lt;/i&gt;</description>
      <category>Security Vulnerabilities</category>
      <category>Cloud Architecture</category>
      <category>Cloud</category>
      <category>Database</category>
      <category>Access Control</category>
      <category>Azure</category>
      <category>Multi-Tenant Data</category>
      <category>Multi-tenancy</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 06 Aug 2026 09:21:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/08/cosmosescape-master-key/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Access+Control</guid>
      <dc:creator>Steef-Jan Wiggers</dc:creator>
      <dc:date>2026-08-06T09:21:00Z</dc:date>
      <dc:identifier>/news/2026/08/cosmosescape-master-key/en</dc:identifier>
    </item>
  </channel>
</rss>
