MISP – Dashboard For A Real Time Overview Of Threat Intelligence From MISP Instances

MISP is a dashboard showing live data and statistics from the ZMQ feeds of one or more MISP instances. The dashboard can be used as a real-time situational awareness tool to gather threat intelligence information.

The misp-dashboard includes a gamification tool to show the contributions of each organization and how they are ranked over time.

The dashboard can be used for SOCs (Security Operation Centers), security teams or during cyber exercises to keep track of what is being processed on your various MISP instances.

Also Read – OpenSK : Open-Source Implementation For Security Keys


Live Dashboard

  • Possibility to subscribe to multiple ZMQ feeds from different MISP instances
  • Shows immediate contributions made by organisations
  • Displays live resolvable posted geo-locations

Geolocalisation Dashboard

  • Provides historical geolocalised information to support security teams, CSIRTs or SOCs in finding threats within their constituency
  • Possibility to get geospatial information from specific regions

Contributors Dashboard


  • The monthly rank of all organisations
  • The last organisation that contributed (dynamic updates)
  • The contribution level of all organisations
  • Each category of contributions per organisation
  • The current ranking of the selected organisation (dynamic updates)


  • Gamification of the platform:
    • Two different levels of ranking with unique icons
    • Exclusive obtainable badges for source code contributors and donator

Users Dashboard

  • Shows when and how the platform is used:
    • Login punchcard and contributions over time
    • Contribution vs login

Trendings Dashboard

  • Provides real time information to support security teams, CSIRTs or SOC showing current threats and activity
    • Shows most active events, categories and tags
    • Shows sightings and discussion overtime


Before installing, consider that the only supported system are open source Unix-like operating system such as Linux and others.

  • Launch ./install_dependencies.sh from the MISP-Dashboard directory (idempotent-ish)
  • Update the configuration file config.cfg so that it matches your system
    • Fields that you may change:
      • RedisGlobal -> host
      • RedisGlobal -> port
      • RedisGlobal -> zmq_url
      • RedisGlobal -> misp_web_url
      • RedisMap -> pathMaxMindDB

Updating By Pulling

  • Re-launch ./install_dependencies.sh to fetch new required dependencies
  • Re-update your configuration file config.cfg by comparing eventual changes in config.cfg.default

virtualenv -p python3 DASHENV
Already using interpreter /usr/bin/python3
Using base prefix ‘/usr’
New python executable in /home/steve/code/misp-dashboard/DASHENV/bin/python3
Traceback (most recent call last):
File “/usr/bin/virtualenv”, line 9, in
load_entry_point(‘virtualenv==15.0.1’, ‘console_scripts’, ‘virtualenv’)()
File “/usr/lib/python3/dist-packages/virtualenv.py”, line 719, in main
File “/usr/lib/python3/dist-packages/virtualenv.py”, line 942, in create_environment site_packages=site_packages, clear=clear, symlink=symlink))
File “/usr/lib/python3/dist-packages/virtualenv.py”, line 1261, in install_python shutil.copyfile(executable, py_executable)
File “/usr/lib/python3.5/shutil.py”, line 115, in copyfile
with open(dst, ‘wb’) as fdst:
OSError: [Errno 26] Text file busy: ‘/home/steve/code/misp-dashboard/DASHENV/bin/python3’

  • Restart the System: ./start_all.sh OR ./start_zmq.sh and ./server.py &

Starting the System

  • Be sure to have a running redis server
    • e.g. redis-server --port 6250
  • Activate your virtualenv . ./DASHENV/bin/activate
  • Listen to the MISP feed by starting the zmq_subscriber ./zmq_subscriber.py &
  • Start the dispatcher to process received messages ./zmq_dispatcher.py &
  • Start the Flask server ./server.py &
  • Access the interface at http://localhost:8001/

Alternatively, you can run the start_all.sh script to run the commands described above.


Debug is fun and gives you more details on what is going on when things fail. Bare in mind running Flask in debug is NOT suitable for production, it will drop you to a Python shell if enabled, to do further digging.

Just before running ./server.py do:

export FLASK_DEBUG=1
export FLASK_APP=server.py
flask run –host= –port=8001 # <- Be careful here, this exposes it on ALL ip addresses. Ideally if run locally –host=

OR, just toggle the debug flag in start_all.sh or config.cfg.

Restart from scratch

To restart from scratch and empty all data from your dashboard you can use the dedicated cleaning script clean.py

Clean data stored in the redis server specified in the configuration file

Optional Arguments:
-h, –help show this help message and exit
-b, –brutal Perfom a FLUSHALL on the redis database. If not set, will use a soft method to delete only keys used by MISP-Dashboard.

Notes about ZMQ

The misp-dashboard being stateless in regards to MISP, it can only process data that it received. Meaning that if your MISP is not publishing all notifications to its ZMQ, the misp-dashboard will not have them.

The most revelant example could be the user login punchcard. If your MISP doesn’t have the option Plugin.ZeroMQ_audit_notifications_enable set to true, the punchcard will be empty.

Dashboard not showing results – No module named zmq

When the misp-dashboard does not show results then first check if the zmq module within MISP is properly installed.

In Administration, Plugin Settings, ZeroMQ check that Plugin.ZeroMQ_enable is set to True.

Publish a test event from MISP to ZMQ via Event Actions, Publish event to ZMQ.

Verify the logfiles


If there’s an error ModuleNotFoundError: No module named ‘zmq’ then install pyzmq.

$SUDO_WWW ${PATH_TO_MISP}/venv/bin/pip install pyzmq

zmq_subscriber options

A zmq subscriber. It subscribe to a ZMQ then redispatch it to the MISP-dashboard

optional arguments:
-h, –help show this help message and exit
n ZMQNAME, –name ZMQNAME The ZMQ feed name
-u ZMQURL, –url ZMQURL The URL to connect to