<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Security - Tag - Buffo's Corner</title><link>https://buffos.github.io/tags/security/</link><description>Security - Tag - Buffo's Corner</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Mon, 16 Feb 2026 22:15:00 +0200</lastBuildDate><atom:link href="https://buffos.github.io/tags/security/" rel="self" type="application/rss+xml"/><item><title>Angular Enterprise Dashboard - Phase 2.5: Role-Based Access Control with Custom Directives</title><link>https://buffos.github.io/2026-03-16-phase-02-part-05/</link><pubDate>Mon, 16 Feb 2026 22:15:00 +0200</pubDate><author><name>Kostas</name><uri>https://buffos.github.io/authors/kostas/</uri></author><guid>https://buffos.github.io/2026-03-16-phase-02-part-05/</guid><description><![CDATA[<div class="featured-image">
                <img src="images/2026/angular-3-logo-png-transparent.png" referrerpolicy="no-referrer">
            </div><p>We’ve secured our routes with <a href="/blog/phase-02-part-02" rel="">Functional Guards</a>, but what about the UI itself? An Admin should see the &ldquo;Delete&rdquo; button, but a standard User should not.</p>]]></description></item><item><title>Angular Enterprise Dashboard - Phase 2.2: Securing the Perimeter - Functional Route Guards</title><link>https://buffos.github.io/2026-03-16-phase-02-part-02/</link><pubDate>Mon, 16 Feb 2026 21:56:00 +0200</pubDate><author><name>Kostas</name><uri>https://buffos.github.io/authors/kostas/</uri></author><guid>https://buffos.github.io/2026-03-16-phase-02-part-02/</guid><description><![CDATA[<div class="featured-image">
                <img src="images/2026/angular-3-logo-png-transparent.png" referrerpolicy="no-referrer">
            </div><p>In the previous part of this series, we built our <a href="/blog/phase-02-part-01" rel="">Reactive Authentication Service</a>. Now, we need to bridge the gap between our authentication state and our application&rsquo;s navigation.</p>]]></description></item></channel></rss>