<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security-Automation on Elliot Belt</title><link>https://felixbillieres.github.io/tags/security-automation/</link><description>Recent content in Security-Automation on Elliot Belt</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>felix.billieres@ecole2600.com (Elliot Belt)</managingEditor><webMaster>felix.billieres@ecole2600.com (Elliot Belt)</webMaster><copyright>© 2026 Elliot Belt</copyright><lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://felixbillieres.github.io/tags/security-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Operating a Semi-Autonomous Security Research Pipeline Without Turning It Into a Scanner</title><link>https://felixbillieres.github.io/posts/operating-a-semi-autonomous-security-research-pipeline/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><author>felix.billieres@ecole2600.com (Elliot Belt)</author><guid>https://felixbillieres.github.io/posts/operating-a-semi-autonomous-security-research-pipeline/</guid><description>How the pipeline keeps research state, selects provider capacity, records evidence and routes updates to Discord while retaining human control over scope and reporting.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://felixbillieres.github.io/posts/operating-a-semi-autonomous-security-research-pipeline/featured.png"/></item></channel></rss>