SSL Inbound Inspection: key vs cert, destination address

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

SSL Inbound Inspection: key vs cert, destination address

L2 Linker

The PAN-OS Administrator's Guide for version 6.0 gives a description of setting up SSL Inbound Inspection on page 295.  In step 2, it instructs to import the target's certificate.  In step 4 it instructs to create a decryption policy by specifying the destination address of the targeted server.

Questions:

1. Doesn't the PA require the encryption key, not just the encryption certificate to perform inbound SSL inspection?

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->DMZ), should the destination address be the public or private IP?

3. How do you know the answer to (2)?  Is there a section in the administrator's guide that spells this out?  I would like to learn more about this so that I can figure out the answer to those sorts of questions on my own.

Thank you,

Chris

1 accepted solution

Accepted Solutions

L4 Transporter

Hello,

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.

Hope this helps.

Thanks

View solution in original post

2 REPLIES 2

L4 Transporter

Hello,

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.

Hope this helps.

Thanks

Okay TY.  So it looks like the documentation in the Admin Guide is wrong on re key vs cert.  I will try to bring it up with the private IP and see if that works.

  • 1 accepted solution
  • 2738 Views
  • 2 replies
  • 1 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!