TheHive-Project / TheHive-Project/Cortex
Additional Filters to Allow/Prevent Observable Analysis
@To-om is already working on this.
Since Jun 7, 2018.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Request Type
Feature Request
Work Environment
| Question | Answer |
|---|---|
| Cortex version / git hash | 2.0.4 |
Problem Description
With the recent addition of the Unshortenlink analyzer, the need for additional filters to allow or prevent certain observable analysis in complement of the TLP arose.
Indeed, using the Unshortenlink analyzer without extra caution might lead to unexpected consequences. For example, if the URL an analyst is seeking to unshorten is an attacker-controlled one, they may end up leaving undesired traces in the threat actor's infrastructure logs. The TLP values Cortex allows an orgAdmin to configure to prevent the use of an analyzer if the TLP associated with an observable is above the authorized level won't be of much help since Unshortenlink have to access the shortened URL.
Possible Solutions
It would be nice if Cortex supports additional configuration items that can be used by analyzers to allow or prevent observable analysis if:
- they begin with a certain pattern (
begin with) - they end with a certain pattern (
end with) - they contain a certain pattern (
contain) - they have a certain value (
is)
By default the configuration item could be positioned to .*. It should also be possible to import a list of entries (whitelist / blacklist) from a text file for example.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.