Content
- WAF configurations2
WAF - Bot Challenge Detections (extra)Parent2 items
sudo cscli collections install crowdsecurity/appsec-bot-challenge-detections-extraThen 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-detections-extra# Detections held out of the default bundle because they are still experimental.## detect-cpu-arch ships a WebAssembly module: it needs 'wasm-unsafe-eval' in# the challenge CSP.appsec-configs:- crowdsecurity/appsec-bot-challenge-detect-cpu-arch- crowdsecurity/appsec-bot-challenge-warn-experimentaldescription: "AppSec bot challenge: CPU architecture against the claimed platform (WebAssembly)"labels:label: "WAF - Bot Challenge Detections (extra)"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.
Detections kept out of the appsec-bot-challenge bundles because they are considered more experimental.
appsec-bot-challenge-detect-cpu-arch — reads the processor actually executing from a
WebAssembly NaN bit pattern and checks it against an iOS or Android claim. Needs
wasm-unsafe-eval in the challenge CSP, and takes a share of the challenge's shared
client-side time budget away from fonts and codecs.appsec-bot-challenge-warn-experimental — the alert policy, listed here as well so this
collection works on its own.Staged like the other unvalidated detections: the rules score 0 and only raise a
crowdsecurity/suspicious-browser-submission alert.
1cscli collections install crowdsecurity/appsec-bot-challenge-detections-extra
The documented crowdsecurity/appsec-bot-* wildcard in your AppSec acquisition picks both configs
up in the right order. Listing configs by name instead, warn-experimental goes last — after your
threshold config, whose RejectSubmission halts every later rule.