Content
- WAF configurations5
sudo cscli collections install crowdsecurity/appsec-bot-challenge-permissiveInstalls 2 parsers and 2 scenarios.
View WAF - Bot Challenge (permissive) →sudo cscli collections install crowdsecurity/appsec-bot-challenge-exclude-pathsThen reload CrowdSec: sudo systemctl reload crowdsec
Sign in to see which of your engines run it →Hover a line or a note to see what each field does.
name: crowdsecurity/appsec-bot-challenge-exclude-paths# Building block: exempts machine-facing / non-navigational paths from the challenge.# Compose it into a top-level appsec-bot-challenge collection, or enable configs individually.appsec-configs:- crowdsecurity/appsec-bot-challenge-exclude-crawler-files- crowdsecurity/appsec-bot-challenge-exclude-static- crowdsecurity/appsec-bot-challenge-exclude-api- crowdsecurity/appsec-bot-challenge-exclude-feeds- crowdsecurity/appsec-bot-challenge-exclude-webhooksdescription: "AppSec bot challenge: exempt well-known paths (crawler files, static assets, API, feeds, webhooks)"labels:label: "WAF - Bot Challenge Path Exclusions"author: crowdsecuritytags:- waf- appsec- http- bot
Sign in to see the Security Engines that run this collection, the version they run and whether it was modified locally.
Part of the appsec-bot-challenge bundles. It lets machine-facing / non-navigational requests through without a challenge, since clients on these paths typically cannot solve one.
Per-purpose path exclusion configs:
/robots.txt, /.well-known/*, /security.txt, /sitemap.xml, …/api/, /graphql, /wp-json/, /oauth/, …)/webhooks/)Installed automatically by the appsec-bot-challenge bundle and its strict / permissive variants. Install it on its own to add just these exemptions, or enable individual configs if you don't want them all.