<?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: PCI compliance ECDHE/RSA in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520876#M3419</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/28576"&gt;@wicklunds&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good evening, well if you use a SSL/TLS profile, associated with a custom certificate, self-signed, or signed by an internal CA. You can generate it with ECDSA with a 256 or 384 or RSA at least 512 to 4096, at least for those self-signed by Palo Alto, but then if it is an internal CA, it depends on what support you have to generate certificates.&lt;/P&gt;
&lt;P&gt;And then this assign it to the firewall administration, to the Web-Gui, so that it responds that certificate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Review this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC#:~:text=value%3E%20%20%20%20%20%20%20%20%20%20Profile%20name-,admin%40192.168.1.1%23%20set%20shared%20ssl%2Dtls%2Dservice%2Dprofile%20TLSprofileTest%20protocol%2Dsettings,-(tab%20to%20view" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC#:~:text=value%3E%20%20%20%20%20%20%20%20%20%20Profile%20name-,admin%40192.168.1.1%23%20set%20shared%20ssl%2Dtls%2Dservice%2Dprofile%20TLSprofileTest%20protocol%2Dsettings,-(tab%20to%20view&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Thu, 10 Nov 2022 01:49:43 GMT</pubDate>
    <dc:creator>Metgatz</dc:creator>
    <dc:date>2022-11-10T01:49:43Z</dc:date>
    <item>
      <title>PCI compliance ECDHE/RSA</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520853#M3418</link>
      <description>&lt;P&gt;There were a couple of discussions on this months ago with no resolution. SecureTrust's PCI scans say that we are failing. We would need to set both RSA and ECDHE to 2048 but there is no option to do so that I know of for the SSL/TLS profile.&amp;nbsp; The workaround that was discussed was to disable ECDHE and RSA.&amp;nbsp; However, among other possible issues, it breaks the app for Apple devices.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Just wondering if anyone has come across a fix.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 13:27:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520853#M3418</guid>
      <dc:creator>wicklunds</dc:creator>
      <dc:date>2022-11-10T13:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: PCI compliance ECDHE/RSA</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520876#M3419</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/28576"&gt;@wicklunds&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good evening, well if you use a SSL/TLS profile, associated with a custom certificate, self-signed, or signed by an internal CA. You can generate it with ECDSA with a 256 or 384 or RSA at least 512 to 4096, at least for those self-signed by Palo Alto, but then if it is an internal CA, it depends on what support you have to generate certificates.&lt;/P&gt;
&lt;P&gt;And then this assign it to the firewall administration, to the Web-Gui, so that it responds that certificate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Review this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC#:~:text=value%3E%20%20%20%20%20%20%20%20%20%20Profile%20name-,admin%40192.168.1.1%23%20set%20shared%20ssl%2Dtls%2Dservice%2Dprofile%20TLSprofileTest%20protocol%2Dsettings,-(tab%20to%20view" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC#:~:text=value%3E%20%20%20%20%20%20%20%20%20%20Profile%20name-,admin%40192.168.1.1%23%20set%20shared%20ssl%2Dtls%2Dservice%2Dprofile%20TLSprofileTest%20protocol%2Dsettings,-(tab%20to%20view&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 01:49:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520876#M3419</guid>
      <dc:creator>Metgatz</dc:creator>
      <dc:date>2022-11-10T01:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: PCI compliance ECDHE/RSA</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520911#M3420</link>
      <description>&lt;P&gt;Thanks for the reply.&amp;nbsp; I should have mentioned that this is for PCI compliance.&amp;nbsp; As I understand it the article you posted only allows an on/off toggle.&amp;nbsp; Our certificate is not self-signed.&amp;nbsp; I'll double check but I believe it was generated properly.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2022 13:33:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/pci-compliance-ecdhe-rsa/m-p/520911#M3420</guid>
      <dc:creator>wicklunds</dc:creator>
      <dc:date>2022-11-10T13:33:15Z</dc:date>
    </item>
  </channel>
</rss>

