<?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 Certificate vulnerable *Urgent* in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329449#M83630</link>
    <description />
    <pubDate>Mon, 25 May 2020 11:14:04 GMT</pubDate>
    <dc:creator>sahithyan.subbu</dc:creator>
    <dc:date>2020-05-25T11:14:04Z</dc:date>
    <item>
      <title>Certificate vulnerable *Urgent*</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329449#M83630</link>
      <description />
      <pubDate>Mon, 25 May 2020 11:14:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329449#M83630</guid>
      <dc:creator>sahithyan.subbu</dc:creator>
      <dc:date>2020-05-25T11:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate vulnerable *Urgent*</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329503#M83641</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Best is to get a valid cert from your PKI that is recognized by the vulnerability scanner. That way it will see it as not a self-signed certificate and hopefully when generated it was made using RSA2048 or higher.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2020 21:55:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329503#M83641</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2020-05-22T21:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate vulnerable *Urgent*</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329567#M83653</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 May 2020 11:15:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329567#M83653</guid>
      <dc:creator>sahithyan.subbu</dc:creator>
      <dc:date>2020-05-25T11:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: Certificate vulnerable *Urgent*</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329640#M83665</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Any certificate generated with RSA 2048 is going to be secure. However this will not get rid of the finding with the vulnerability scanner.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that answers your question.&lt;/P&gt;</description>
      <pubDate>Sat, 23 May 2020 16:43:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/certificate-vulnerable-urgent/m-p/329640#M83665</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2020-05-23T16:43:22Z</dc:date>
    </item>
  </channel>
</rss>

