<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rbac on t0ul</title><link>https://t0ul.com/tags/rbac/</link><description>Recent content in Rbac on t0ul</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 21 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://t0ul.com/tags/rbac/index.xml" rel="self" type="application/rss+xml"/><item><title>A governed control plane and operator roles</title><link>https://t0ul.com/blog/a-governed-control-plane-and-operator-roles/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://t0ul.com/blog/a-governed-control-plane-and-operator-roles/</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="from-building-it-to-running-it"&gt;From building it to running it&lt;/h2&gt;
&lt;p&gt;The agent is finished. Every feature is wired and every attack from the outside is contained. This part is about the other half of security, the half that starts once the thing is deployed and a team has to operate it: who is allowed to change it, what happens when it crashes, and how you prove after the fact what it did. The threats here are not a hostile newsletter. They are a mistaken operator, a leaked credential, a change nobody reviewed.&lt;/p&gt;</description></item></channel></rss>