<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AIDE – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/aide/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Thu, 05 Nov 2026 20:00:00 +0100</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/aide/index.xml" rel="self" type="application/rss+xml"/><item><title>Deep Dive: AIDE and rkhunter on a K3s Host – Integrity Checks Without Drowning in False Alarms</title><link>https://www.apt-upgrade.me/2026/11/05/deep-dive-aide-and-rkhunter-on-a-k3s-host-integrity-checks-without-drowning-in-false-alarms/</link><pubDate>Thu, 05 Nov 2026 20:00:00 +0100</pubDate><guid>https://www.apt-upgrade.me/2026/11/05/deep-dive-aide-and-rkhunter-on-a-k3s-host-integrity-checks-without-drowning-in-false-alarms/</guid><description>&lt;p&gt;An integrity checker is only as good as the mails it sends. If it reports hundreds of changes every morning, nobody reads them after a week – and the one real finding gets lost with them. That was my problem with AIDE and rkhunter on three K3s hosts: both worked, but mostly they reported things I had caused myself.&lt;/p&gt;&#10;&lt;p&gt;This deep dive shows what the two tools do, where the noise comes from on a Kubernetes host, and how the baseline follows every intended change.&lt;/p&gt;</description></item><item><title>The Ansible Tour, Part 5: IT Security – Firewall, SSH, fail2ban, Hardening, SELinux and Detection</title><link>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-5-security/</link><pubDate>Mon, 19 Oct 2026 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-5-security/</guid><description>&lt;p&gt;&lt;em&gt;Part 5 of the &lt;a href="https://www.apt-upgrade.me/2026/10/14/ansible-tour-part-1-framework/"&gt;Ansible Tour&lt;/a&gt;. After the platform, the blog and Nextcloud, this part gathers all security roles in one place, across both stacks. The series describes release &lt;a href="https://github.com/aptupgrademe/www_k3s/tree/v3.3.0"&gt;v3.3.0&lt;/a&gt;, with later changes added as updates.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Security here comes from layers: each one catches what the previous one missed. From the outside in, these are the firewall, the SSH login, the reaction to attacks in the logs (fail2ban), the hardening of the operating system, containment by SELinux, and detection by auditd, AIDE, rkhunter and ClamAV. The code is public, so an attacker can read it too. That is fine: the protection has to come from keys, layers and alerts, not from secrecy. Exact thresholds still stay vague here.&lt;/p&gt;</description></item><item><title>Germany Only: Geo-Fencing SSH with nftables and Ansible (and What My Logs Said About Bots and Readers)</title><link>https://www.apt-upgrade.me/2026/10/01/geo-fencing-ssh-with-nftables-and-ansible/</link><pubDate>Thu, 01 Oct 2026 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/01/geo-fencing-ssh-with-nftables-and-ansible/</guid><description>&lt;p&gt;After moving two &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt; instances to new servers this week, I asked a simple question: &lt;em&gt;do my three servers - this blog and the two Nextclouds - attract different kinds of attackers?&lt;/em&gt; The answer was mostly &amp;ldquo;no, it&amp;rsquo;s the same background noise everywhere&amp;rdquo;. Except for one line that bugged me: &lt;strong&gt;SSH&lt;/strong&gt;. It runs on a non-standard port, accepts keys only, and fail2ban watches it. And yet the blog alone logged around &lt;strong&gt;16 connection attempts per hour&lt;/strong&gt; to the SSH daemon, from all over the world.&lt;/p&gt;</description></item><item><title>151 Pass, 113 Fail: My Linux Box Gets a Reality Check</title><link>https://www.apt-upgrade.me/2026/08/20/1302/</link><pubDate>Thu, 20 Aug 2026 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/08/20/1302/</guid><description>&lt;p&gt;Same evening, different layer of the stack. 🥱➡️🤓 After the kube-bench post I got a very reasonable follow-up question in the comments-that-live-in-my-own-head: &lt;em&gt;&amp;ldquo;okay but what about the actual Linux box underneath all this Kubernetes stuff?&amp;rdquo;&lt;/em&gt; Fair point. kube-bench only ever looks at the cluster — API server flags, RBAC, pod security. The AlmaLinux 9 host it&amp;rsquo;s all running on top of never got the same treatment. So, one more late-night detour. 🐧🔍&lt;/p&gt;</description></item></channel></rss>