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
Copy file name to clipboardExpand all lines: crowdsec-docs/unversioned/bouncers/intro.md
+10
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,16 @@ This command must be run on the server where the local API is installed (or at l
44
44
45
45
If you wish to create your own Remediation Component, look at [this section](/docs/next/local_api/bouncers) of the local API documentation.
46
46
47
+
## Remediation Component Badges
47
48
49
+
As CrowdSec has evolved over the years we have added support for various technologies and services. The following badges indicate the level of support for each remediation component.
50
+
51
+
| Badge | Description |
52
+
| --- | --- |
53
+
| AppSec | Can forward HTTP requests to the AppSec Component [more information](/docs/next/appsec/intro)|
54
+
| Mode | Can be configured into different modes, typically live (send a request to LAPI for each remediation check) or stream (downloads all current decisions to a local cache and checks periodically for new / deleted ones) <br/><br/>**note these are the naming schemes live/stream are used by first party remediation components**|
55
+
| Metrics | Can send detailed metrics to the LAPI [more information](/docs/next/observability/usage_metrics)|
56
+
| MTLS | Supports Mutual TLS authentication to the LAPI [more information](/docs/next/local_api/tls_auth)|
0 commit comments