Import new Event with specific EventID
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 491
- Forks
- 290
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 3
Description
The EventId can be used in an API call or within PyMISP utility to delete or update a specific event.
Is there a MISP configuration to enable so when adding a new event, a specific EventId can be used?
{
"Event": {
"id": "222222",
"orgc_id": "2",
"org_id": "1",
"date": "2022-09-22",
"threat_level_id": "3",
"info": "test event",
"published": false,
"attribute_count": "0",
"analysis": "2",
"timestamp": "1663876708",
"distribution": "0",
"proposal_email_lock": false,
"locked": true,
"publish_timestamp": "0",
"sharing_group_id": "0",
"disable_correlation": false,
"extends_uuid": "",
"protected": null,
}
}
rather than MISP autogenerating the next available event number.
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 reviewing PyMISP's event-creation API and the MISP configuration documentation for event ID handling. Confirm whether importing an event with a caller-supplied EventId is supported, and document the required configuration or the scope of any needed feature work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100