<?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: Ransomware isolation automation in Cortex XDR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/ransomware-isolation-automation/m-p/595096#M7079</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/112301"&gt;@CraigV123&lt;/a&gt;, thanks for reaching us using the Live Community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Automation Rules are the way to isolate the endpoints on a critical event like this. You need to create the rule as detailed as possible, like Severity = High or Critical &amp;amp; Category contains Malware + you can add the Mitre Tactics and Techniques usually used for this kind of malware.&lt;/P&gt;
&lt;P&gt;Of course the best option is to have an alert about this kind of malware and create the filter using the current findings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this post answers your question, please mark it as the solution.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2024 12:56:15 GMT</pubDate>
    <dc:creator>jmazzeo</dc:creator>
    <dc:date>2024-08-16T12:56:15Z</dc:date>
    <item>
      <title>Ransomware isolation automation</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/ransomware-isolation-automation/m-p/595045#M7076</link>
      <description>&lt;P&gt;Hi everyone.&lt;/P&gt;
&lt;P&gt;Have XDR Pro. Looking for an "easy" way to automatically isolate a device when ransomware-like behaviors are detected. Looking through the automation configurations, it doesn't appear to be that easy. I obviously don't want to be isolating a ton of devices on false positives either.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any suggestions from the community?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2024 20:13:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/ransomware-isolation-automation/m-p/595045#M7076</guid>
      <dc:creator>CraigV123</dc:creator>
      <dc:date>2024-08-15T20:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: Ransomware isolation automation</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/ransomware-isolation-automation/m-p/595096#M7079</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/112301"&gt;@CraigV123&lt;/a&gt;, thanks for reaching us using the Live Community.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The Automation Rules are the way to isolate the endpoints on a critical event like this. You need to create the rule as detailed as possible, like Severity = High or Critical &amp;amp; Category contains Malware + you can add the Mitre Tactics and Techniques usually used for this kind of malware.&lt;/P&gt;
&lt;P&gt;Of course the best option is to have an alert about this kind of malware and create the filter using the current findings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If this post answers your question, please mark it as the solution.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2024 12:56:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xdr-discussions/ransomware-isolation-automation/m-p/595096#M7079</guid>
      <dc:creator>jmazzeo</dc:creator>
      <dc:date>2024-08-16T12:56:15Z</dc:date>
    </item>
  </channel>
</rss>

