<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI-DLC on BlueSquadron — Security engineering for AI systems</title><link>https://bluesquadron.dev/tags/ai-dlc/</link><description>Recent content in AI-DLC 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/tags/ai-dlc/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>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>