<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kibana on CSP Guide</title>
    <link>https://csp-guide.com/tags/kibana/</link>
    <description>Recent content in Kibana on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/kibana/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Elasticsearch Frontends: Options, Tradeoffs, and Gotchas</title>
      <link>https://csp-guide.com/posts/csp-for-elasticsearch-frontend/</link>
      <pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-elasticsearch-frontend/</guid>
      
      <description>&lt;p&gt;If you put Elasticsearch behind a browser-facing frontend, your Content Security Policy gets tricky fast.&lt;/p&gt;
&lt;p&gt;The problem usually is not Elasticsearch itself. It’s the frontend around it: Kibana, a custom React app, embedded dashboards, analytics tags, cookie banners, WebSocket connections, and a build pipeline that quietly injects inline scripts when you are not looking.&lt;/p&gt;
&lt;p&gt;I’ve seen teams lock down &lt;code&gt;default-src &#39;self&#39;&lt;/code&gt; and feel good for five minutes, then discover their search UI needs &lt;code&gt;connect-src&lt;/code&gt; for the cluster API, &lt;code&gt;wss:&lt;/code&gt; for live updates, and some awful third-party script exception because marketing won an argument.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
