Skip to content

Commit e30b4ca

Browse files
committed
fix appsec broken links
1 parent f6b6585 commit e30b4ca

File tree

13 files changed

+28
-28
lines changed

13 files changed

+28
-28
lines changed

crowdsec-docs/docs/appsec/installation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ tcp 0 0 127.0.0.1:7422 0.0.0.0:* LISTEN
102102

103103
## Configuration : Remediation component
104104

105-
Configuring the AppSec component [accross remediation components](/appsec/installation#pre-requisites) can vary:
105+
Configuring the AppSec component [accross remediation components](appsec/installation.md#pre-requisites) can vary:
106106

107107
| Name | Minimum Version | Public Doc |
108108
| --------- | --------------- | ----------- |

crowdsec-docs/docs/appsec/intro.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,9 @@ This component capitalizes on existing remediation functions in web servers (suc
2424
![appsec-global](/img/appsec-global.svg)
2525

2626
1. The Web Server receives the HTTP request
27-
2. The HTTP Request is intercepted and passed to the CrowdSec Security Engine via [the HTTP API](/appsec/protocol.md)
27+
2. The HTTP Request is intercepted and passed to the CrowdSec Security Engine via [the HTTP API](appsec/protocol.md)
2828
3. The Security Engine answers to the Web Server once the Appsec inband rules have been processed.
29-
4. Based on the [Security Engine answer](/appsec/protocol#response-code), the Web Server either blocks the HTTP Request or processes it as usual
29+
4. Based on the [Security Engine answer](appsec/protocol.md#response-code), the Web Server either blocks the HTTP Request or processes it as usual
3030

3131
## Inband Rules and Out-Of-Band Rules
3232

crowdsec-docs/docs/appsec/quickstart/nginxopenresty.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Steps:
8181

8282
The two important directives in this configuration file are:
8383

84-
- `appsec_config` is the name of the [*AppSec Configuration*](/appsec/configuration.md#appsec-configuration) that was included in the [Collection](/concepts.md#colleccollectionstion) we just installed.
84+
- `appsec_config` is the name of the [*AppSec Configuration*](appsec/configuration.md#appsec-configuration) that was included in the [Collection](/concepts.md#collections) we just installed.
8585
- the `listen_addr` is the IP and port the AppSec Component will listen to.
8686

8787
:::warning

crowdsec-docs/docs/appsec/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ DEBU[2023-12-06 15:40:26] Finish evaluating rule band=inb
6363
## Authenticating with the AppSec Component
6464

6565
:::note
66-
We are assuming the AppSec engine is running on `127.0.0.1:7422`. See [installation directives](/docs/next/appsec/install)
66+
We are assuming the AppSec engine is running on `127.0.0.1:7422`. See [installation directives](/docs/next/appsec/installation)
6767
:::
6868

6969
> Create a valid API Key

crowdsec-docs/docs/concepts.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ The `labels` part is here to tag the incoming logs with a type. `labels.type` ar
6565

6666
## Application Security Component
6767

68-
[[References](/appsec/intro.md)]
68+
[[References](appsec/intro)]
6969

7070
The Application Security Component is a special datasource that allows the supported remediation components to forward HTTP requests to crowdsec for analysis, before they can reach the application.
7171
Because CrowdSec can analyse the request and take a decision before it reaches the application, the combo of the Application Security Component and the remediation components acts as a Web Application Firewall (WAF).
@@ -142,9 +142,9 @@ You can as well [write your own](/scenarios/create.md)!
142142

143143
## AppSec Rules
144144

145-
[[References](/appsec/intro.md)]
145+
[[References](appsec/intro)]
146146

147-
An AppSec rule is a YAML configuration file that describe a rule for the [Application Security Component](/appsec/intro.md).
147+
An AppSec rule is a YAML configuration file that describe a rule for the [Application Security Component](appsec/intro).
148148

149149
An AppSec rule can match on various aspect of an HTTP request, such as the verb, the URI, the headers, the parameters, the body, etc.
150150
You can use them to detect and block exploitation of specific vulnerabilities (virtual patching) or to write more generic WAF rules.
@@ -153,12 +153,12 @@ Contrary to scenarios, appsec rules can block a request before it reaches the ap
153153

154154
## AppSec Configs
155155

156-
An Appsec Config file is a YAML configuration file that tell the [Application Security Component](/appsec/intro.md) which rules should be loaded, and in which band (in-band or out-of-band).
156+
An Appsec Config file is a YAML configuration file that tell the [Application Security Component](appsec/intro) which rules should be loaded, and in which band (in-band or out-of-band).
157157

158158
The config also expose hooks allowing you to customize at runtime the behavior of the AppSec component (disable a rule on a specific URL, apply a captcha if a specific rule is triggered, etc.)
159159

160160

161-
[[References](/appsec/intro.md)]
161+
[[References](appsec/intro)]
162162

163163
## Collections
164164

crowdsec-docs/docs/data_sources/appsec.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ title: Application Security Component
66

77
This module allows you to enable the `Application Security Component` as a data source.
88

9-
A more detailed documentation is available [here](/appsec/intro.md).
9+
A more detailed documentation is available [here](/docs/next/appsec/intro).
1010

11-
A quickstart tutorial is available [here](/appsec/quickstart.md).
11+
A quickstart tutorial is available for [Nginx/OpenResty](/docs/next/appsec/quickstart/nginxopenresty) and [Traefik](/docs/next/appsec/quickstart/traefik).
1212

1313
## Configuration example
1414

crowdsec-docs/docs/intro.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,8 +49,8 @@ In addition to the core "detect and react" mechanism, CrowdSec is committed to s
4949

5050
Under the hood, the Security Engine has various components:
5151

52-
- 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.
53-
- The [Appsec](/appsec/intro.md) feature is part of the Log Processor and filters HTTP Requests from the compatible web servers.
52+
- The Log Processor is in charge of detection: it analyzes logs from [various data sources](data_sources/intro) or [HTTP requests](appsec/intro) from web servers.
53+
- The [Appsec](appsec/intro) feature is part of the Log Processor and filters HTTP Requests from the compatible web servers.
5454
- The [Local API](/local_api/intro.md) acts as a middle man:
5555
- Between the [Log Processors](/docs/data_sources/intro) and the [Remediation Components](/u/bouncers/intro) which are in charge of enforcing decisions.
5656
- And with the [Central API](/central_api/intro.md) to share alerts and receive blocklists.
@@ -64,7 +64,7 @@ This architecture allows for both simple/standalone setups, or more distributed
6464
- Already have a log pit (such as rsyslog or loki)? Run crowdsec next to it, not on the production workloads
6565
- Running Kubernetes? Have a look at [our helm chart](/u/getting_started/installation/kubernetes)
6666
- Running containers? The [docker data source](/docs/data_sources/docker) might be what you need
67-
- Just looking for a WAF? Look at [our quickstart](/appsec/intro.md)
67+
- Just looking for a WAF? Look at [our quickstart](appsec/intro)
6868

6969
Distributed architecture example:
7070

crowdsec-docs/versioned_docs/version-v1.6.0/appsec/intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ This component capitalizes on existing remediation functions in web servers (suc
2626
1. The Web Server receives the HTTP request
2727
2. The HTTP Request is intercepted and passed to the Crowdsec Security Engine via [the HTTP API](/appsec/protocol.md)
2828
3. The Security Engine answers to the Web Server once the Appsec inband rules have been processed.
29-
4. Based on the [Security Engine answer](/appsec/protocol#response-code), the Web Server either blocks the HTTP Request or processes it as usual
29+
4. Based on the [Security Engine answer](/appsec/protocol.md#response-code), the Web Server either blocks the HTTP Request or processes it as usual
3030

3131
## Inband Rules and Out-Of-Band Rules
3232

crowdsec-docs/versioned_docs/version-v1.6.0/appsec/quickstart.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ sidebar_position: 2
66

77
## Objectives
88

9-
The goal of this quickstart is to set up the [AppSec Component](/appsec/intro.md#introduction) to safeguard web applications running on [Nginx](https://nginx.com). We'll deploy a [set of rules](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching) designed to block [well-known attacks](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-generic-rules) and [currently exploited vulnerabilities](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching). Additionally, we'll show how to monitor these alerts through the [console](https://app.crowdsec.net/).
9+
The goal of this quickstart is to set up the [AppSec Component](appsec/intro.md#introduction) to safeguard web applications running on [Nginx](https://nginx.com). We'll deploy a [set of rules](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching) designed to block [well-known attacks](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-generic-rules) and [currently exploited vulnerabilities](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching). Additionally, we'll show how to monitor these alerts through the [console](https://app.crowdsec.net/).
1010

1111
## Pre-requisites
1212

13-
1. If you're new to the [AppSec Component](/appsec/intro.md#introduction) or **W**eb **A**pplication **F**irewalls, start with the [Introduction](/appsec/intro.md#introduction) for a better understanding.
13+
1. If you're new to the [AppSec Component](appsec/intro.md#introduction) or **W**eb **A**pplication **F**irewalls, start with the [Introduction](appsec/intro.md#introduction) for a better understanding.
1414

1515
2. It's assumed that you have already installed:
1616
- **Crowdsec [Security Engine](/docs/next/intro)**: for installation, refer to the [QuickStart guide](/docs/getting_started/install_crowdsec). The AppSec Component, which analyzes HTTP requests, is included within the security engine.

crowdsec-docs/versioned_docs/version-v1.6.0/appsec/troubleshooting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ DEBU[2023-12-06 15:40:26] Finish evaluating rule band=inb
6363
## Authenticating with the AppSec Component
6464

6565
:::note
66-
We are assuming the AppSec engine is running on `127.0.0.1:7422`. See [installation directives](/docs/next/appsec/install)
66+
We are assuming the AppSec engine is running on `127.0.0.1:7422`. See [installation directives](/docs/next/appsec/installation)
6767
:::
6868

6969
> Create a valid API Key

0 commit comments

Comments
 (0)