<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Defense-in-Depth on t0ul</title><link>https://t0ul.com/tags/defense-in-depth/</link><description>Recent content in Defense-in-Depth on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/defense-in-depth/index.xml" rel="self" type="application/rss+xml"/><item><title>Defeating the lethal trifecta</title><link>https://t0ul.com/blog/defeating-the-lethal-trifecta/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/defeating-the-lethal-trifecta/</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="three-legs"&gt;Three legs&lt;/h2&gt;
&lt;p&gt;Simon Willison gave the pattern its name: the lethal trifecta is an agent that has all three of access to untrusted content, access to private data, and the ability to act or communicate outward. Each alone is fine. An agent that reads your email but can only draft replies is harmless; so is one that holds secrets but never sees an attacker&amp;rsquo;s words. Put all three in one process, though, and an instruction hidden in the untrusted content can walk a secret out the door.&lt;/p&gt;</description></item><item><title>A full-chain attack, contained</title><link>https://t0ul.com/blog/a-full-chain-attack-contained/</link><pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/a-full-chain-attack-contained/</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="one-email-every-attack"&gt;One email, every attack&lt;/h2&gt;
&lt;p&gt;The book has taken the attacks one at a time, which is how you learn them and not how they arrive. A real hostile email does not politely send its injection on Monday and its exfiltration on Tuesday. It packs everything into one message and hopes one thing gets through. So the capstone is a single email that tries the lot, run against the actual pipeline, with nothing mocked.&lt;/p&gt;</description></item></channel></rss>