<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CSP on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/csp/</link><description>Recent content in CSP on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/csp/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 10: Frontend Security: Protecting Your Application and Users</title><link>https://ai-blog.noorshomelab.dev/react-production-guide-2026/frontend-security-xss-csp/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/react-production-guide-2026/frontend-security-xss-csp/</guid><description>&lt;h2 id="chapter-10-frontend-security-protecting-your-application-and-users"&gt;Chapter 10: Frontend Security: Protecting Your Application and Users&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 10! As you build increasingly complex and interactive React applications, it&amp;rsquo;s paramount to remember that security isn&amp;rsquo;t just a backend concern—it&amp;rsquo;s a full-stack responsibility. The frontend, often the first point of interaction for your users, is a critical battleground for safeguarding data, maintaining user trust, and protecting your application&amp;rsquo;s integrity.&lt;/p&gt;
&lt;p&gt;In this chapter, we&amp;rsquo;ll dive deep into essential frontend security practices for modern React applications. You&amp;rsquo;ll learn how to defend against common vulnerabilities like Cross-Site Scripting (XSS), implement robust Content Security Policies (CSP), make informed decisions about secure data storage, and understand the risks and mitigations associated with third-party scripts. By the end, you&amp;rsquo;ll have a strong foundation for building more resilient and trustworthy React applications.&lt;/p&gt;</description></item><item><title>Chapter 16: Frontend Security: CSP, XSS, and Token Storage</title><link>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/frontend-security/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/frontend-security/</guid><description>&lt;h2 id="chapter-16-frontend-security-csp-xss-and-token-storage"&gt;Chapter 16: Frontend Security: CSP, XSS, and Token Storage&lt;/h2&gt;
&lt;p&gt;Welcome back, future Angular security guru! In the intricate world of web development, building robust features is only half the battle. The other, equally critical half is ensuring those features are secure. Neglecting security is like building a beautiful house with no locks on the doors – it might look great, but it&amp;rsquo;s an open invitation for trouble.&lt;/p&gt;
&lt;p&gt;This chapter dives deep into crucial frontend security practices for your Angular applications, leveraging the latest standalone architecture. We&amp;rsquo;ll unravel the mysteries of common attack vectors like Cross-Site Scripting (XSS) and explore how Angular&amp;rsquo;s built-in tools, such as &lt;code&gt;DomSanitizer&lt;/code&gt;, become your first line of defense. We&amp;rsquo;ll then elevate our security posture with Content Security Policy (CSP), a powerful browser-level mechanism. Finally, we&amp;rsquo;ll tackle the ever-present challenge of securely storing sensitive authentication tokens, weighing the trade-offs between various approaches. By the end of this chapter, you&amp;rsquo;ll not only understand these concepts but also know how to implement them effectively, giving you the confidence to build truly secure Angular applications.&lt;/p&gt;</description></item><item><title>How Content Security Policy (CSP) Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/content-security-policy-internals/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/content-security-policy-internals/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the intricate landscape of web security, protecting users from malicious attacks is a paramount concern. Content Security Policy (CSP) stands as a critical defense mechanism, acting as an additional layer of security to mitigate various code injection threats. It&amp;rsquo;s not merely a &amp;ldquo;firewall&amp;rdquo; but a sophisticated agreement between a web server and a browser, dictating precisely which resources the browser is permitted to load and execute for a given page.&lt;/p&gt;</description></item></channel></rss>