misp-container-frontend VS MISP

In this version, we kept the implementation of Nginx and PHP-FPM from Coolacid’s container and removed the workers and cron jobs from it. Nginx and PHP-FPM are started by Supervisor and the configuration of the application is mounted as static files (ConfigMap, Secret) to the container instead of dynamically set.

MISP is an open-source solution to streamline the acquisition, retention, distribution, and collaborative exchange of critical cybersecurity indicators and threats. Timely-Lychee-5204 considers it "a threat intelligence platform for gathering, sharing, storing, and correlating indicators of compromise."

MISP https://www.misp-project.org/

It sounds like you want to jump into game development before learning how to write "Hello, world!". Try using any of the open source tools that already do this and sign up for some "free" threat intel tools and learn the lay of the land. https://www.misp-project.org/ https://github.com/OpenCTI-Platform/opencti https://iplists.firehol.org/ https://www.greynoise.io/

Yes but … the frontend/ui is still trying to check the health of each process by checking in /proc/{PID} like in previous and shows that the process maybe start but it couldn’t check if it’s alive or not. An issue was created and we’re waiting for the patch to be integrated in a future version.

You could use MISP to collect events and IOCs about threat actors and map their activity using Mitre ATTAC&K. Once you start building a knowledge base you can mainly focus on Threat actors who are interested in your sector.

Is it possible to feed MISP with CrowdSec’s IOC lists?

Also forgot to include this, for the blog post - yeah it should go up there soon. Until then it's to be found here: https://github.com/MISP/MISP/releases/tag/v2.4.160