# Introduction The "Community Blocklist" is a curated list of IP addresses identified as malicious by CrowdSec. CrowdSec proactively block the IP addresses of this blocklist, preventing malevolent IPs from reaching your systems. # Community Blocklist Variation and Eligibility info The Community Blocklist is **only** available when using the Security Engine. To gain access, follow the steps in the [Getting Started Guide](https://docs.crowdsec.net/u/getting_started/intro.md). The rules are different for free and paying users: * Free users that **do not regularly contribute signals** get the `Community Blocklist (Lite)` * Free users that **do regularly contribute signals** get access to the `Community Blocklist` * Paying users get access to the `Community Blocklist (Premium)`, even if they don't contribute Regardless of the blocklist "tier" you have access to (`Lite`, `Community`, `Premium`), each Security Engine gets a tailored blocklist based on the kind of behavior you're trying to detect. ## What Counts as a Signal?[​](#what-counts-as-a-signal "Direct link to What Counts as a Signal?") For your signals to be counted toward community contribution, they must meet specific criteria: ### What We Count[​](#what-we-count "Direct link to What We Count") * **Signals generated by official CrowdSec scenarios from the Hub, unmodified** * We verify this by comparing the scenario's content hash we publish with the hash your engine reports ### What We Do Not Count[​](#what-we-do-not-count "Direct link to What We Do Not Count") * **Custom scenarios you write yourself** * **Tainted or modified scenarios** (even small edits). We cannot reliably vet behavior once a scenario is changed, so the consensus engine ignores those signals info Modifying a parser or using a custom parser has no impact on signal validity. ### Example[​](#example "Direct link to Example") If you only run a honeypot with a scenario you have modified, your local alerts will still fire, but the consensus engine will not use those signals. You can then show up as "not actively contributing," even though you see activity locally. ### How to Make Sure Your Signals Count[​](#how-to-make-sure-your-signals-count "Direct link to How to Make Sure Your Signals Count") * **Use the scenario straight from the Hub without edits** * **Keep auto-updates on** so hashes stay in sync * **If you need custom behavior**, copy to a local scenario and use it, but understand those signals will be excluded from consensus ## Community Blocklist[​](#community-blocklist "Direct link to Community Blocklist") Free users that are actively contributing to the network (sending signals on a regular basis) have their Security Engines automatically subscribed to the *Community Blocklist*. The content of the blocklist is unique to each Security Engine, as it mirrors the behaviours they report. For example, suppose you're running the Security Engine on a web server with WordPress. In that case, you will receive IPs performing generic attacks against web servers *and* IPs engaging in wordpress-specific attacks. The *Community Blocklist* contains 15 thousand malicious IP's based on your reported scenarios. ## Community Blocklist (Premium)[​](#community-blocklist-premium "Direct link to Community Blocklist (Premium)") Paying users' Security Engine are automatically subscribed to the *Community Blocklist (Premium)*, which contains IPs that mirror their installed scenarios. Paying users' do not need to contribute to the network to be eligible to the blocklist. The *Community Blocklist (Premium)* blocklist content has no size limit, unlike free users. ## Community Blocklist (Lite)[​](#community-blocklist-lite "Direct link to Community Blocklist (Lite)") Free users that are not actively contributing to the network or that have been flagged as cheating/abusing the system will receive the *Community Blocklist (Lite)*. This Blocklist is capped at 3 thousand IPs. ### Why is my Security Engine on the Lite Blocklist?[​](#why-is-my-security-engine-on-the-lite-blocklist "Direct link to Why is my Security Engine on the Lite Blocklist?") Your Security Engine may be placed on the Lite Blocklist for various reasons, such as: 1. Low Visibility Services Your services are self-hosted (e.g., for private video or image hosting) and primarily accessed by a small group. As a result, your Security Engine detects less malicious activity compared to public-facing services like blogs or e-commerce sites. 2. Comprehensive Security Setup Your existing security measures reduce reliance on the Community Blocklist. These may include: * Geoblocking (restricting access to certain countries) * IP whitelisting with a default deny-all policy * VPN-only access * OAuth authentication (e.g., Authentik, Authelia, Keycloak) This simply a result of your security model and access requirements, its neither an issue with your setup nor a limitation on our end. 3. Incomplete CrowdSec Configuration Your Security Engine may not be monitoring all your services. If you suspect this might be the case, refer to our [post-installation guide](https://docs.crowdsec.net/u/getting_started/next_steps.md) to ensure full coverage.