Cortex XSOAR - Best Practice Optimize Threat Intelligence Management (TIM)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cortex XSOAR - Best Practice Optimize Threat Intelligence Management (TIM)

L0 Member

Dear Community,

 

I read the documentation about Threat Intelligence Management (TIM) from this article before https://live.paloaltonetworks.com/t5/cortex-xsoar-discussions/what-is-everyone-doing-with-their-tim-.... However, that document is not updated, and there is no mention of best practices for managing TIM efficiently.

 

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.

AFaruq_0-1750923154291.png

 

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.

 

Thanks

 

1 accepted solution

Accepted Solutions

L4 Transporter

Hello @A.Faruq ,

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.

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.

Link to Docs 

I hope this helps you to understand how to manage this correctly. 

Many thanks,

MichaelSysec

 

PCSAE

View solution in original post

1 REPLY 1

L4 Transporter

Hello @A.Faruq ,

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.

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.

Link to Docs 

I hope this helps you to understand how to manage this correctly. 

Many thanks,

MichaelSysec

 

PCSAE
  • 1 accepted solution
  • 268 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!