📚 Documentation: https://doc.crowdsec.net/
💠 Configuration Hub: https://hub.crowdsec.net/
💬 Discourse (Forum): https://discourse.crowdsec.net/
💬 Gitter (Live chat): https://gitter.im/crowdsec-project/
CrowdSec is an open-source (MIT license) and collaborative security solution designed to protect Linux servers, services, containers, or virtual machines exposed on the internet with a server-side agent. It was inspired by Fail2Ban and aims to be a modernized, collaborative version of that intrusion-prevention tool.
The goal is to leverage the crowd power to create a real-time IP reputation database. As for the IP that aggressed your machine, you can choose to remedy the threat in any manner you feel appropriate. Ultimately, CrowdSec leverages the power of the crowd to create an extremely accurate IP reputation system that benefits all its users.
CrowdSec alternatives and similar tools
Based on the "Security" category.
Alternatively, view crowdsec alternatives based on common mentions on social networks and blogs.
OSQuery9.3 9.0 L2 CrowdSec VS OSQuerySQL powered operating system instrumentation, monitoring, and analytics.
lynis8.5 1.6 CrowdSec VS lynisLynis - Security auditing tool for Linux, macOS, and UNIX-based systems. Assists with compliance testing (HIPAA/ISO27001/PCI DSS) and system hardening. Agentless, and installation optional.
Fail2Ban8.2 7.0 L2 CrowdSec VS Fail2BanDaemon to ban hosts that cause multiple authentication errors
Wazuh7.7 9.9 CrowdSec VS WazuhWazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
pfSense7.6 9.8 L2 CrowdSec VS pfSenseMain repository for pfSense
Blackbox7.6 4.8 CrowdSec VS BlackboxSafely store secrets in Git/Mercurial/Subversion
OSSEC7.4 0.0 L2 CrowdSec VS OSSECOSSEC is an Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.
Suricata7.2 9.9 CrowdSec VS SuricataSuricata git repository maintained by the OISF
Snort6.0 9.0 L1 CrowdSec VS SnortSnort++
autoVPN5.8 0.0 CrowdSec VS autoVPNCreate On Demand Disposable OpenVPN Endpoints on AWS.
Kippo5.6 0.0 L4 CrowdSec VS KippoKippo - SSH Honeypot
Password Pusher5.2 6.5 CrowdSec VS Password Pusher🔐 An application to securely communicate passwords over the web. Passwords automatically expire after a certain number of views and/or time has passed. Track who, what and when.
fwknop4.9 0.0 L3 CrowdSec VS fwknopSingle Packet Authorization > Port Knocking
Glastopf4.5 0.0 L5 CrowdSec VS GlastopfWeb Application Honeypot
Denyhosts4.5 1.0 L3 CrowdSec VS DenyhostsAutomated host blocking from SSH brute force attacks
Pen Test Tools4.4 0.0 L5 CrowdSec VS Pen Test ToolsHomebrew Tap - Pen Test Tools
SpamAssassin3.4 5.9 L3 CrowdSec VS SpamAssassinRead-only mirror of Apache SpamAssassin. Submit patches to https://bz.apache.org/SpamAssassin/. Do not send pull requests
SOCless2.8 3.5 CrowdSec VS SOClessThe SOCless automation framework
Static code analysis for 29 languages.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of CrowdSec or a related project?
:computer: Console (WebApp) :books: Documentation :diamond_shape_with_a_dot_inside: Configuration Hub :speech_balloon: Discourse (Forum) :speech_balloon: Discord (Live Chat)
:dancer: This is a community driven project, we need your feedback.
CrowdSec is a free, modern & collaborative behavior detection engine, coupled with a global IP reputation network. It stacks on fail2ban's philosophy but is IPV6 compatible and 60x faster (Go vs Python), uses Grok patterns to parse logs and YAML scenario to identify behaviors. CrowdSec is engineered for modern Cloud / Containers / VM based infrastructures (by decoupling detection and remediation). Once detected you can remedy threats with various bouncers (firewall block, nginx http 403, Captchas, etc.) while the aggressive IP can be sent to CrowdSec for curation before being shared among all users to further improve everyone's security. See FAQ or read below for more.
2 mins install
Installing it through the Package system of your OS is the easiest way to proceed. Otherwise, you can install it from source.
From package (Debian)
curl -s https://packagecloud.io/install/repositories/crowdsec/crowdsec/script.deb.sh | sudo bash sudo apt-get update sudo apt-get install crowdsec
From package (rhel/centos/amazon linux)
curl -s https://packagecloud.io/install/repositories/crowdsec/crowdsec/script.rpm.sh | sudo bash sudo yum install crowdsec
From package (FreeBSD)
sudo pkg update sudo pkg install crowdsec
wget https://github.com/crowdsecurity/crowdsec/releases/latest/download/crowdsec-release.tgz tar xzvf crowdsec-release.tgz cd crowdsec-v* && sudo ./wizard.sh -i
:information_source: About the CrowdSec project
Crowdsec is an open-source, lightweight software, detecting peers with aggressive behaviors to prevent them from accessing your systems. Its user friendly design and assistance offers a low technical barrier of entry and nevertheless a high security gain.
The architecture is as follows :
Once an unwanted behavior is detected, deal with it through a bouncer. The aggressive IP, scenario triggered and timestamp are sent for curation, to avoid poisoning & false positives. (This can be disabled). If verified, this IP is then redistributed to all CrowdSec users running the same scenario.
Outnumbering hackers all together
By sharing the threat they faced, all users are protecting each-others (hence the name Crowd-Security). Crowdsec is designed for modern infrastructures, with its "Detect Here, Remedy There" approach, letting you analyse logs coming from several sources in one place and block threats at various levels (applicative, system, infrastructural) of your stack.
CrowdSec ships by default with scenarios (brute force, port scan, web scan, etc.) adapted for most context, but you can easily extend it by picking more of them from the HUB. It is also easy to adapt an existing one or create one yourself.
:point_right: What it is not
CrowdSec is not a SIEM, storing your logs (neither locally nor remotely). Your data are analyzed locally and forgotten.
Signals sent to the curation platform are limited to the very strict minimum: IP, Scenario, Timestamp. They are only used to allow the system to spot new rogue IPs, rule out false positives or poisoning attempts.
:arrow_down: Install it !
Crowdsec is available for various platforms :
- Use our debian repositories or the official debian packages
- An image is available for docker
- Prebuilt release packages are also available (suitable for
- You can as well build it from source
Or look directly at installation documentation for other methods and platforms.
:tada: Key benefits
Fast assisted installation, no technical barrier
Initial configuration is automated, providing functional out-of-the-box setup
Out of the box detection
Baseline detection is effective out-of-the-box, no fine-tuning required (click to expand)
Easy bouncer deployment
It's trivial to add bouncers to enforce decisions of crowdsec (click to expand)
Easy dashboard access
It's easy to deploy a metabase interface to view your data simply with cscli (click to expand)
Hot & Cold logs
Process cold logs, for forensic, tests and chasing false-positives & false negatives (click to expand)
📦 About this repository
This repository contains the code for the two main components of crowdsec :
crowdsec: the daemon a-la-fail2ban that can read, parse, enrich and apply heuristics to logs. This is the component in charge of "detecting" the attacks
cscli: the cli tool mainly used to interact with crowdsec : ban/unban/view current bans, enable/disable parsers and scenarios.
If you wish to contribute to the core of crowdsec, you are welcome to open a PR in this repository.
If you wish to add a new parser, scenario or collection, please open a PR in the hub repository.
If you wish to contribute to the documentation, please open a PR in the documentation repository.
*Note that all licence references and agreements mentioned in the CrowdSec README section above are relevant to that project's source code only.