Skip to content

Commit a332cb3

Browse files
committed
fix jde comments
1 parent 4e0caef commit a332cb3

1 file changed

Lines changed: 6 additions & 16 deletions

File tree

crowdsec-docs/docs/intro.mdx

Lines changed: 6 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -23,18 +23,19 @@ import AcademyPromo from '@site/src/components/AcademyPromo';
2323
 
2424
 
2525

26+
2627
The [CrowdSec Security Engine](https://github.com/crowdsecurity/crowdsec) is an open-source, lightweight software that detects and blocks malicious actors from accessing your systems at various levels, using log and HTTP Requests analysis with threat patterns called scenarios.
2728

28-
CrowdSec is a modular framework, offering a variety of [scenarios](https://app.crowdsec.net/hub/collections). Users can choose their protection scenarios and deploy [Remediation Components](https://app.crowdsec.net/hub/bouncers) to block malicious access.
29+
CrowdSec is a modular security tool offering [behavior-based detection](https://app.crowdsec.net/hub/collections), including [AppSec rules](https://app.crowdsec.net/hub/appsec-rules), and optional components to block threats called [Remediation Components](https://app.crowdsec.net/hub/bouncers)
2930

30-
The crowd-sourced aspect allows sharing attack information among users, enhancing real-time attack detection and preemptive blocking of known bad actors from your system.
31+
The crowd-sourced aspect allows the sharing of attacks they detected and blocked. Participants of this crowd-sourced threat intel receive, automatically via the security engine, a curated list of validated attackers (community blocklist) enhancing their real-time protection capabilities by taking preemptive actions against known threats.
3132

3233
## Main Features
3334

3435
In addition to the core "detect and react" mechanism, CrowdSec is committed to several other key aspects:
3536

3637
- **Easy Installation**: Effortless out-of-the-box installation on all [supported platforms](/getting_started/versions_matrix.md).
37-
- **Simplified Daily Operations**: Use the [console](http://app.crowdsec.net) and [cscli](/cscli/cscli.md) for effortless maintenance and keeping your detection mechanisms up-to-date.
38+
- **Simplified Daily Operations**: You have access to our Web UI administration via [CrowdSec's console](http://app.crowdsec.net) or the powerful [Command line tool cscli](/cscli/cscli.md) for effortless maintenance and keeping your detection mechanisms up-to-date.
3839
- **Reproducibility**: The Security Engine can analyze not only live logs but also [cold logs](/u/user_guides/replay_mode), making it easier to detect potential false triggers, conduct forensic analysis, or generate reports.
3940
- **Versatile**: The Security Engine can analyze [system logs](/docs/data_sources/intro) and [HTTP Requests](/docs/next/appsec/intro) to exhaustively protect your perimeter.
4041
- **Observability**: Providing valuable insights into the system's activity:
@@ -46,12 +47,6 @@ In addition to the core "detect and react" mechanism, CrowdSec is committed to s
4647

4748
## Architecture
4849

49-
50-
<!-- @kka : update schema:
51-
- align text
52-
- rename data sources to log sources
53-
- move log sources out of the SE box
54-
-->
5550
<div style={{display: 'flex'}}>
5651
<div style={{textAlign: 'center', flex: '1'}}>
5752
<img src={useBaseUrl('/img/simplified_SE_underthehood.png')}></img>
@@ -61,14 +56,9 @@ In addition to the core "detect and react" mechanism, CrowdSec is committed to s
6156
Under the hood, the Security Engine has various components:
6257

6358
- The Log Processor is in charge of detection: it analyzes logs from [various data sources](/docs/data_sources/intro) or [HTTP requests](/appsec/intro.md) from web servers.
64-
- The [WAF](/appsec/intro.md) feature is part of the Log Processor and filters HTTP Requests from the compatible web servers.
59+
- The [Appsec](/appsec/intro.md) feature is part of the Log Processor and filters HTTP Requests from the compatible web servers.
6560
- The [Local API](/local_api/intro.md) acts as a middle man between the [Log Processors](/docs/data_sources/intro) and the [Remediation Components](/u/bouncers/intro) which are in charge of enforcing decisions.
66-
- The [Remediation Components](/u/bouncers/intro) - also known as bouncers - are in charge of blocking bad IPs by using the components already available.
67-
68-
69-
<!-- @tko
70-
- decide which ones to keep in the list and make (short) dedicated pages for those
71-
-->
61+
- The [Remediation Components](/u/bouncers/intro) - also known as bouncers - block malicious IPs at your chosen level—whether via IpTables, firewalls, web servers, or reverse proxies. [See the full list on our CrowdSec Hub.](https://app.crowdsec.net/hub/remediation-components)
7262

7363
This architecture allows for both simple/standalone setups, or more distributed ones including as illustrated below:
7464

0 commit comments

Comments
 (0)