CrowdSec Threat Map

CrowdSec Threat Map is a dashboard for homelabers running CrowdSec that displays local alerts on an interactive world map with a live feed, CSV export,…

  • Monitoring & Logging
  • Network Services
  • Tools & Utilities
CrowdSec Threat Map is a dashboard for homelabers running CrowdSec that displays local alerts on an interactive world map with a live feed, CSV export, themes, language options, and optional unban and dynamic whitelist controls.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

47/100 Fair

Maintained
75last commit 91 days ago
Popular
123 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
3
Open issues
0
Last commit
2026-08-22
License
GPL-3.0
Activity
stale

Checked 7 days ago - source: GitHub (Railline/crowdsec-threat-map-docker)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Run interactive setup first Run `cscli setup interactive` before starting; it can detect services like SSH and web logs and write the acquisition files that tell CrowdSec which logs to watch. Without this, the threat map often stays empty because CrowdSec has no log sources. source
  • Install parsers for your logs Install parsers that match the logs you want analyzed, such as SSH or your web server logs. If the parser is missing, CrowdSec cannot understand the lines, so bad activity won't appear on the map. source
  • Validate setup files early If you create or edit `setup.yaml`, run `cscli setup validate setup.yaml` before applying it. This catches missing or misconfigured log sources early instead of leaving the install half done. source
  • Required volumes Mount your CrowdSec data and postoverflows directories (read-only) plus the Docker socket so the unban and whitelist controls actually work. source
  • Required mounts and map settings Mount the local CrowdSec data and postoverflows directories (data read-only), set SERVER_LAT and SERVER_LON to center the map on your location, and optionally mount /var/run/docker.sock read-only to enable the unban and whitelist actions. source

Fetched 30 days ago - each note links to its source

Alternatives (5)

  • Cloudflare - Protects websites with front-end proxy, dynamic DNS, CDN, and firewall; blocks DDoS and targeted attacks, optimizes traffic, and analyzes t…
  • CrowdSec - CrowdSec is a free, open-source IDS/IPS and WAF that detects malicious behavior by analyzing server logs and HTTP requests, then blocks off…
  • Fail2ban - Fail2ban is a daemon that monitors log files and automatically bans hosts that cause multiple authentication failures, using firewall rules…
  • IPBanPro - IPBan is a FREE and open source application that allows auto banning ip addresses from failed login attempts.
  • defensia-agent

Checked 40 days ago - source: AlternativeTo

Common questions

Why does the CrowdSec Threat Map show no alerts after the container starts?

Run cscli setup interactive before starting CrowdSec so it detects services and writes the acquisition files that tell CrowdSec which logs to watch. Without log sources, the threat map often stays empty.

What should I do if my CrowdSec installation uses a database backend other than SQLite?

The container reads the CrowdSec SQLite database directly. If your CrowdSec install uses another database backend, mirror or export the data to a readable SQLite file before using this dashboard.

How can I enable the optional unban and whitelist restart features safely?

Mount the Docker socket read-only only when using the dashboard unban or whitelist restart features. Set UNBAN_API_TOKEN if /unban is reachable outside a trusted LAN.

How do I choose the dashboard language?

Set LANGUAGE=en or LANGUAGE=fr. Unknown values fall back to English.

Which port should I expose for the dashboard?

Expose port 8080 and open the dashboard on that port.

Answers sourced from doc.crowdsec.net, github.com

Community

Collected 48 days ago - public community threads