<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writing on BlueSquadron — Security engineering for AI systems</title><link>https://bluesquadron.dev/posts/</link><description>Recent content in Writing 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>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://bluesquadron.dev/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing AI-DLC: Process Integrity Is Not Product Security</title><link>https://bluesquadron.dev/posts/securing-the-ai-driven-development-lifecycle/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/securing-the-ai-driven-development-lifecycle/</guid><description>AI-DLC gives you the strongest process integrity I have seen in any methodology — approval gates, audit shards, element-level traceability. None of it tells you the code is safe. Those are different claims, and closing the gap phase by phase is the work.</description></item><item><title>The Security Coach for AI Agents</title><link>https://bluesquadron.dev/posts/security-coach-for-ai-agents/</link><pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/security-coach-for-ai-agents/</guid><description>Every team debating whether to trust the model has already made the decision that matters: where the boundary lives. A prompt is a promise. A tool interface is a constraint. Four patterns for telling them apart.</description></item><item><title>Sitadel: What You Owe People Once a Distro Ships Your Tool</title><link>https://bluesquadron.dev/posts/sitadel-what-you-owe-your-users/</link><pubDate>Tue, 18 Aug 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/sitadel-what-you-owe-your-users/</guid><description>Eight years, 179 commits, and packaged in Kali and BlackArch — which I did not plan and which changed what I am allowed to break. On finding quality over detection coverage, a hang that only existed in a real terminal, and the cleanup nobody asks for.</description></item><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><item><title>Secrust: When Adding Cores Made It Slower</title><link>https://bluesquadron.dev/posts/secrust-when-adding-cores-made-it-slower/</link><pubDate>Tue, 04 Aug 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/secrust-when-adding-cores-made-it-slower/</guid><description>A single-process Sigma correlation engine in Rust. Eight optimisation passes took the realistic workload up 301% — and then four threads made it 23% slower than two. Why that happened, what I shipped as the default, and the things I decided not to build.</description></item><item><title>Cutting 90% of the Noise: Agent-Driven Security Operations</title><link>https://bluesquadron.dev/posts/agent-driven-security-operations/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/agent-driven-security-operations/</guid><description>Tuning detections until the volume fits your headcount means choosing your visibility based on your staffing. The fix is not more analysts — it is separating the three layers of triage by what each one is allowed to be wrong about.</description></item><item><title>From 40 Hours to 8: Designing Security Into the AI Development Lifecycle</title><link>https://bluesquadron.dev/posts/designing-security-into-the-ai-development-lifecycle/</link><pubDate>Tue, 16 Jun 2026 00:00:00 +0000</pubDate><author>florent.batard@gmail.com (Florent Batard)</author><guid>https://bluesquadron.dev/posts/designing-security-into-the-ai-development-lifecycle/</guid><description>Not every deferred decision is an option. Some are debt whose strike price rises with the calendar — and security spends most of its budget servicing that debt rather than doing security.</description></item></channel></rss>