How v1d1an/s1em works
Project type and purpose
• This is a full-stack, containerized cybersecurity platform (S1EM) that bundles open-source SIEM, SIRP, threat-intel, full-packet capture, and SOAR tooling.
• It uses Docker Compose (single vs. multi-node) to deploy Elasticsearch, Beats, Logstash, Kibana, security agents (Suricata, Zeek, Auditbeat, Filebeat, Metricbeat, Heartbeat), triage/response tools (TheHive, Cortex, MISP, OpenCTI), workflow automation (n8n), packet capture (Arkime), EDR (Velociraptor, Zircolite), threat-intel (Spiderfoot), alerting (Elastalert), plus supporting services (Traefik, Redis, RabbitMQ, MySQL/Postgres, Syslog-ng).
File structure
• Top-level scripts (00_*.sh, 01_deploy.sh, etc.) orchestrate instance creation, deployment, and cleanup.
• Docker Compose manifests: docker-compose-single.yml and docker-compose-multi.yml define service sets for single-node vs. cluster.
• Directories grouped by function:
• beats/ (filebeat, metricbeat, auditbeat, heartbeat)
• logstash/ (pipelines, templates, configs)
• arkime/, suricata/, zeek/ for network capture/IDS
• misp/, cortex/, thehive/, n8n/ for threat-intel & SOAR
• redis/, postgres/, mysql/ for state & caching
• traefik/ for ingress routing
• kibana/ for dashboards & index patterns
• elastalert/, replay/, rules/, sigma/ for alerts and detection rules
README for additional insights
• Confirms the stack components (Elasticsearch cluster, Beats, Logstash, Kibana, N8n, Zircolite, Velociraptor, Spiderfoot, Syslog-ng, etc.)
• References an Architecture Guide in the wiki
• Mentions single vs. multi-node modes