<?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: Use SSL Inbound Inspection to decrypt  cause  did‘t general url log in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336407#M84737</link>
    <description>&lt;P&gt;ok, I see,thanks you reply.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jul 2020 06:17:10 GMT</pubDate>
    <dc:creator>Felixcao</dc:creator>
    <dc:date>2020-07-02T06:17:10Z</dc:date>
    <item>
      <title>Use SSL Inbound Inspection to decrypt  cause  did‘t general url log</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336075#M84673</link>
      <description>&lt;P&gt;When customers use the https protocol to access our company's website from the Internet, they need to go through a firewall. After the client's access passes through the firewall, the URL log will be generated on the firewall.&lt;BR /&gt;But when we enabled SSL decryption on the wall, after decrypting the inbound traffic, the customer also visited the company's website, but it did not generate the url log. We did not make any other changes. Is this a normal result?&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 15:59:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336075#M84673</guid>
      <dc:creator>Felixcao</dc:creator>
      <dc:date>2020-06-30T15:59:36Z</dc:date>
    </item>
    <item>
      <title>Re: Use SSL Inbound Inspection to decrypt  cause  did‘t general url log</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336092#M84675</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/76688"&gt;@Felixcao&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;That wouldn't be expected, you should still be generating URL logs. The one thing that I would double check is that the security rulebase entry matching this traffic hasn't changed, and that the URL-Filtering profile assigned to the matched rulebase entry is setup to properly alert on the URL.&lt;/P&gt;
&lt;P&gt;It's very possible that with the inbound decryption the security entry matching this traffic has changed.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jun 2020 16:25:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336092#M84675</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-06-30T16:25:54Z</dc:date>
    </item>
    <item>
      <title>Re: Use SSL Inbound Inspection to decrypt  cause  did‘t general url log</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336407#M84737</link>
      <description>&lt;P&gt;ok, I see,thanks you reply.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2020 06:17:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/use-ssl-inbound-inspection-to-decrypt-cause-did-t-general-url/m-p/336407#M84737</guid>
      <dc:creator>Felixcao</dc:creator>
      <dc:date>2020-07-02T06:17:10Z</dc:date>
    </item>
  </channel>
</rss>

