<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Intrusion-Detection on Pi Stack</title><link>https://www.pistack.xyz/tags/intrusion-detection/</link><description>Recent content in Intrusion-Detection on Pi Stack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 19 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.pistack.xyz/tags/intrusion-detection/index.xml" rel="self" type="application/rss+xml"/><item><title>AIDE vs OSSEC vs Tripwire: Self-Hosted File Integrity Monitoring Guide 2026</title><link>https://www.pistack.xyz/posts/self-hosted-file-integrity-monitoring-aide-ossec-tripwire-guide-2026/</link><pubDate>Sun, 19 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.pistack.xyz/posts/self-hosted-file-integrity-monitoring-aide-ossec-tripwire-guide-2026/</guid><description>&lt;p>File integrity monitoring (FIM) is one of the most fundamental security controls for any self-hosted infrastructure. It answers a critical question: &lt;strong>has someone modified files on my server without authorization?&lt;/strong> Whether it&amp;rsquo;s a compromised binary, a backdoored configuration file, or an attacker planting a rootkit, file integrity monitoring detects changes to critical system files before they can cause damage.&lt;/p></description></item></channel></rss>