TheHive-Project / TheHive-Project/Cortex
Intermediate report for long time running analyzers
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Intermediate report for long time running analyzers
Request Type
Feature Request
Work Environment
| Question | Answer |
|---|---|
| OS version (server) | RedHat, ... |
| Cortex version / git hash | 3.1.2 |
| Package Type | Docker |
Problem Description
Some analyzers can be long to run (ex: sandbox analysis).
It can be usefull for an analyst to have some intermediate short-report indicating the status of a task.
Example : Run a sandbox analysis, get a preliminary short-report to indicate status changes (ex: Pending, Running, Completed) or to report the virtual machine name where the analysis is running.
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
The issue names no files, tests, or entry points. Start by tracing the analyzer task flow and how sandbox analysis exposes status, using the requested Pending, Running, and Completed states as the reference. Done would provide an intermediate short report, including status changes and, where available, the virtual machine name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100