<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Clickjacking on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/clickjacking/</link><description>Recent content in Clickjacking on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 07 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/clickjacking/index.xml" rel="self" type="application/rss+xml"/><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>