<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Appsec on CSP Guide</title>
    <link>https://csp-guide.com/tags/appsec/</link>
    <description>Recent content in Appsec on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/appsec/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Audit Your Existing CSP Policy</title>
      <link>https://csp-guide.com/posts/how-to-audit-your-existing-csp-policy/</link>
      <pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/how-to-audit-your-existing-csp-policy/</guid>
      
      <description>&lt;p&gt;A CSP audit is mostly about answering one question: does this policy actually reduce risk, or does it just look security-ish in a scanner?&lt;/p&gt;
&lt;p&gt;I’ve seen plenty of CSPs that technically exist but barely help. The usual pattern is a giant allowlist, &lt;code&gt;unsafe-inline&lt;/code&gt; hanging around forever, and a team that’s scared to touch it because analytics or consent tooling might break. Fair enough. CSP can get messy fast.&lt;/p&gt;
&lt;p&gt;Here’s a practical way to audit the policy you already have, using a real-world header as the running example.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
