<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: AI Visibility with On-Premise NGFW in AIOps for NGFW Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/aiops-for-ngfw-discussions/ai-visibility-with-on-premise-ngfw/m-p/1264086#M660</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/56396"&gt;@ChrisShopp&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="8,0"&gt;The biggest blind spot with monitoring AI traffic is encryption. Standard App-ID and URL filtering will catch the initial domain handshake, but since almost every AI provider uses HTTPS, all the payload details are hidden inside the encrypted tunnel.&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;To see prompt contents, API payloads, or file transfers, you’ll need to set up SSL Decryption. Once decrypted, you can layer on tools like Enterprise DLP to alert on or block sensitive data moving into those tools.&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;Best,&lt;/P&gt;</description>
    <pubDate>Thu, 10 Sep 2026 11:49:05 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2026-09-10T11:49:05Z</dc:date>
    <item>
      <title>AI Visibility with On-Premise NGFW</title>
      <link>https://live.paloaltonetworks.com/t5/aiops-for-ngfw-discussions/ai-visibility-with-on-premise-ngfw/m-p/1263870#M658</link>
      <description>&lt;P&gt;Looking for recommendations or best practice items for monitoring/searching for AI usage through on-premise NGFWs.&amp;nbsp; Standard app-id/URL classifications already being used, but is there anything else that might help or make things more visibile?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2026 14:43:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/aiops-for-ngfw-discussions/ai-visibility-with-on-premise-ngfw/m-p/1263870#M658</guid>
      <dc:creator>ChrisShopp</dc:creator>
      <dc:date>2026-09-08T14:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: AI Visibility with On-Premise NGFW</title>
      <link>https://live.paloaltonetworks.com/t5/aiops-for-ngfw-discussions/ai-visibility-with-on-premise-ngfw/m-p/1264086#M660</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/56396"&gt;@ChrisShopp&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="8,0"&gt;The biggest blind spot with monitoring AI traffic is encryption. Standard App-ID and URL filtering will catch the initial domain handshake, but since almost every AI provider uses HTTPS, all the payload details are hidden inside the encrypted tunnel.&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;To see prompt contents, API payloads, or file transfers, you’ll need to set up SSL Decryption. Once decrypted, you can layer on tools like Enterprise DLP to alert on or block sensitive data moving into those tools.&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-path-to-node="8,1"&gt;Best,&lt;/P&gt;</description>
      <pubDate>Thu, 10 Sep 2026 11:49:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/aiops-for-ngfw-discussions/ai-visibility-with-on-premise-ngfw/m-p/1264086#M660</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2026-09-10T11:49:05Z</dc:date>
    </item>
  </channel>
</rss>

