<?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 BlueSquadron — Security engineering for AI systems</title><link>https://bluesquadron.dev/tags/multi-tenancy/</link><description>Recent content in Multi-Tenancy on BlueSquadron — Security engineering for AI systems</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>florent.batard@gmail.com (Florent Batard)</managingEditor><webMaster>florent.batard@gmail.com (Florent Batard)</webMaster><lastBuildDate>Tue, 11 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bluesquadron.dev/tags/multi-tenancy/index.xml" rel="self" type="application/rss+xml"/><item><title>Watari: A Security Control That Was Never On</title><link>https://bluesquadron.dev/posts/watari-a-control-that-was-never-on/</link><pubDate>Tue, 11 Aug 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/watari-a-control-that-was-never-on/</guid><description>Watari&amp;rsquo;s headline claim is tenant isolation enforced by PostgreSQL Row-Level Security. The policies had been in the schema for months and had never once taken effect. Turning them on took four changes that had to land together — and none of them was writing a policy.</description></item></channel></rss>