FalconCrowstrikeCustomIOC Responder v2 #1188
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
As the Swagger API create_ioc & IOCs endpoint are now deprecated (issue #904), the previous Falcon responser does not work anymore. But I’ve been able to rebuilt it (based on ag-michael previous work) using the new IOC.indicator_create() method from falconpy instead. Here are some modifications I’ve added to this responder:
Choice of the severity level when IOCs are ingested by Falcon CustomIOC:
Choice of how the IOCs are ingested by Falcon CustomIOC:
Choice of the tag added to TheHive (Default: « Falcon:Custom IOC Uploaded »)
Choice of the tag added to Falcon (Default: « Cortex Incident - FalconCustomIOC »)
Choice of the expiration date by IOC types (in days) - 30 days by default: