<?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 What problems or vulnerabilities does this present? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/what-problems-or-vulnerabilities-does-this-present/m-p/531616#M920</link>
    <description>&lt;P&gt;&lt;STRONG&gt;IMPORTANT NOTE&lt;/STRONG&gt;&lt;SPAN&gt;: Never set both checkboxes "Forward Trust Certificate" and "Forward Untrust Certificate" in the same certificate, and do not have the "Forward Untrust Certificate" deployed under a trusted certificate chain. If you do this, it&amp;nbsp;will cause the firewall to present client devices with a CA certificate they trust, even when they&amp;nbsp;connect&amp;nbsp;to&amp;nbsp;websites or applications&amp;nbsp;that are presenting with invalid certificates to the firewall.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;My SSL inspection&amp;nbsp; cert is selected forward trust, forward untrust, and trusted root CA...&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am using an MS CA setup. &lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Feb 2023 20:40:56 GMT</pubDate>
    <dc:creator>Stevenjw0728</dc:creator>
    <dc:date>2023-02-17T20:40:56Z</dc:date>
    <item>
      <title>What problems or vulnerabilities does this present?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/what-problems-or-vulnerabilities-does-this-present/m-p/531616#M920</link>
      <description>&lt;P&gt;&lt;STRONG&gt;IMPORTANT NOTE&lt;/STRONG&gt;&lt;SPAN&gt;: Never set both checkboxes "Forward Trust Certificate" and "Forward Untrust Certificate" in the same certificate, and do not have the "Forward Untrust Certificate" deployed under a trusted certificate chain. If you do this, it&amp;nbsp;will cause the firewall to present client devices with a CA certificate they trust, even when they&amp;nbsp;connect&amp;nbsp;to&amp;nbsp;websites or applications&amp;nbsp;that are presenting with invalid certificates to the firewall.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;My SSL inspection&amp;nbsp; cert is selected forward trust, forward untrust, and trusted root CA...&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am using an MS CA setup. &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Feb 2023 20:40:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/what-problems-or-vulnerabilities-does-this-present/m-p/531616#M920</guid>
      <dc:creator>Stevenjw0728</dc:creator>
      <dc:date>2023-02-17T20:40:56Z</dc:date>
    </item>
    <item>
      <title>Re: What problems or vulnerabilities does this present?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/what-problems-or-vulnerabilities-does-this-present/m-p/531635#M921</link>
      <description>&lt;P&gt;This is all really about preserving the untrusted state of an invalid internet certificate when you have SSL decryption in the PA and passed that connection to an internal client.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When you decrypt a public site with a valid SSL certificate on the PA, you intercept the SSL connection, decrypt the data, and then re-sign the connection to the internal client with your own internally trusted certificate (either a self-signed certificate, or an internal CA-signed certificate, that you have distributed to your clients). The client sees the HTTPS connection as secure because the connection is signed by a certificate it trusts (the PA). This is the "Forward Trust Certificate" setting.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, when your client is connecting to an internet site that has an invalid certificate for whatever reason (is invalid for the host, fraudulent, self-signed, etc.), you want to preserve that invalid state so the client browser warns the end user. If you were to SSL decrypt and re-sign the connection with your trusted PA certificate, then the client will trust the public site even though it has an untrusted internet certificate. Therefore, you want to create a second untrusted certificate on the PA (which is not internally signed or distributed to the clients) and use that certificate to re-sign the untrusted internet connections - associated to the "Forward Untrust Certificate". That way the client sees an untrusted certificate in the connection and warns the end user.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Feb 2023 00:13:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/what-problems-or-vulnerabilities-does-this-present/m-p/531635#M921</guid>
      <dc:creator>Adrian_Jensen</dc:creator>
      <dc:date>2023-02-18T00:13:41Z</dc:date>
    </item>
  </channel>
</rss>

