<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Networking on Cyberforks</title>
    <link>https://blog.cyberforks.com/tags/networking/</link>
    <description>Recent content in Networking on Cyberforks</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.cyberforks.com/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop Renting Holes in Your Firewall</title>
      <link>https://blog.cyberforks.com/posts/stop-renting-holes-in-your-firewall/</link>
      <pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberforks.com/posts/stop-renting-holes-in-your-firewall/</guid>
      <description>I spent an afternoon chasing a firewall rule that kept breaking, and the fix that finally stuck was deleting the port behind it off the public internet entirely. Source-IP allowlists are a maintenance treadmill that quietly rots into someone else&amp;rsquo;s access — here&amp;rsquo;s the inversion that ends it.</description>
    </item>
  </channel>
</rss>
