appsec-bot-challenge-exclude-api WAF Configuration by crowdsecurity | CrowdSec Hub

appsec-bot-challenge-exclude-api

WAF configuration

By: crowdsecurity
Version: 0.2

Install with a top-level collection

3 collections include it

sudo cscli collections install crowdsecurity/appsec-bot-challenge

Installs 2 parsers and 2 scenarios, via WAF - Bot Challenge Path Exclusions.

View WAF - Bot Challenge →

Installation

sudo cscli appsec-configs install crowdsecurity/appsec-bot-challenge-exclude-api

Then reload CrowdSec: sudo systemctl reload crowdsec

Configuration

appsec-configs/crowdsecurity/appsec-bot-challenge-exclude-api.yaml· 15 linesGitHub

1name: crowdsecurity/appsec-bot-challenge-exclude-api
2# Let programmatic/API endpoints through without a challenge: it would break with legitimate clients 
3# that cannot solve the challenge.
4# Do not edit this file to add your own exclusions, create a custom config.
5inband:
6  pre_eval:
7    - filter: >-
8        req.URL.Path in ['/api', '/graphql'] ||
9        req.URL.Path startsWith '/api/' || req.URL.Path startsWith '/wp-json/' ||
10        req.URL.Path startsWith '/graphql/' || req.URL.Path startsWith '/rest/' ||
11        req.URL.Path startsWith '/v1/' || req.URL.Path startsWith '/v2/' ||
12        req.URL.Path startsWith '/oauth/' || req.URL.Path startsWith '/.netlify/functions/' ||
13        req.URL.Path startsWith '/_next/data/'
14      apply:
15        - ExemptFromChallenge("api")

Installed on

Know where it runs

Sign in to see the Security Engines that run this waf configuration, the version they run and whether it was modified locally.