<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Red-Team on t0ul</title><link>https://t0ul.com/tags/red-team/</link><description>Recent content in Red-Team on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/red-team/index.xml" rel="self" type="application/rss+xml"/><item><title>A live red-team against the real model</title><link>https://t0ul.com/blog/a-live-red-team-against-the-real-model/</link><pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/a-live-red-team-against-the-real-model/</guid><description>&lt;p&gt;&lt;em&gt;Part of my &lt;a href="https://t0ul.com/blog/the-plan/"&gt;AI Security Engineering&lt;/a&gt; series, a local email-to-calendar agent I build, then attack, then harden. If you have not set up the lab yet, start with &lt;a href="https://t0ul.com/blog/setting-up-the-lab/"&gt;Set up your lab&lt;/a&gt;. The lessons are &lt;a href="https://github.com/t0ul/ai-security-engineering"&gt;on GitHub&lt;/a&gt;, and the agent itself lives at &lt;a href="https://github.com/t0ul/emaildrop"&gt;t0ul/emaildrop&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-suite-that-tests-nothing"&gt;The suite that tests nothing&lt;/h2&gt;
&lt;p&gt;Every live-tagged test in this book has had the same comment at the top: run against the local model, fail if it is down, never skip. This post is why. A security suite for an LLM agent has a tempting shortcut built into every testing framework, and taking it quietly turns the whole scorecard into decoration.&lt;/p&gt;</description></item><item><title>The app-layer red team: GORED</title><link>https://t0ul.com/blog/the-app-layer-red-team-gored/</link><pubDate>Tue, 06 Oct 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/the-app-layer-red-team-gored/</guid><description>&lt;p&gt;&lt;em&gt;Part of my &lt;a href="https://t0ul.com/blog/the-plan/"&gt;AI Security Engineering&lt;/a&gt; series, a local email-to-calendar agent I build, then attack, then harden. If you have not set up the lab yet, start with &lt;a href="https://t0ul.com/blog/setting-up-the-lab/"&gt;Set up your lab&lt;/a&gt;. The lessons are &lt;a href="https://github.com/t0ul/ai-security-engineering"&gt;on GitHub&lt;/a&gt;, and the agent itself lives at &lt;a href="https://github.com/t0ul/emaildrop"&gt;t0ul/emaildrop&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-authors-blind-spots"&gt;The author&amp;rsquo;s blind spots&lt;/h2&gt;
&lt;p&gt;This book has been one person attacking their own work, which is the honest way to learn and the dishonest way to finish. Every attack here was written by the same hand that wrote the defense, so every attack is shaped by the same assumptions, and the vulnerabilities an author cannot imagine are exactly the ones their tests will never contain. A finished system deserves one thing its builder cannot provide: an adversary who does not already know how it is supposed to work.&lt;/p&gt;</description></item></channel></rss>