The heart of DDoSDB is a Django Webapp. MongoDB is used for storing the fingerprints, with Mongo Express you can inspect the fingerprints database and backup/restore it if necessary. Nginx is used as webserver front-end (except for the development setup).

The raw .json files and the pcap samples are stored locally on disk.

If you don't know what Django is, but would like to understand how DDoSDB is setup, then please checkout the excellent documentation and familiarise yourself a bit with Django by following the tutorial.

You can use two approaches to running a (local) DDoSDB repository:

• Run a fully dockerized version, this is the preferred option.
• Work with Django directly in a development setup.

For deployment you can use the dockerized version and add Let's Encrypt cerificates using the script provided.

There is also a DDosDB-in-a-box setup. Essentially this is nothing more than a Linux VM with the dockerized version installed; so if you can docker & docker-compose on your system then running the dockerized version is the preferred option.

The DDoS clearing house can be used by any community of organizations that wishes to collaboratively defend themselves against DDoS attacks. The development of the clearing house was partly funded by the European Union’s Horizon 2020 Research and Innovation program under Grant Agreement No 830927. It will be used by the Dutch National Anti-DDoS Coalition, a self-funded public-private initiative to collaboratively protect Dutch organizations and the wider Internet community from DDoS attacks. Websites: https://www.concordia-h2020.eu/ and https://www.nomoreddos.org/en/.