-
### Work environment
| Questions | Answers
|---------------------------|--------------------
| Type of issue | Support
| OS version (server) | Ubuntu
| OS vers…
mik5z updated
4 years ago
-
misp use a lot of memory when you use search on event controller.
same issue when we search with curl
### Work environment
| Questions | Answers
|---------------------------|…
-
#5245 # Work environment
| Questions | Answers
|---------------------------|--------------------
| Type of issue | Support
| OS version (server) | Ubuntu 18.04.…
Gudmo updated
4 years ago
-
There are times that we have a need to merge many events into one. One case is related to https://github.com/MISP/MISP/issues/5544 where we needed to change default feeds from daily events to a fi…
-
Had two nearly identical searches (one for domains, and one for IPs) running to create sighting alerts in MISP, however the IP search was failing to actually create sightings.
The only difference i…
-
It would be wonderful to have an option to set an expiration date for an event at the time that it is created. We get weekly spreadsheets of threat IoCs that we organize using MISP and feed into our s…
-
Hello,
I would like to request a little feature in **PyMISP search** method.
First I will try to describe the problem. We are currently running our own IP reputation database, which should now p…
-
I can see a number of methods available here: https://github.com/MISP/PyMISP/blob/master/pymisp/api.py#L1122
but all appear to add a sighting to an attribute, I can't find any obvious way in PyMISP…
-
Not sure it is a bug tho (the key to pass to the controller is called `org_id`)
-
2.4.114
I've noticed that tagging attributes in an event with a large amount of attributes with most of them having correlation enabled that each call to `ExpandedPyMISP.tag` can take upwards of a …