<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firewall on AI VOID</title><link>https://ai-blog.noorshomelab.dev/categories/firewall/</link><description>Recent content in Firewall on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/categories/firewall/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 6: Network Address Translation (NAT)</title><link>https://ai-blog.noorshomelab.dev/palo-alto-ngfw-mastery/nat-configuration/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/palo-alto-ngfw-mastery/nat-configuration/</guid><description>&lt;h2 id="introduction-to-network-address-translation-nat"&gt;Introduction to Network Address Translation (NAT)&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 6! So far, we&amp;rsquo;ve built a solid foundation, understanding the core architecture of Palo Alto Networks firewalls and how to craft powerful security policies. But what happens when the IP addresses on your internal network aren&amp;rsquo;t meant to be seen by the outside world? Or when you need external users to reach an internal server without knowing its private IP? That&amp;rsquo;s where Network Address Translation, or NAT, steps in.&lt;/p&gt;</description></item></channel></rss>