You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: optimize AppSec landing page for marketing campaigns
- Add "What is CrowdSec?" intro section for new users
- Replace confusing HTTP API references with plain-language explanations
- Add prominent "Supported Web Servers & Reverse Proxies" section with official brand logos
- Display Nginx, OpenResty, Traefik, and WordPress as separate visual cards
- Comment out HAProxy support until feature release
- Implement responsive grid layout with consistent logo sizing (50px height)
- Improve user experience for ad-driven landing page traffic
If you're new to CrowdSec, here's a quick overview:
10
+
11
+
**CrowdSec** is an open-source, collaborative security solution that:
12
+
- Detects and blocks malicious actors threatening your infrastructure and applications
13
+
- Provides real-time threat intelligence through a participative community
14
+
- Offers both **Infrastructure Protection** (IP reputation, DDoS mitigation) and **Application Security** (WAF capabilities)
15
+
16
+
:::tip New to CrowdSec?
17
+
For a more detailed introduction, check out our [Getting Started Guide](/u/getting_started/intro).
18
+
:::
8
19
9
-
<!-- xx : fix crowdsec version -->
20
+
## Introduction
10
21
11
22
Meet the Crowdsec **Application Security Component** (AKA : **AppSec Component**), a new capability for advanced application security turning your CrowdSec install into a full fledged **WAF**.
12
23
@@ -23,10 +34,55 @@ This component capitalizes on existing remediation functions in web servers (suc
23
34
24
35

25
36
37
+
### How it works
38
+
26
39
1. The Web Server receives the HTTP request
27
-
2. The HTTP Request is intercepted and passed to the CrowdSec Security Engine via [the HTTP API](appsec/protocol.md)
28
-
3. The Security Engine answers to the Web Server once the Appsec inband rules have been processed.
29
-
4. Based on the [Security Engine answer](appsec/protocol.md#response-code), the Web Server either blocks the HTTP Request or processes it as usual
40
+
2. The HTTP Request is forwarded to the CrowdSec Security Engine via a local HTTP interface
41
+
3. The Security Engine analyzes the request against AppSec rules (inband rules for immediate blocking)
42
+
4. Based on the analysis, the Web Server either blocks the HTTP Request or processes it as usual
43
+
44
+
## Supported Web Servers & Reverse Proxies
45
+
46
+
The AppSec Component works seamlessly with modern web servers and reverse proxies:
**Looking for other integrations?** Check out the [full list of remediation components](https://hub.crowdsec.net/browse/#remediation-components) on the CrowdSec Hub. We're constantly adding new integrations!
30
86
31
87
## Inband Rules and Out-Of-Band Rules
32
88
@@ -75,4 +131,4 @@ Or consider learning more about the AppSec capabilities:
75
131
-**Scenarios**: [How to create scenarios that leverage the AppSec Component events](/appsec/alerts_and_scenarios.md)
76
132
-**Hooks**: [To customise behavior of the AppSec at runtime](/appsec/hooks.md)
77
133
-**Troubleshoot**: [How to troubleshoot the behavior of the AppSec Component](/appsec/troubleshooting.md)
78
-
-**AppSec Protocol**: [if you're maintaining or creating a remedation component and want to add the AppSec capabilities](/appsec/protocol.md)
134
+
-**AppSec Technical Details**: [For developers integrating with the AppSec Component](/appsec/protocol.md)
0 commit comments