<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on Homelab Journal</title><link>https://mareox.github.io/homelab-journal/topics/python/</link><description>Recent content in Python on Homelab Journal</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Mario</copyright><lastBuildDate>Fri, 01 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mareox.github.io/homelab-journal/topics/python/index.xml" rel="self" type="application/rss+xml"/><item><title>Your Firewall Baseline Should Fail Builds</title><link>https://mareox.github.io/homelab-journal/posts/2026/pytest-panos-firewall-testing/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://mareox.github.io/homelab-journal/posts/2026/pytest-panos-firewall-testing/</guid><description>&lt;p>Most organizations can tell you whether their firewalls are healthy. Fewer can prove every allow rule is inspected, logged, owned, and still required.&lt;/p>
&lt;p>The gap between those two things is where audits become painful. Multiple firewall admins, emergency changes at 2am, quarterly reviews that turn into archaeology digs, vendor access rules that were &amp;ldquo;temporary&amp;rdquo; in February and are still there in October. Nobody disabled them because nobody noticed they were still there. No alert fires when a rule that was supposed to be temporary quietly becomes permanent.&lt;/p></description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://mareox.github.io/homelab-journal/posts/2026/pytest-panos-firewall-testing/thumbnail.png"/></item></channel></rss>