<?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: SSL Decryption Certificate in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-decryption-certificate/m-p/46592#M34252</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For inbound decryption, the certificate needs to match the certificate on the web-server. For outbound decryption (SSL Forward Proxy), the certificate on the PA should be a sub-ordinate CA signed be your internal CA. You can also use a self-signed CA-certificate, but then this needs to be distributed to your clients as a trusted root ca. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can get more info from this document: &lt;A href="https://live.paloaltonetworks.com/docs/DOC-1412"&gt;How to Implement SSL Decryption&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 12 Jun 2014 13:56:01 GMT</pubDate>
    <dc:creator>torm</dc:creator>
    <dc:date>2014-06-12T13:56:01Z</dc:date>
    <item>
      <title>SSL Decryption Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-decryption-certificate/m-p/46591#M34251</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoNormal"&gt;&lt;SPAN style="color: #1f497d;"&gt;For SSL Decryption does the cert on the PALO need to be issued from the same enterprise cert chain as the workstations, or does the cert on the workstation have to match the cert on the PALO exactly?&amp;nbsp; We have about 2000 workstations that have been issued a unique cert already for other applications. &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;SPAN style="color: #1f497d;"&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal"&gt;&lt;SPAN style="color: #1f497d;"&gt;Mark&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jun 2014 16:30:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-decryption-certificate/m-p/46591#M34251</guid>
      <dc:creator>markk96</dc:creator>
      <dc:date>2014-06-11T16:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Decryption Certificate</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-decryption-certificate/m-p/46592#M34252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For inbound decryption, the certificate needs to match the certificate on the web-server. For outbound decryption (SSL Forward Proxy), the certificate on the PA should be a sub-ordinate CA signed be your internal CA. You can also use a self-signed CA-certificate, but then this needs to be distributed to your clients as a trusted root ca. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can get more info from this document: &lt;A href="https://live.paloaltonetworks.com/docs/DOC-1412"&gt;How to Implement SSL Decryption&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jun 2014 13:56:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-decryption-certificate/m-p/46592#M34252</guid>
      <dc:creator>torm</dc:creator>
      <dc:date>2014-06-12T13:56:01Z</dc:date>
    </item>
  </channel>
</rss>

