- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-24-2024 06:40 AM
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.
Regards,
Thinh Phan
02-26-2024 07:13 AM
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.
02-26-2024 07:13 AM
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.
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!