v1.17.0-beta.1
New
- Web attack alerts are now shown: if you enabled CrowdSec's AppSec (WAF) component, its alerts — blocked
.envprobes, virtual-patching hits, bot challenges — appear alongside your regular alerts, including which rule fired, which of your sites was targeted and the request method used. - Filter by alert origin: the alerts list accepts a new
alert_typefilter. Leave it onallto see everything, pickappsecfor only web attacks, orlogsfor only the classic log-based alerts. - Filter web attacks by rule and host: you can narrow the alerts list to a specific AppSec rule (e.g. everything matching
vpatch-env-access) or to one of your sites, and combine it with the other filters you already use. - New statistics for web attacks: the alerts summary now tells you how many alerts are AppSec, which rules fire the most and which hosts get attacked the most.
- The AI assistant endpoint understands the new filters too: you can ask things like "show me only the WAF alerts" or "which AppSec rule triggered the most this week?" in plain language.
- Notifications can now watch web attacks: create a notification that fires when a specific AppSec rule or host shows up, just like you already do with scenarios or countries.
Changed
- Alerts coming from blocklist imports are now explicitly kept out of the alerts list (they keep living in their own blocklist section, as before).
Notes
- This is a beta: the AppSec views, filters and statistics may still change slightly before the stable release. Your stored alerts and settings are untouched — updating only adds the new views on top.
- No configuration changes are needed. If your CrowdSec is very old and the new kind-based sync finds nothing, the classic filters keep working exactly as before.
- The database prepares empty tables for a future metrics-history view, but nothing reads or writes them yet in this beta.