<?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: Impact after Changing the key size setting clears the current certificate cache. in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558032#M1844</link>
    <description>&lt;P&gt;Thanks for sharing if follow the KB steps to disable the weak cipher . Require to reboot the firewall ? what is the impact if currently I have certificate is using one of the weak cipher ?&lt;/P&gt;</description>
    <pubDate>Fri, 15 Sep 2023 00:29:59 GMT</pubDate>
    <dc:creator>JiaXiang</dc:creator>
    <dc:date>2023-09-15T00:29:59Z</dc:date>
    <item>
      <title>Impact after Changing the key size setting clears the current certificate cache.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/557861#M1835</link>
      <description>&lt;P&gt;Due to VA Scanner scan my firewall having vulnerabilities of&amp;nbsp;SSL Certificate Chain Contains RSA Keys Less Than 2048 bits .&lt;/P&gt;
&lt;P&gt;So I plan to follow below KB to change the key size.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/certificate-management/configure-the-key-size-for-ssl-forward-proxy-server-certificates" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/certificate-management/configure-the-key-size-for-ssl-forward-proxy-server-certificates&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the KB mentioned as below, may I know clear the certificate cache will have any impact ?&amp;nbsp; and change the keysize require to reboot firewall ?&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;
&lt;DIV class="itemgroup info" data-label="ADDITIONAL INFORMATION"&gt;
&lt;DIV&gt;
&lt;DIV class="note caution" data-label="CAUTION"&gt;
&lt;DIV&gt;
&lt;DIV&gt;
&lt;DIV class="p"&gt;
&lt;DIV&gt;Changing the key size setting clears the current certificate cache.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 14 Sep 2023 06:04:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/557861#M1835</guid>
      <dc:creator>JiaXiang</dc:creator>
      <dc:date>2023-09-14T06:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Impact after Changing the key size setting clears the current certificate cache.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/557900#M1839</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/195025"&gt;@JiaXiang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;I believe you are not interperting the findings from your VA scan properly.&lt;/P&gt;
&lt;P&gt;The link you mentioned will effect how PAN firewall is performing SSL decryption, while I am expecting your VA scan to have report that PAN firewall admin WebUI is&amp;nbsp; using server cert with short key. What you are probably looking for&amp;nbsp; is here - &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CmqeCAC&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2023 09:20:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/557900#M1839</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2023-09-14T09:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: Impact after Changing the key size setting clears the current certificate cache.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558032#M1844</link>
      <description>&lt;P&gt;Thanks for sharing if follow the KB steps to disable the weak cipher . Require to reboot the firewall ? what is the impact if currently I have certificate is using one of the weak cipher ?&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 00:29:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558032#M1844</guid>
      <dc:creator>JiaXiang</dc:creator>
      <dc:date>2023-09-15T00:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: Impact after Changing the key size setting clears the current certificate cache.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558085#M1851</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/195025"&gt;@JiaXiang&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;I haven't done this procedure yet,&amp;nbsp; so I am not completely sure. But I am almost certain that it doesn't require reboot, why:&lt;/P&gt;
&lt;P&gt;- WebUI is controlled by the management plane.&lt;/P&gt;
&lt;P&gt;- Here you can see the process responsible for serving the admin webui - &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLUeCAO" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PLUeCAO&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;- I would assume changing the ciphers will require restart only for that particular process, which has nothing to do with the dataplane - which is reponsible for processing traffic.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Based on the above I am almost certain that applying the changes will not have any effect on forwarded traffic. Only the current admin sessions using the WebUI will be closed (while process restart). Admin SSH sessions probably wouldn't be affected as well.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 07:03:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558085#M1851</guid>
      <dc:creator>aleksandar.astardzhiev</dc:creator>
      <dc:date>2023-09-15T07:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: Impact after Changing the key size setting clears the current certificate cache.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558090#M1852</link>
      <description>&lt;P&gt;Thank you, I test first .&lt;/P&gt;</description>
      <pubDate>Fri, 15 Sep 2023 07:25:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/impact-after-changing-the-key-size-setting-clears-the-current/m-p/558090#M1852</guid>
      <dc:creator>JiaXiang</dc:creator>
      <dc:date>2023-09-15T07:25:24Z</dc:date>
    </item>
  </channel>
</rss>

