<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ghost on CSP Guide</title>
    <link>https://csp-guide.com/tags/ghost/</link>
    <description>Recent content in Ghost on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/ghost/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Ghost: Copy-Paste Policies That Actually Work</title>
      <link>https://csp-guide.com/posts/csp-for-ghost-blogging-platform/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-ghost-blogging-platform/</guid>
      
      <description>&lt;p&gt;Ghost is pretty clean from a CSP perspective, but the moment you add analytics, consent banners, custom themes, comments, or embeds, things get messy fast.&lt;/p&gt;
&lt;p&gt;I’ve had the best results treating Ghost like this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;start with a tight baseline policy&lt;/li&gt;
&lt;li&gt;add only what your theme and integrations actually need&lt;/li&gt;
&lt;li&gt;avoid &lt;code&gt;unsafe-inline&lt;/code&gt; for scripts if you can&lt;/li&gt;
&lt;li&gt;accept that &lt;code&gt;style-src &#39;unsafe-inline&#39;&lt;/code&gt; is often the practical compromise on Ghost themes unless you control every template&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This guide is a reference you can copy from and adjust.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
