<?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 AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/rbac/</link><description>Recent content in RBAC on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 08 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/rbac/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 11: Implementing Robust Security: Rate Limiting, CORS, &amp;amp; RBAC</title><link>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/11-security-rbac/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/11-security-rbac/</guid><description>&lt;h2 id="chapter-11-implementing-robust-security-rate-limiting-cors--rbac"&gt;Chapter 11: Implementing Robust Security: Rate Limiting, CORS, &amp;amp; RBAC&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 11 of our Node.js backend journey! In this chapter, we&amp;rsquo;re diving deep into critical security enhancements that are non-negotiable for any production-ready application: Rate Limiting, Cross-Origin Resource Sharing (CORS), and Role-Based Access Control (RBAC). These mechanisms are essential for protecting your API from abuse, enabling secure interactions with frontend applications, and ensuring users only access resources they are authorized to see.&lt;/p&gt;</description></item></channel></rss>