<?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 Allowed SSL traffic reporting as policy-deny in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/533967#M1007</link>
    <description>&lt;P&gt;We have a decryption rule to allow user internet access over SSL. Access to LinkedIn was working until 2 days back we started getting certificate error with validity expired. All users accessing the internet use the same CA signed certificate with no issues. I have attached the logs showing access permitted but the&amp;nbsp; session end reason is policy-deny.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Mar 2023 15:04:00 GMT</pubDate>
    <dc:creator>tejasmapuskar</dc:creator>
    <dc:date>2023-03-10T15:04:00Z</dc:date>
    <item>
      <title>Allowed SSL traffic reporting as policy-deny</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/533967#M1007</link>
      <description>&lt;P&gt;We have a decryption rule to allow user internet access over SSL. Access to LinkedIn was working until 2 days back we started getting certificate error with validity expired. All users accessing the internet use the same CA signed certificate with no issues. I have attached the logs showing access permitted but the&amp;nbsp; session end reason is policy-deny.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 15:04:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/533967#M1007</guid>
      <dc:creator>tejasmapuskar</dc:creator>
      <dc:date>2023-03-10T15:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: Allowed SSL traffic reporting as policy-deny</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/533968#M1008</link>
      <description>&lt;P&gt;Check Decryption logs from that source to that destination and you will find the answer.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Mar 2023 15:05:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/533968#M1008</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2023-03-10T15:05:27Z</dc:date>
    </item>
    <item>
      <title>Re: Allowed SSL traffic reporting as policy-deny</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/534206#M1014</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for looking into it. The issue was fixed after renewing the expired Digicert issue on the firewall.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Mar 2023 15:25:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/allowed-ssl-traffic-reporting-as-policy-deny/m-p/534206#M1014</guid>
      <dc:creator>tejasmapuskar</dc:creator>
      <dc:date>2023-03-13T15:25:31Z</dc:date>
    </item>
  </channel>
</rss>

