Christophe Vandeplas

Actually, the tag_editor role should not be able to edit/delete tags. (otherwise someone external could rename "tlp:amber" to "tlp:white" for example). The role allows adding tags and should allow tags...

@3c7 as explained [here](https://github.com/MISP/MISP/issues/2917#issuecomment-558543558) it is a design decision for now to only allow admins to rename / edit tags. The impact of allowing that permission is much bigger than...

Thank you @3c7 . For now this PR cannot be merged, as explained in #2917 allowing tags to be renamed is not a good idea. However some other features could...

Are you sure your logstash is configured and running? try a: ``` sudo netstat -nalp | fgrep "1800" ``` That should return lines stating that java is listening on these...

Hi there, What you are experiencing is the effect of tokenization. If you try to index "Hello world" then Elasticsearch will explode that based on pre-defined tokens (spaces, dots, comma,..)...

Hi, I'm unfortunately not maintaining this repository anymore. However all corrections and improvements are welcome.

Following our call here was our current approach: - I'll merge again everything to generic clusters (like before, so one for `intrusion-set`) and will include the `enterprise-attack` , `pre-attack`, `mobile-attack`...

TODO: - [x] galaxy changes to bring it to the new version - by @cvandeplas https://github.com/MISP/misp-galaxy/pull/320 - [ ] soft delete of tags with all the crap around it -...

I agree we should not change `mitre-tool.json`. On the other hand renaming `tool.json` with a prefix would also imply renaming all the other ones like `threat-actor.json`, `botnet.json` to follow the...

The ATT&CK version was updated some time ago. It should be up to date to the latest MITRE version. (v9) @nyx0 : I'm not sure to understand. You would want...