<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>compliance – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/compliance/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Thu, 20 Aug 2026 20:00:00 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/compliance/index.xml" rel="self" type="application/rss+xml"/><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>