MISP / MISP/misp-sighting-server
Consider adding organisations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Was looking into using this as a plug-in replacement in the future for the sighting system, it indeed looks very good and the performance is insanely fast.
However, in order to fully replicate what we have currently we need to be able to replicate the following:
- value based sighting
- id/uuid sighting
- source
- types:
- sighting
- FP (added just now)
- expiration (to be added, but tricky due to 1/org limitation - maybe this shouldn't go in here?)
- timestamp
- org_id/org_uuid
Once we have all of them covered we can start thinking about phasing out the current implementation (though sharing across instances will still be tricky).
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 identifies missing id/UUID sightings and org_id/org_uuid support, but names no files, tests, or entry points. Start by tracing how sightings are currently stored and looked up, then define the organization-scoping requirements; done means the unchecked organization and identifier capabilities are supported without breaking the existing sighting types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100