TheHive-Project / TheHive-Project/Cortex
Add a min_tlp value in Cortex
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Add a min_tlp value in Cortex alongside max_tlp. to control what the minimum tlp level is for an analyzer to run.
Request Type
Feature Request
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | Ubuntu |
| OS version (client) | 10 |
| Cortex version / git hash | 2.1.3-1 |
| Package Type | Binary |
| Browser type & version | N/A |
Problem Description
We have internal Cortex instances and external Cortex instances. When we add external observables we want those to be sent to the external Cortex instance for analysis by 3rd party threat Intel providers. When we add an internal IP we want that to be sent to the internal Cortex instance and not to external.
We've set the TLP values on the observables as per the guidance. An external IP is set to tlp:green. An internal IP seen is set to tlp:red. When we set the SecurityCenter max_tlp to red, external IP's get accepted by the analyzer. When we set the max_tlp on the analyzer to white, external IP's aren't accepted but also internal IP's aren't accepted either.
What we want to do is set the min_tlp of the SecurityCenter analyzer (and other internal analyzers too) to have a min_tlp:red so that it will only accept observables with a tlp:red (essentially internal observables we don't want to share).
Steps to Reproduce
Enable SecurityCenter Analyzer.
Create a case, and an an external IP as an observable. Set the TLP to red as you don't want to share this externally.
Run the SecurityCenter analyzer. It attempts to scan the external target.
Possible Solutions
Create a min_tlp value for analyzers get the analyzers to respect that.
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.
Research direction
Start by tracing how the SecurityCenter analyzer and other analyzers read and enforce max_tlp during observable analysis. Compare the reported external and internal observable cases, then identify the analyzer configuration and execution points involved; done means the requested minimum TLP behavior is defined and verified for those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100