Hello everyone!
I have a few doubts on how events are handled across misp instances and Orgs. As I still haven't complete domain of the code and my curiosity is killing me, I'm coming here to ask help =]

1. In the situation a site admin edit an event from another org and publish it. What exactly will happen with that information? Supposing it has a distribution level as "All communities".
   Wil

Bug / Feature Request

Work Environment

Problem Description

There are no longer any default dashboards

Possible Solutions

Add the default da

The Table of Contents does not show all the sections in the Install Guide, and the First Start section needs to be updated starting with the title and correcting other verbiage issues within the section text.

Create an interface within the plugin to add notes, tags and other manually captured items analysts might want to keep track of, and have the notes displayed in the popups as well.

Any feedback or ideas for this are welcome.

IMHO it's good to remove examples which use deprecated methods.
Those examples are obstacles to learn how to use PyMISP in the latest manner.

When following the current install instructions:

sudo apt-get install python3-dev python3-pip libpq5 libjpeg-dev
cd /usr/local/src/
sudo git clone https://github.com/MISP/misp-modules.git
cd misp-modules
sudo pip3 install -I -r REQUIREMENTS
sudo pip3 install -I .
sudo vi /etc/rc.local, add this line: `sudo -u www-data misp-modules -s &`
misp-modules #to start the modules

the

Describe the solution you'd like
Documentation that lists the different CLI commands that can be issued via cake.
(can work on this myself; putting this as a reminder)

cake
cake CakeResque.CakeResque

Describe alternatives you've considered
Trial and error.

Because of this line:
https://github.com/MISP/misp-docker/blob/master/web/run.sh#L137

First boot will run everytime.

Is this intended?

If it's not, could cook up a PR that simply checks for the presence of the .gnupg folder to run firstboot.

At the moment text in the STIX Indicator:Description field is lost. It would be nice to convert this to an attribute comment in MISP.

The same is true for the stix:Description field which could be converted to Catergory=other Type=comment in MISP.

file
microblog post
domain-ip
ip-port
coin-address
virustotal-report
paste
person
pe
pe-section
registry-key