# Why Crowdsec + Appsec in traefik not automate banned?

**URL:** <https://discourse.crowdsec.net/t/why-crowdsec-appsec-in-traefik-not-automate-banned/2231>\
**Category:** crowdsec\
**Created:** [January 2, 2025, 3:41am UTC](https://discourse.crowdsec.net/t/why-crowdsec-appsec-in-traefik-not-automate-banned/2231 "2025-01-02T03:41:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![afrzlfa](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/afrzlfa/32/1077_2.png) [@afrzlfa](https://discourse.crowdsec.net/u/afrzlfa)\
**Post date:** [January 2, 2025, 3:42am UTC](https://discourse.crowdsec.net/t/why-crowdsec-appsec-in-traefik-not-automate-banned/2231/1 "2025-01-02T03:42:00Z")

</div>

Why doesn’t CrowdSec + AppSec inside the Traefik Docker make banned decisions, even though it has already triggered an alert? How can it be made to trigger the banned action?

root@CrowdSec:/# docker exec -it traefik cscli alert list  
╭────┬──────────────────┬─────────────────────────────────┬─────────┬────┬───────────┬───────────────────────────────╮  
│ ID │ value │ reason │ country │ as │ decisions │ created\_at │  
├────┼──────────────────┼─────────────────────────────────┼─────────┼────┼───────────┼───────────────────────────────┤  
+0000 UTC │  
│ 1 │ Ip:xx.xx.xx.xx │ crowdsecurity/vpatch-env-access │ │ │ │ 2025-01-02 03:48:10 +0000 UTC │  
╰────┴──────────────────┴─────────────────────────────────┴─────────┴────┴───────────┴───────────────────────────────╯  
root@CrowdSec:/# docker exec -it traefik cscli decisions list  
No active decisions  
root@CrowdSec:/#

---

<div class="post-metadata">

**Author:** ![iiAmLoz](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/iiamloz/32/386_2.png) [@iiAmLoz](https://discourse.crowdsec.net/u/iiAmLoz)\
**Post date:** [January 2, 2025, 9:55am UTC](https://discourse.crowdsec.net/t/why-crowdsec-appsec-in-traefik-not-automate-banned/2231/2 "2025-01-02T09:55:29Z")

</div>

By default the `vpatch` [scenario](https://app.crowdsec.net/hub/author/crowdsecurity/scenarios/appsec-vpatch) needs a user to trigger 2 distinct appsec rules to get a decision, this is because we saw alot of false positive potential if a user trips up one rule.

You can change this behavior by changing `capacity` to `0` and this will trigger always on the first rule that get poured.