<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Intrusion-Prevention on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/intrusion-prevention/</link>
    <description>Recent content in Intrusion-Prevention on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/intrusion-prevention/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fail2Ban vs SSHGuard vs CrowdSec: Self-Hosted Intrusion Prevention 2026</title>
      <link>https://www.pistack.xyz/posts/2026-04-24-fail2ban-vs-sshguard-vs-crowdsec-self-hosted-intrusion-prevention-2026/</link>
      <pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-04-24-fail2ban-vs-sshguard-vs-crowdsec-self-hosted-intrusion-prevention-2026/</guid>
      <description>&lt;p&gt;When you expose any service to the internet, brute-force attacks are not a matter of &lt;em&gt;if&lt;/em&gt; but &lt;em&gt;when&lt;/em&gt;. SSH servers see thousands of failed login attempts per day from botnets scanning the entire IPv4 space. Web applications face credential stuffing and directory enumeration. Without automated protection, your server wastes resources on malicious traffic and eventually risks compromise.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
