PyMISP get object template from server and drop local copies from package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 491
- Forks
- 290
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Description
Inspired by #658 this requests a new feature: the PyMISP client MISPObject class __init__() method should query the MISP server for the object template definition (e.g., "my-internal-bad-event") instead of requiring & reading a definition.json file locally in its site-packages area. I see at least two advantages:
- Clients could use new custom objects immediately after server administrators upload new custom object definitions.
- Eliminating redundancy of definition files in the PyMISP package and the server will reduce maintenance effort.
To ensure performance does not suffer too much, the PyMISP client should cache object definitions.
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 at the PyMISP client’s MISPObject.init() method and trace how it currently reads definition.json from the package. Check the server API path for retrieving object templates and determine how definitions can be cached; done means custom server-side objects work without local definition files while avoiding repeated requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100