<?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: Forward Proxy &amp;amp; SSL Inbound Inspection Certificate Comparasion in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/forward-proxy-amp-ssl-inbound-inspection-certificate-comparasion/m-p/996225#M5132</link>
    <description>&lt;P&gt;1. for outbound proxy, the certificate needs to be CA and have the private key, for inbound inline inspection, you need to have the server certificate associated with the web service running on the server. you only need to have the key, this does not need to be a CA certificate&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. do NOT use the same certificate for trusted and untrusted. the trusted one needs to be imported on the client so it trusts the signing CA certificate. the untrust must not be imported so the user gets a certificate error (it's untrusted because the upstream certificate is untrusted, this needs to be aparent to the user as well as they would else have the false impression this site is safe&lt;/P&gt;</description>
    <pubDate>Tue, 03 Dec 2024 13:18:37 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2024-12-03T13:18:37Z</dc:date>
    <item>
      <title>Forward Proxy &amp; SSL Inbound Inspection Certificate Comparasion</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/forward-proxy-amp-ssl-inbound-inspection-certificate-comparasion/m-p/995987#M5121</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;1- The CA and Keys checkboxes in the Certificates section of Palo Alto Firewall should always be selected? respectively the certificates used for Forward Proxy and SSL Inbound Inspection should always have CA selected and Keys imported?&lt;BR /&gt;&lt;BR /&gt;2- We use just one self-signed certificate for Forward Trust and Untrust proxy. So we need to import this certificate as Trusted CA in client computer. My question, how client will understand then wenn a website is untrusted ? (the reason of my question is that we are using same self-signed certificate for both options)&lt;BR /&gt;&lt;BR /&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Mon, 02 Dec 2024 13:54:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/forward-proxy-amp-ssl-inbound-inspection-certificate-comparasion/m-p/995987#M5121</guid>
      <dc:creator>f.kuecuek</dc:creator>
      <dc:date>2024-12-02T13:54:50Z</dc:date>
    </item>
    <item>
      <title>Re: Forward Proxy &amp; SSL Inbound Inspection Certificate Comparasion</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/forward-proxy-amp-ssl-inbound-inspection-certificate-comparasion/m-p/996225#M5132</link>
      <description>&lt;P&gt;1. for outbound proxy, the certificate needs to be CA and have the private key, for inbound inline inspection, you need to have the server certificate associated with the web service running on the server. you only need to have the key, this does not need to be a CA certificate&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. do NOT use the same certificate for trusted and untrusted. the trusted one needs to be imported on the client so it trusts the signing CA certificate. the untrust must not be imported so the user gets a certificate error (it's untrusted because the upstream certificate is untrusted, this needs to be aparent to the user as well as they would else have the false impression this site is safe&lt;/P&gt;</description>
      <pubDate>Tue, 03 Dec 2024 13:18:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/forward-proxy-amp-ssl-inbound-inspection-certificate-comparasion/m-p/996225#M5132</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2024-12-03T13:18:37Z</dc:date>
    </item>
  </channel>
</rss>

