<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Tenancy on CuraSec</title><link>https://curasec.metacog.co.kr/tags/multi-tenancy/</link><description>Recent content in Multi-Tenancy on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 16 Jul 2026 12:18:39 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/multi-tenancy/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-auth multi-tenant flaw found in DoD-backed SaaS platform</title><link>https://curasec.metacog.co.kr/insights/2026-07-16-securing-a-dod-contractor-finding-a-multi-tenant-authorizati/</link><pubDate>Thu, 16 Jul 2026 12:18:39 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-16-securing-a-dod-contractor-finding-a-multi-tenant-authorizati/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> A real-world case study on broken object-level authorization in a multi-tenant SaaS context — review your own tenant-isolation logic and authorization checks at API boundaries for similar patterns.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Illustrates how authorization failures in multi-tenant SaaS can expose all customers&amp;rsquo; data, useful context for vendor risk assessments and security questionnaire review criteria.&lt;/li>
&lt;/ul></description></item></channel></rss>