Skip to content

Commit 664adf4

Browse files
Merge branch 'main' into patch-2
2 parents 54ce5a1 + 858ac18 commit 664adf4

File tree

779 files changed

+39867
-4560
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

779 files changed

+39867
-4560
lines changed

crowdsec-docs/docs/appsec/alerts_and_scenarios.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
id: alerts_and_scenarios
3-
title: AppSec Alerts & Scenarios
3+
title: Alerts & Scenarios
44
sidebar_position: 5
55
---
66

@@ -115,7 +115,7 @@ We can now create a scenario that will trigger when a single IPs triggers this r
115115
type: leaky
116116
format: 3.0
117117
name: crowdsecurity/foobar-enum
118-
description: "Ban IPs repeateadly triggering out of band rules"
118+
description: "Ban IPs repeatedly triggering out of band rules"
119119
filter: "evt.Meta.log_type == 'appsec-info' && evt.Meta.rule_name == 'crowdsecurity/foobar-access'"
120120
distinct: evt.Meta.target_uri
121121
leakspeed: "60s"

crowdsec-docs/docs/appsec/benchmark.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
id: benchmark
3-
title: CrowdSec WAF / AppSec Component Benchmark
3+
title: WAF Component Benchmark
44
sidebar_position: 80
55
---
66

@@ -15,7 +15,7 @@ sidebar_position: 80
1515
1616
-->
1717

18-
The Application Security Component benchmarks have been run on a AWS EC2 Instance `t2.medium` (2vCPU/4Go RAM).
18+
The Application Security Component benchmarks have been run on a AWS EC2 Instance `t2.medium` (2vCPU/4GiB RAM).
1919

2020
All the benchmarks have been run with only one `routine` configured for the Application Security Component.
2121

0 commit comments

Comments
 (0)