TheHive-Project / TheHive-Project/Cortex
Create an Analyzer Store
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 264
- PR merge metrics
- No merged PRs in 30d
Description
Request Type
Feature Request
Work Environment
N/A
Problem Description
Cortex as of 1.x doesn't have a (simple) process for:
- Getting notifications when a new version of an existing analyzer is available or a new analyzer has been published
- Updating existing public analyzers to the latest versions (or select a specific version and lock updating)
- Installing new public analyzers
Moreover, Cortex does not currently allow teams to:
- Add analyzers from private sources
- Package analyzers in a simple way and share them easily with public or private communities (without having to use pull requests for public analyzers)
- Specify the license of their contributed analyzers and monetize them if they want to
Possible Solutions
Create an analyzer store much like a mobile app store that allow teams to:
- Browse through the existing analyzers, see their license, author(s), report samples, required input...
- Subscribe to different sources (public, private communities) of analyzers to install them, get notifications about new versions, and lock their update process to stay at a given version if they so please
- Install analyzers and configure them on-the-fly without having to restart Cortex
- Package and push new analyzers choosing where to share them (public, single or multiple private communities)
- Buy analyzers
- Obtain support when applicable
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 describes a broad analyzer-store feature but names no files, tests, or entry points. Begin by locating Cortex's analyzer installation, configuration, and API components, then determine how browsing, versioning, private sources, packaging, licensing, payments, and runtime installation should fit together. Done means an agreed design and an implemented store workflow covering the requested capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100