CrowdSec blocking googlebot SEO crawler
Multi-SERVER - Problem with an agent with 2 IPs
Handle PersistentVolume for multiple LAPI replicas in Kubernetes environment
lapi.replicas=3
, and lapi.strategy.type=RollingUpdate
.
But when 3 lapi pods are being created, one succeeds and the two other fail because they can't be attached to the same volume....Opnsense reporting only "Unknown Behavior" in console Remediation Metrics
Pocket-Id Scenario
NGinx bouncer / appsec / no remediation
Rate limits on firewall integrations?
how do I use the BOUNCER_KEY_<name>=<key> ?
With TLS authentication: Bouncers are automatically registered and don't need an API key. The bouncers' names are derived from the IP address from which they connect.So my question, do I still need to define it in docker-compose somewhere?...
Does my Crowdsec block correctly?
Migrating LAPI from Docker to Opnsense
the list/decisions for ssh:bruteforce are not available on a standard query

Whitelisting specific IPs based on a file
Service machine won't connect to LAPI
Notification - traefik router name
CrowdSec not reacting to .git scans
apache2-logs
/http-sensitive-files
. Do you have any idea why?
log :
213.209.143.144 - - [21/Apr/2025:09:00:47 +0200] "GET /.git/objects/*/* HTTP/1.1" 404 48685 "-" "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0"
213.209.143.144 - - [21/Apr/2025:09:00:47 +0200] "GET /.git/objects/*/* HTTP/1.1" 404 48685 "-" "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0"

No decisions are made when testing with nikto on Kubernetes

Services with internal subdomain get blocked with Traefik bouncer
cloudflare bouncer
csLapiSecret and registrationToken injection from k8s secret impossible