<?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: How Palo Alto NGFW Prevent Unknow CVEs? in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-palo-alto-ngfw-prevent-unknow-cves/m-p/575920#M2578</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/223298"&gt;@SopheaHem&lt;/a&gt;&amp;nbsp;- CVE IDs are centrally allocated, but it is inevitable that there is some duplication and overlap among the 220,000+ CVE &lt;A href="https://www.cve.org/" target="_self"&gt;records&lt;/A&gt; currently available. Sometimes an "unknown" one (to us) might actually be known to us as a different CVE ID.&amp;nbsp; A similar story would apply to any other security vendor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bear in mind that CVE IDs can be allocated before any information is known about the specifics of the threat, and without threat specifics we would need to rely on other heuristics to identify a novel threat.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Like any good answer, the best answer I can give here is, "it depends."&amp;nbsp; No security vendor, be it Palo Alto Networks or anyone else, can&amp;nbsp;&lt;EM&gt;guarantee&lt;/EM&gt; anything about detecting and eliminating unknown CVEs, and you should be highly suspicious of claims to the contrary.&amp;nbsp; If they're unknown, or highly novel, there is always a risk that they could slip past unnoticed.&amp;nbsp; This is where tools like App-ID, URL Filtering, and WildFire, and having a sensible but strict security policy that utilises them, really come into their own.&amp;nbsp; &amp;nbsp;Defence in depth is an excellent approach as well: don't just rely on App-ID, for example, but instead use all of the tools at your disposal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Moreover, not every CVE is network-centric, which makes it hard for a next-generation firewall to have any impact, positive or negative, on the detection of those.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What we can also do is use tools like Advanced WildFire to detect and eliminate threats, including novel one threats, as quickly as possible using a range of analysis tools and techniques.&amp;nbsp; This can also include threats that don't (yet) have a CVE identified.&amp;nbsp; This relies on the knowledge gained from multiple sources including other customer environments using Advanced WildFire, which means that on average, any novel threat will have been seen at least once, and hopefully identified as such, before it encroaches on your environment.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 04 Feb 2024 23:02:59 GMT</pubDate>
    <dc:creator>iarobertson</dc:creator>
    <dc:date>2024-02-04T23:02:59Z</dc:date>
    <item>
      <title>How Palo Alto NGFW Prevent Unknow CVEs?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-palo-alto-ngfw-prevent-unknow-cves/m-p/572473#M2405</link>
      <description>&lt;P&gt;Dear Team,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="color: #252525;"&gt;I hope all of you are doing well.&lt;/P&gt;
&lt;P style="color: #252525;"&gt;I have one question. How can PA prevent an unknown CVE on NGFW?&lt;/P&gt;
&lt;P style="color: #252525;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="color: #252525;"&gt;Why I brought up this question is because I saw that from one vendor to another, they have different CVE numbers and IDs.&lt;/P&gt;
&lt;P style="color: #252525;"&gt;I was wondering if you could advise me.&lt;/P&gt;
&lt;P style="color: #252525;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="color: #252525;"&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 10 Jan 2024 03:19:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-palo-alto-ngfw-prevent-unknow-cves/m-p/572473#M2405</guid>
      <dc:creator>SopheaHem</dc:creator>
      <dc:date>2024-01-10T03:19:44Z</dc:date>
    </item>
    <item>
      <title>Re: How Palo Alto NGFW Prevent Unknow CVEs?</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-palo-alto-ngfw-prevent-unknow-cves/m-p/575920#M2578</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/223298"&gt;@SopheaHem&lt;/a&gt;&amp;nbsp;- CVE IDs are centrally allocated, but it is inevitable that there is some duplication and overlap among the 220,000+ CVE &lt;A href="https://www.cve.org/" target="_self"&gt;records&lt;/A&gt; currently available. Sometimes an "unknown" one (to us) might actually be known to us as a different CVE ID.&amp;nbsp; A similar story would apply to any other security vendor.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bear in mind that CVE IDs can be allocated before any information is known about the specifics of the threat, and without threat specifics we would need to rely on other heuristics to identify a novel threat.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Like any good answer, the best answer I can give here is, "it depends."&amp;nbsp; No security vendor, be it Palo Alto Networks or anyone else, can&amp;nbsp;&lt;EM&gt;guarantee&lt;/EM&gt; anything about detecting and eliminating unknown CVEs, and you should be highly suspicious of claims to the contrary.&amp;nbsp; If they're unknown, or highly novel, there is always a risk that they could slip past unnoticed.&amp;nbsp; This is where tools like App-ID, URL Filtering, and WildFire, and having a sensible but strict security policy that utilises them, really come into their own.&amp;nbsp; &amp;nbsp;Defence in depth is an excellent approach as well: don't just rely on App-ID, for example, but instead use all of the tools at your disposal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Moreover, not every CVE is network-centric, which makes it hard for a next-generation firewall to have any impact, positive or negative, on the detection of those.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What we can also do is use tools like Advanced WildFire to detect and eliminate threats, including novel one threats, as quickly as possible using a range of analysis tools and techniques.&amp;nbsp; This can also include threats that don't (yet) have a CVE identified.&amp;nbsp; This relies on the knowledge gained from multiple sources including other customer environments using Advanced WildFire, which means that on average, any novel threat will have been seen at least once, and hopefully identified as such, before it encroaches on your environment.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Feb 2024 23:02:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/how-palo-alto-ngfw-prevent-unknow-cves/m-p/575920#M2578</guid>
      <dc:creator>iarobertson</dc:creator>
      <dc:date>2024-02-04T23:02:59Z</dc:date>
    </item>
  </channel>
</rss>

