<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Coraza on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/coraza/</link>
    <description>Recent content in Coraza on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 19 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/coraza/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted WAF Core Rule Set Management: ModSecurity CRS vs Coraza CRS vs NAXSI Rules</title>
      <link>https://www.pistack.xyz/posts/2026-05-19-self-hosted-waf-core-rule-set-modsecurity-coraza-naxsi-guide/</link>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-19-self-hosted-waf-core-rule-set-modsecurity-coraza-naxsi-guide/</guid>
      <description>&lt;p&gt;A Web Application Firewall (WAF) is only as effective as its rule set. While the WAF engine handles request inspection and blocking, the &lt;strong&gt;Core Rule Set (CRS)&lt;/strong&gt; defines what threats to look for — SQL injection patterns, cross-site scripting payloads, file inclusion attempts, and hundreds of other attack signatures.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
