<?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 SSL Inbound Inspection: key vs cert, destination address in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38044#M27858</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The PAN-OS Administrator's Guide for version 6.0 gives a description of setting up SSL Inbound Inspection on page 295.&amp;nbsp; In step 2, it instructs to import the target's &lt;STRONG&gt;certificate&lt;/STRONG&gt;.&amp;nbsp; In step 4 it instructs to create a decryption policy by specifying the &lt;STRONG&gt;destination address&lt;/STRONG&gt; of the targeted server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Doesn't the PA require the encryption &lt;STRONG&gt;key&lt;/STRONG&gt;, not just the encryption &lt;STRONG&gt;certificate&lt;/STRONG&gt; to perform inbound SSL inspection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. In the case where the server to be inspected is running in a DMZ behind a bi-directional NAT (and the policy is for Trust-&amp;gt;DMZ), should the &lt;STRONG&gt;destination address&lt;/STRONG&gt; be the public or private IP?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. How do you know the answer to (2)?&amp;nbsp; Is there a section in the administrator's guide that spells this out?&amp;nbsp; I would like to learn more about this so that I can figure out the answer to those sorts of questions on my own.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Aug 2014 18:47:00 GMT</pubDate>
    <dc:creator>cstech</dc:creator>
    <dc:date>2014-08-29T18:47:00Z</dc:date>
    <item>
      <title>SSL Inbound Inspection: key vs cert, destination address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38044#M27858</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The PAN-OS Administrator's Guide for version 6.0 gives a description of setting up SSL Inbound Inspection on page 295.&amp;nbsp; In step 2, it instructs to import the target's &lt;STRONG&gt;certificate&lt;/STRONG&gt;.&amp;nbsp; In step 4 it instructs to create a decryption policy by specifying the &lt;STRONG&gt;destination address&lt;/STRONG&gt; of the targeted server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Doesn't the PA require the encryption &lt;STRONG&gt;key&lt;/STRONG&gt;, not just the encryption &lt;STRONG&gt;certificate&lt;/STRONG&gt; to perform inbound SSL inspection?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. In the case where the server to be inspected is running in a DMZ behind a bi-directional NAT (and the policy is for Trust-&amp;gt;DMZ), should the &lt;STRONG&gt;destination address&lt;/STRONG&gt; be the public or private IP?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. How do you know the answer to (2)?&amp;nbsp; Is there a section in the administrator's guide that spells this out?&amp;nbsp; I would like to learn more about this so that I can figure out the answer to those sorts of questions on my own.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Aug 2014 18:47:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38044#M27858</guid>
      <dc:creator>cstech</dc:creator>
      <dc:date>2014-08-29T18:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Inbound Inspection: key vs cert, destination address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38045#M27859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will answer questions 2 and 3 first. It should be the private-ip address. There is not documentation but I have had this working in the lab with private ip-address. This is because I believe the decryption policy look-up happens after the traffic is translated when NAT policy is applied. Now to answer your first question, the certificate of the web server that we are importing to PA for inbound inspection has to be imported with the private key. Without the private key, will not be able to decrypt the traffic.&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Aug 2014 22:15:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38045#M27859</guid>
      <dc:creator>tshiv</dc:creator>
      <dc:date>2014-08-29T22:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: SSL Inbound Inspection: key vs cert, destination address</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38046#M27860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Okay TY.&amp;nbsp; So it looks like the documentation in the Admin Guide is wrong on re key vs cert.&amp;nbsp; I will try to bring it up with the private IP and see if that works.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Aug 2014 00:43:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-inbound-inspection-key-vs-cert-destination-address/m-p/38046#M27860</guid>
      <dc:creator>cstech</dc:creator>
      <dc:date>2014-08-30T00:43:39Z</dc:date>
    </item>
  </channel>
</rss>

