Skip to content

Commit

Permalink
enhance: update comm bl with details and situations where lite happens (
Browse files Browse the repository at this point in the history
#731)

* enhance: update comm bl with details and situations where lite happens

* enhance: add better formatting

* enhance: add better formatting

* enhance: formatting
  • Loading branch information
LaurenceJJones authored Feb 9, 2025
1 parent e657527 commit 0c58e83
Showing 1 changed file with 29 additions and 5 deletions.
34 changes: 29 additions & 5 deletions crowdsec-docs/docs/central_api/blocklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,29 +12,53 @@ The "Community Blocklist" is a curated list of IP addresses identified as malici
# Community Blocklist Variation and Eligibility

The rules are different for free and paying users:
- Free users that **do not** contribute get the `Community Blocklist (Lite)`
- Free users that **do** contribute get access to the `Community Blocklist`
- Free users that **do not regularly** contribute get the `Community Blocklist (Lite)`
- Free users that **do regularly** contribute 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.

# Community Blocklist
## Community Blocklist

Free users that are actively contributing to the network (sending signal 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)

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)

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?

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](/u/getting_started/next_steps) to ensure full coverage.

0 comments on commit 0c58e83

Please sign in to comment.