Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions crowdsec-docs/sidebarsUnversioned.js
Original file line number Diff line number Diff line change
Expand Up @@ -557,11 +557,6 @@ module.exports = {
id: "getting_started/intro",
label: "🧭 Introduction",
},
{
type: "doc",
id: "getting_started/pre_requisites",
label: "📋 Prerequisites",
},
{
type: "category",
label: "📦 Installation",
Expand Down
19 changes: 19 additions & 0 deletions crowdsec-docs/src/components/UnderlineTooltip.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
import React from 'react';
import { Tooltip, TooltipTrigger, TooltipContent, TooltipProvider } from '@site/src/ui/tooltip';

export default function UnderlineTooltip({ children, tooltip }) {
return (
<TooltipProvider delayDuration={300}>
<Tooltip>
<TooltipTrigger asChild>
<span className="tw-underline tw-decoration-dashed tw-decoration-1 tw-decoration-gray-700 tw-cursor-help hover:tw-decoration-gray-900 dark:tw-decoration-gray-300 dark:hover:tw-decoration-gray-100 tw-underline-offset-2">
{children}
</span>
</TooltipTrigger>
<TooltipContent>
<p>{tooltip}</p>
</TooltipContent>
</Tooltip>
</TooltipProvider>
);
}
2 changes: 1 addition & 1 deletion crowdsec-docs/unversioned/getting_started/health_check.mdx
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: health_check
title: CrowdSec Security Engine Setup Health-Check
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/next_steps
---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: cloudways
title: Cloudways (CrowdSec + WP Remediation) - 🧪 Experimental
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: docker
title: Docker
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand All @@ -11,7 +11,7 @@ pagination_next: getting_started/health_check
Prerequisites are written for bare metal installations. Please keep in mind the containerization layer may make some of these items unnecessary.
:::

Before getting started it is advised to read the [prerequisites](/unversioned/getting_started/prerequisites.mdx) page to understand the requirements for running CrowdSec.
Before getting started it is advised to read the [introduction](/unversioned/getting_started/introduction.mdx) page to understand the requirements for running CrowdSec.

## Docker

Expand Down
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
id: freebsd
title: FreeBSD
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

# Installation FreeBSD

Before getting started it is advised to read the [prerequisites](/unversioned/getting_started/prerequisites.mdx) page to understand the requirements for running CrowdSec.
Before getting started it is advised to read the [introduction](/unversioned/getting_started/introduction.mdx) page to understand the requirements for running CrowdSec.

# Configuring the repositories

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: kubernetes
title: Kubernetes
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand All @@ -12,7 +12,7 @@ import CodeBlock from '@theme/CodeBlock';

# Kubernetes Deployment

Before proceeding, ensure you have met all [prerequisites](/unversioned/getting_started/prerequisites.mdx) necessary for running CrowdSec on Kubernetes.
Before proceeding, ensure you have met all [introduction](/unversioned/getting_started/introduction.mdx) necessary for running CrowdSec on Kubernetes.

## Requirements

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: linux
title: Linux
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand All @@ -11,7 +11,7 @@ import CodeBlock from '@theme/CodeBlock';

# Installation Linux

Before getting started it is advised to read the [prerequisites](/unversioned/getting_started/prerequisites.mdx) page to understand the requirements for running CrowdSec.
Before getting started it is advised to read the [introduction](/unversioned/getting_started/introduction.mdx) page to understand the requirements for running CrowdSec.

## Repository Installation

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: macos
title: MacOS
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand All @@ -17,7 +17,7 @@ We advise you to use our online sandbox to test CrowdSec on MacOS since it comes
[Find it here](https://killercoda.com/iiamloz/scenario/crowdsec-setup)
:::

Before getting started it is advised to read the [prerequisites](/unversioned/getting_started/prerequisites.mdx) page to understand the requirements for running CrowdSec.
Before getting started it is advised to read the [introduction](/unversioned/getting_started/introduction.mdx) page to understand the requirements for running CrowdSec.

## Running CrowdSec on MacOS

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: opnsense
title: OPNsense
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: pfsense
title: pfSense
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: whm
title: WHM plugin
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: windows
title: Windows
pagination_prev: getting_started/pre_requisites
pagination_prev: getting_started/intro
pagination_next: getting_started/health_check
---

Expand Down
15 changes: 0 additions & 15 deletions crowdsec-docs/unversioned/getting_started/introduction.md

This file was deleted.

76 changes: 76 additions & 0 deletions crowdsec-docs/unversioned/getting_started/introduction.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
---
id: intro
title: Introduction
sidebar_position: 1
---

import useBaseUrl from "@docusaurus/useBaseUrl"
import UnderlineTooltip from "@site/src/components/UnderlineTooltip"

## What is CrowdSec Security Engine?

The Security Engine is a collaborative and lightweight <UnderlineTooltip tooltip="An Intrusion Detection System monitors logs or traffic to detect and report suspicious or malicious behavior, such as scans, brute-force attempts, or exploits.">Intrusion Detection System</UnderlineTooltip> (IDS) and <UnderlineTooltip tooltip="A security system that filters, monitors, and blocks HTTP traffic to and from a web application to prevent attacks like SQL injection, XSS, and more.">Web Application Firewall</UnderlineTooltip> (WAF).

It begins by reading logs specified in <UnderlineTooltip tooltip="Acquisition files tell CrowdSec where to find logs and which application they belong to.">acquisitions</UnderlineTooltip>, then uses <UnderlineTooltip tooltip="YAML files that extract relevant data from logs, such as IP addresses, timestamps, or request paths.">parsers</UnderlineTooltip> to structure the information. This data is evaluated against <UnderlineTooltip tooltip="Behavioral rules written in a domain-specific language that define what malicious activity looks like, such as multiple failed logins in a short time.">scenarios</UnderlineTooltip>, which are designed to detect specific types of attacks or suspicious patterns.

When an attack is identified, CrowdSec can apply a <UnderlineTooltip tooltip="A temporary or permanent decision, like blocking an IP address, taken in response to a detected threat.">remediation</UnderlineTooltip>, based on rules defined in <UnderlineTooltip tooltip="Profiles are rule sets that define which decisions to take (or ignore) when a behavior is detected.">profiles</UnderlineTooltip>.

What makes CrowdSec unique is its <UnderlineTooltip tooltip="Users who detect malicious behavior share anonymized signals with the wider network, helping others preemptively block emerging threats.">collaborative threat intelligence</UnderlineTooltip> system, where each protected system contributes to a [community blocklist](/docs/next/central_api/community_blocklist) that helps everyone stay better protected.

## What is a Remediation Component?

Remediation Components are software modules that connect to the <UnderlineTooltip tooltip="The Local API (LAPI) is exposed by the Security Engine and acts as the interface for retrieving and managing decisions.">Local API</UnderlineTooltip> (LAPI) and enforce <UnderlineTooltip tooltip="Decisions are remediation actions such as bans or alerts taken by the Security Engine in response to detected threats.">decisions</UnderlineTooltip> made by the Security Engine.

These components can operate independently, such as the [Firewall Remediation](bouncers/firewall.mdx), which integrates with <UnderlineTooltip tooltip="A widely used packet filtering and firewall system for Linux.">iptables</UnderlineTooltip>, <UnderlineTooltip tooltip="The modern replacement for iptables, offering improved performance and a more consistent syntax.">nftables</UnderlineTooltip>, or <UnderlineTooltip tooltip="The built-in firewall system used on BSD-based systems like FreeBSD, OpenBSD, and macOS.">pf</UnderlineTooltip>. They can also be embedded directly into existing applications, such as [Nginx](bouncers/nginx.mdx), where <UnderlineTooltip tooltip="A lightweight scripting language embedded into software like Nginx to enable custom behavior, including dynamic security enforcement.">Lua</UnderlineTooltip> is used to enforce decisions at runtime.

This is often referred to as the <UnderlineTooltip tooltip="An Intrusion Prevention System actively blocks or mitigates detected threats, often based on decisions made by an Intrusion Detection System.">Intrusion Prevention System</UnderlineTooltip> (IPS) layer that complements the <UnderlineTooltip tooltip="An Intrusion Detection System monitors logs or traffic to detect and report suspicious or malicious behavior, such as scans, brute-force attempts, or exploits.">Intrusion Detection System</UnderlineTooltip> (IDS) role of the Security Engine. They do not make decisions on their own; instead, they act based on what the Security Engine instructs.

## Prerequisites

We recommend that you understand the following prerequisites before installing CrowdSec:

### Hardware

CrowdSec is a lightweight software that can run on most modern hardware.

However, the recommendation is at least:

* platform:
* amd64
* arm64
* armhf
* 1 CPU core
* 100mb of free RAM
* 1GB of free disk space

:::info
We recommend 1gb of free disk space due to the amount of data that can be stored in the database.
:::

### Operating System

We support the following operating systems:

* [Linux](/getting_started/installation/linux.mdx)
* [FreeBSD](/getting_started/installation/freebsd.mdx)
* [Windows](/getting_started/installation/windows.mdx)
* [MacOS](/getting_started/installation/macos.mdx) (through Docker)
* [Kubernetes](/getting_started/installation/kubernetes.mdx)

[See version matrix for detailed breakdown](/docs/next/getting_started/versions_matrix)

### Ports

CrowdSec Security Engine uses the following default ports these can be altered after installation:

* 6060/tcp: Prometheus metrics port
* 8080/tcp: API port

<div style={{ display: "flex" }}>
<div style={{ textAlign: "center", flex: "1" }}>
<img src={useBaseUrl("/img/simplified_SE_underthehood.svg")}></img>
</div>
</div>



58 changes: 0 additions & 58 deletions crowdsec-docs/unversioned/getting_started/prerequisites.mdx

This file was deleted.