<?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: Using Third Party Certificates on a Palo in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35159#M25830</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One workaround would be use a separate web server to buy a wildcard certificate from Commercial CA with something like&amp;nbsp; *.yourdomain.com. Then export the certificate and private key file in PKCS or PEM format from that web server to PaloAlto firewall or Panorama.&lt;/P&gt;&lt;P&gt;I think it may not be possible to generate CSR (Certificate Signing Request) from a PaloAlto firewall as I could not see any option to do that.&lt;/P&gt;&lt;P&gt;Then the workaround like above helped.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 12 Nov 2012 13:36:39 GMT</pubDate>
    <dc:creator>pandragon</dc:creator>
    <dc:date>2012-11-12T13:36:39Z</dc:date>
    <item>
      <title>Using Third Party Certificates on a Palo</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35157#M25828</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does anyone know what the best certificate to use on a Palo is please? We have a customer who is failing PCI compliance testing as we are using a self signed certificate which was generated on the Palo for Global Protect. Any help or advise would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 15:20:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35157#M25828</guid>
      <dc:creator>GNS_Support</dc:creator>
      <dc:date>2012-11-09T15:20:51Z</dc:date>
    </item>
    <item>
      <title>Re: Using Third Party Certificates on a Palo</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35158#M25829</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are loads of CAs that browsers will support by default.&amp;nbsp; It's really a question of budget and preference.&amp;nbsp; Comodo for cheap, VeriSign for good service.&amp;nbsp; Never GoDaddy for anything (IMO).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concerning PCI, you could setup a compensating control that states that all the users that connect to the service have the correct cert in their local store and are trained on how to deal with a non-trusted response.&amp;nbsp; In that case you can just keep the self-signed cert.&amp;nbsp; &amp;lt;disclaimer&amp;gt; I am not a QSA, your client needs to check w/ their QSA if they want to go down this road&amp;lt;/disclaimer&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But really, so far as PAN is concerned, it shouldn't matter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Nov 2012 16:38:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35158#M25829</guid>
      <dc:creator>msullivan</dc:creator>
      <dc:date>2012-11-09T16:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: Using Third Party Certificates on a Palo</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35159#M25830</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;One workaround would be use a separate web server to buy a wildcard certificate from Commercial CA with something like&amp;nbsp; *.yourdomain.com. Then export the certificate and private key file in PKCS or PEM format from that web server to PaloAlto firewall or Panorama.&lt;/P&gt;&lt;P&gt;I think it may not be possible to generate CSR (Certificate Signing Request) from a PaloAlto firewall as I could not see any option to do that.&lt;/P&gt;&lt;P&gt;Then the workaround like above helped.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Nov 2012 13:36:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/using-third-party-certificates-on-a-palo/m-p/35159#M25830</guid>
      <dc:creator>pandragon</dc:creator>
      <dc:date>2012-11-12T13:36:39Z</dc:date>
    </item>
  </channel>
</rss>

