Hello friends, welcome back to Day 32 of my PCNSA series. In this video I’m not doing only theory—I’m showing you the real lab steps to configure URL Filtering in a Palo Alto firewall and how to verify whether a URL is actually getting blocked or not. I use a simple topology with a test PC going through the Palo Alto to the internet, and I also highlight an important point: before URL filtering works properly, your basics must be in place—IP addressing, routing (default/static route), security policy, NAT, and (very important) SSL decryption. I start from Objects > URL Filtering, show you the default read-only profile, and then I clone it to create my own “my lab profile.” After that, I demonstrate a practical use case: blocking YouTube. I first check YouTube’s category (streaming media), then I change the action for that category (block/continue) and commit. On the test PC you can immediately see the behavior—either a block page, a “continue” prompt, or a connection reset. Finally, I do an experiment to explain why SSL decryption matters. With decryption enabled, you get proper user-facing responses like the continue page and better visibility; without decryption, the firewall can still block, but you lose some of that readable control/visibility because the traffic is encrypted. I also show where to confirm everything under Monitor > URL Filtering (action, category, rule name).