You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature description
Trying to create a reporting responder using the following reporter as a base. I want the responder to fetch all analyzer job results for each observable in case. The purpose is to have all information included in the report(for a case) so the analyst can edit/remove what is required or not in the final report. I've checked the Cortex4py documentation and you can get (ex: per name or id)the analyzer and jobs details but there is no way to narrow it down to a specific case(using the case ID for example). Is it something that is feasible? If not, I would like to request that feature.
Describe the solution you'd like
Would like to be able to programatically get all analyzer job results for each observable in a case.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
StiveN99
changed the title
[FR] Analyzer jobs per case
[FR] Get analyser jobs per case
Nov 24, 2021
Feature description
Trying to create a reporting responder using the following reporter as a base. I want the responder to fetch all analyzer job results for each observable in case. The purpose is to have all information included in the report(for a case) so the analyst can edit/remove what is required or not in the final report. I've checked the Cortex4py documentation and you can get (ex: per name or id)the analyzer and jobs details but there is no way to narrow it down to a specific case(using the case ID for example). Is it something that is feasible? If not, I would like to request that feature.
Describe the solution you'd like
Would like to be able to programatically get all analyzer job results for each observable in a case.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: