<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reporting on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/reporting/</link><description>Recent content in Reporting 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/tags/reporting/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 12: Logging, Monitoring &amp;amp; Reporting</title><link>https://ai-blog.noorshomelab.dev/palo-alto-ngfw-mastery/logging-monitoring-reporting/</link><pubDate>Tue, 23 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/palo-alto-ngfw-mastery/logging-monitoring-reporting/</guid><description>&lt;h2 id="introduction-to-logging-monitoring--reporting"&gt;Introduction to Logging, Monitoring &amp;amp; Reporting&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 12! So far, we&amp;rsquo;ve built a solid foundation, understanding how Palo Alto Networks Next-Generation Firewalls (NGFWs) classify traffic, enforce policies, and secure our networks. But what happens after a policy permits or denies traffic? How do we know if our security policies are effective, if threats are being blocked, or if users are accessing appropriate applications? This is where logging, monitoring, and reporting become absolutely essential.&lt;/p&gt;</description></item></channel></rss>