ThreatConnect's reputation commands does not return correct results when no indicator found

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

ThreatConnect's reputation commands does not return correct results when no indicator found

L0 Member

Hi all,

 

I am not sure if this is a bug in ThreatConnect pack since its reputation commands does not return correct results when it could not find the indicator. The correct behavior should be https://xsoar.pan.dev/docs/integrations/dbot#unknown. Since it does not return correct results in those cases, we have no idea if the command has ever run. In other words, it never returns `unknown` score for indicators.

TPhan_0-1708785626717.png

Regards,

Thinh Phan

1 accepted solution

Accepted Solutions

L1 Bithead

Hello,

 

Does this occur with several different IPs as well? I've reviewed the commands code, and it looks like the output from ThreatConnect is being sent directly as output to XSOAR. Your execution returned back an empty JSON object because that is what ThreatConnect returned back. XSOAR does not look at the text submitted, as input to the command, as the indicator to be created when the command finishes. It reviews the output from the command, and parses any indicators found from said output.

I believe this type of output is expected behavior. XSOAR, since it doesn't take into account the string provided by the ip argument, as a valid indicator, reviews the output of the command, and creates/sets reputations based on the findings of the service. You would have seen the unknown reputation appear if ThreatConnect returned back a finding for the given ip, and a reputation was not found for it.

View solution in original post

1 REPLY 1

L1 Bithead

Hello,

 

Does this occur with several different IPs as well? I've reviewed the commands code, and it looks like the output from ThreatConnect is being sent directly as output to XSOAR. Your execution returned back an empty JSON object because that is what ThreatConnect returned back. XSOAR does not look at the text submitted, as input to the command, as the indicator to be created when the command finishes. It reviews the output from the command, and parses any indicators found from said output.

I believe this type of output is expected behavior. XSOAR, since it doesn't take into account the string provided by the ip argument, as a valid indicator, reviews the output of the command, and creates/sets reputations based on the findings of the service. You would have seen the unknown reputation appear if ThreatConnect returned back a finding for the given ip, and a reputation was not found for it.

  • 1 accepted solution
  • 824 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!