<?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 ioctl</title><link>https://ioctl.lol/tags/rbac/</link><description>Recent content in Rbac on ioctl</description><generator>Hugo</generator><language>en</language><copyright>ioctl</copyright><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ioctl.lol/tags/rbac/index.xml" rel="self" type="application/rss+xml"/><item><title>azure-roles-digger.sh</title><link>https://ioctl.lol/tools/azure-roles-digger/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://ioctl.lol/tools/azure-roles-digger/</guid><description>&lt;h2 id="the-problem">The problem&lt;/h2>
&lt;p>Azure permission auditing is a special kind of hell.&lt;/p>
&lt;p>You run &lt;code>az role assignment list&lt;/code> and get back&amp;hellip; direct assignments. That&amp;rsquo;s it. No inherited roles from group nesting. No Entra ID directory roles. No PIM-eligible roles sitting there waiting to be activated. Nothing about what that service principal can &lt;em>actually&lt;/em> do when you trace the full chain.&lt;/p>
&lt;p>So you&amp;rsquo;re left clicking through 15 portal blades, running separate Graph queries, cross-referencing group memberships by hand, piecing it all together in a spreadsheet like it&amp;rsquo;s 2005. And after 30 minutes you&amp;rsquo;re still not sure you found everything.&lt;/p></description></item></channel></rss>