up

Author: buixor

crowdsec-docs/docs/intro.mdx

@@ -57,7 +57,9 @@ Under the hood, the Security Engine has various components:
 
  - 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.
  - The [Appsec](/appsec/intro.md) feature is part of the Log Processor and filters HTTP Requests from the compatible web servers. 
- - 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.
+ - 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.
+    - And with the [Central API](/central_api/intro.md) to share alerts and receive blocklists.
  - 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)
 
 This architecture allows for both simple/standalone setups, or more distributed ones including as illustrated below: