<?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 Whitelist IP from XDR anlysis in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/whitelist-ip-from-xdr-anlysis/m-p/475804#M1750</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would ike to know if it is possible to create a list of IP's that will not be analysed by any of the XDR protection modules.We have a vulnerability scanning tool that uses all sorts of scripts to perform its tasks, At the moment, most of these scripts are blocked by Cortex because they look suspicious, which is true but not wanted in this situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to create some sort of whitelist that prevents XDR from analyzing / inspecting / blocking traffic from these IP's. Is such a thing possible?&lt;/P&gt;</description>
    <pubDate>Fri, 25 Mar 2022 15:44:34 GMT</pubDate>
    <dc:creator>Kevin_Robers</dc:creator>
    <dc:date>2022-03-25T15:44:34Z</dc:date>
    <item>
      <title>Whitelist IP from XDR anlysis</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/whitelist-ip-from-xdr-anlysis/m-p/475804#M1750</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would ike to know if it is possible to create a list of IP's that will not be analysed by any of the XDR protection modules.We have a vulnerability scanning tool that uses all sorts of scripts to perform its tasks, At the moment, most of these scripts are blocked by Cortex because they look suspicious, which is true but not wanted in this situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to create some sort of whitelist that prevents XDR from analyzing / inspecting / blocking traffic from these IP's. Is such a thing possible?&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 15:44:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/whitelist-ip-from-xdr-anlysis/m-p/475804#M1750</guid>
      <dc:creator>Kevin_Robers</dc:creator>
      <dc:date>2022-03-25T15:44:34Z</dc:date>
    </item>
    <item>
      <title>Re: Whitelist IP from XDR anlysis</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/whitelist-ip-from-xdr-anlysis/m-p/475821#M1751</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/213969"&gt;@Kevin_Robers&lt;/a&gt;, We want to maintain security of environment while reducing operational impact. &lt;SPAN&gt;I believe obtaining some additional context on the alert criteria / scope will assist in determining the most effective path forward.&amp;nbsp; The following information will help to guide you on determining next steps:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Have you completed vulnerability scans in your environment in the past, or this the first occurrence? If you have complete vulnerability scans without any operational impact, then this may be an opportunity to enhance the alert efficacy with content&lt;/SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/endpoint-security/about-content-updates.html" target="_blank" rel="noopener"&gt;&lt;SPAN&gt; updates&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; on your Cortex XDR agents. You will need to &lt;/SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/investigation-and-response/investigate-endpoints/retrieve-support-logs-from-an-endpoint" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;retrieve the endpoint support file&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; from an endpoint in scope, and raise a support ticket for additional analysis.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Do the alerts in questions have a "detection" alert action? If so, then there should not be any change in the behavior of the file / process execution on the endpoint.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Do the alerts in question have a “prevention” alert action?&amp;nbsp; If so, then you may consider adding the process / file path to an &lt;/SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/investigation-and-response/investigate-endpoint-alerts/manage-alerts.html" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;allow list&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; / &lt;/SPAN&gt;&lt;A href="https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/endpoint-security/exceptions-security-profiles/add-exceptions-profile.html" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;alert exception&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN&gt; to continue operations.&amp;nbsp;&lt;/SPAN&gt;&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;Similar to the first bullet, if the behavior in the alert originated from your vulnerability scanner and it is not a threat, then you can coordinate with support on the next steps (&lt;EM&gt;E.g. content update&lt;/EM&gt;). &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/UL&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>Fri, 25 Mar 2022 16:48:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/whitelist-ip-from-xdr-anlysis/m-p/475821#M1751</guid>
      <dc:creator>WSeldenIII</dc:creator>
      <dc:date>2022-03-25T16:48:31Z</dc:date>
    </item>
  </channel>
</rss>

