<?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: Cortex XSOAR - Best Practice Optimize Threat Intelligence Management (TIM) in Cortex XSOAR Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/cortex-xsoar-best-practice-optimize-threat-intelligence/m-p/1233027#M4094</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1397286955"&gt;@A.Faruq&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;I would recommend you create a series of delete and exclusions for private IP ranges using their subnet range definition in addition you can exclude organizational domains as these may offer little benefit as an indicator. I would recommend reading the recommendation for this from the Palo Docs.&lt;/P&gt;
&lt;P&gt;In regards to managing the premium Threat Intel integration, you can work out how to limit it for only suitable indicators of a specific types.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Delete-and-exclude-indicators" target="_blank" rel="noopener"&gt;Link to Docs&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this helps you to understand how to manage this correctly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;MichaelSysec&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jul 2025 12:01:10 GMT</pubDate>
    <dc:creator>michaelsysec242</dc:creator>
    <dc:date>2025-07-02T12:01:10Z</dc:date>
    <item>
      <title>Cortex XSOAR - Best Practice Optimize Threat Intelligence Management (TIM)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/cortex-xsoar-best-practice-optimize-threat-intelligence/m-p/1232639#M4084</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I read the documentation about Threat Intelligence Management (TIM) from this article before &lt;A href="https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/what-is-everyone-doing-with-their-tim-license/td-p/548211?attachment-id=12602" target="_blank"&gt;https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/what-is-everyone-doing-with-their-tim-license/td-p/548211?attachment-id=12602&lt;/A&gt;. However, that document is not updated, and there is no mention of best practices for managing TIM efficiently.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a case also when integrated the Cortex XSOAR with Threatfusion from SOCRadar and when I checked the integration. There are so many false positive detections from Threatfusion that waste the remaining credit checks by checking unnecessary things like internal ip or naming field below.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AFaruq_0-1750923154291.png" style="width: 984px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/68198i32E2A007BB03AB76/image-dimensions/984x209?v=v2" width="984" height="209" role="button" title="AFaruq_0-1750923154291.png" alt="AFaruq_0-1750923154291.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Where is the menu that I can optimize TIM like manage allowlist (Exception), or show what command was used before to manage and keep credits from Premium Threat Intelligence like Threatfusion.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jun 2025 07:33:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/cortex-xsoar-best-practice-optimize-threat-intelligence/m-p/1232639#M4084</guid>
      <dc:creator>A.Faruq</dc:creator>
      <dc:date>2025-06-26T07:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: Cortex XSOAR - Best Practice Optimize Threat Intelligence Management (TIM)</title>
      <link>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/cortex-xsoar-best-practice-optimize-threat-intelligence/m-p/1233027#M4094</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1397286955"&gt;@A.Faruq&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;I would recommend you create a series of delete and exclusions for private IP ranges using their subnet range definition in addition you can exclude organizational domains as these may offer little benefit as an indicator. I would recommend reading the recommendation for this from the Palo Docs.&lt;/P&gt;
&lt;P&gt;In regards to managing the premium Threat Intel integration, you can work out how to limit it for only suitable indicators of a specific types.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs-cortex.paloaltonetworks.com/r/Cortex-XSOAR/8/Cortex-XSOAR-Cloud-Documentation/Delete-and-exclude-indicators" target="_blank" rel="noopener"&gt;Link to Docs&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope this helps you to understand how to manage this correctly.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Many thanks,&lt;/P&gt;
&lt;P&gt;MichaelSysec&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 12:01:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/cortex-xsoar-best-practice-optimize-threat-intelligence/m-p/1233027#M4094</guid>
      <dc:creator>michaelsysec242</dc:creator>
      <dc:date>2025-07-02T12:01:10Z</dc:date>
    </item>
  </channel>
</rss>

