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

Author: LaurenceJJones

crowdsec-docs/docs/central_api/blocklist.md

@@ -12,8 +12,8 @@ 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.
@@ -38,3 +38,23 @@ The *Community Blocklist (Premium)* blocklist content has no size limit, unlike
 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?
+
+This can vary from engine to engine, but the most common reasons are:
+
+1. Your services are designed for self-hosting (videos, pictures, etc.) and are intended to be accessed only by a small group of people.
+
+In this case, your services may not be well known to the internet at large, so you may see less malicious traffic than a more public service such as a blog or ecommerce site.
+
+2. You already have a comprehensive security setup that reduces the need for the Community Blocklist. These measures can include:
+    - Geoblocking (restricting access to specific countries or your country of origin)
+    - IP whitelisting with a default deny-all policy
+    - VPN-only access
+    - Requiring authentication via an OAuth provider (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. Your CrowdSec installation may not be configured to monitor 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.