Skip to content

Commit 1472815

Browse files
committed
fix(waf): fix faq
1 parent 4af3a80 commit 1472815

File tree

5 files changed

+15
-3
lines changed

5 files changed

+15
-3
lines changed

faq/edge-services.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Yes, if you choose to [customize your Edge Services endpoint with your own subdo
3535

3636
## What is WAF?
3737

38-
**W**eb **A**pplication **F**irewall is a feature available via Edge Services for Load Balancer origins only. When enabled, WAF filters requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose. Find out more about WAF in our [detailed documentation](/edge-services/reference-content/understanding-waf/).
38+
**W**eb **A**pplication **F**irewall is a feature available in Public Beta via Edge Services for Load Balancer origins only. When enabled, WAF filters requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose. Find out more about WAF in our [detailed documentation](/edge-services/reference-content/understanding-waf/).
3939

4040
## I don't have a Load Balancer, how can I use WAF with a different type of Scaleway resource?
4141

@@ -49,4 +49,4 @@ Yes, you can have both of these features enabled at the same time on the same Lo
4949

5050
Scaleway Edge Services WAF uses the [OWASP **C**ore **R**ule **S**et (CRS)](https://coreruleset.org/). This is an industry standard, open source ruleset for WAF, which protects against multiple categories of attack such as SQL injection and cross-site scripting. Full details are available in the [OWASP CRS documentation](https://coreruleset.org/docs/).
5151

52-
We handle the automatic updating of rules, removing this hassle from you the user.
52+
We handle the regular updating of rules, removing this hassle from you the user.

pages/edge-services/concepts.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,4 +79,8 @@ The protocol (HTTP or HTTPS) that the Edge Services pipeline should use when sen
7979

8080
## WAF
8181

82+
<Message type="note">
83+
Edge Services WAF is currently in [Public Beta](https://www.scaleway.com/en/betas/).
84+
</Message>
85+
8286
An Edge Services **W**eb **A**pplication **F**irewall (WAF) evaluates requests to your Load Balancer origin to determine whether they are potentially malicious. You can set the [paranoia level](#paranoia-level) to be used when evaluating requests. Requests that are judged to be malicious are then blocked or logged, depending on the settings you choose. Find out more about [configuring WAF](/edge-services/how-to/configure-waf/).

pages/edge-services/how-to/configure-waf.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ categories:
1313
- network
1414
---
1515

16+
<Message type="note">
17+
Edge Services WAF is currently in [Public Beta](https://www.scaleway.com/en/betas/).
18+
</Message>
19+
1620
An Edge Services **W**eb **A**pplication **F**irewall (WAF) evaluates requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose.
1721

1822
This page walks you through the processing of enabling and configuring WAF to protect your Load Balancer origin.

pages/edge-services/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ meta:
88
sentiment="info"
99
title="Edge Services WAF is now available!"
1010
>
11-
Edge Services now offers a Web Application Firewall (WAF) service, to protect your Load Balancer origin from threats and malicious requests. Find out more in our [dedicated documentation](/edge-services/how-to/configure-waf/).
11+
Web Application Firewall (WAF) for Edge Services is now in Public Beta. Enable WAF to protect your Load Balancer origin from threats and malicious requests. Find out more in our [dedicated documentation](/edge-services/how-to/configure-waf/).
1212
</Alert>
1313

1414
<ProductHeader

pages/edge-services/reference-content/understanding-waf.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ categories:
1313
- network
1414
---
1515

16+
<Message type="note">
17+
Edge Services WAF is currently in [Public Beta](https://www.scaleway.com/en/betas/).
18+
</Message>
19+
1620
If your Edge Services pipeline points towards a Load Balancer origin, you can choose to enable the **W**eb **A**pplication **F**irewall (WAF) feature, for added protection. This documentation page gives a detailed overview of WAF, and the different settings, modes and functionalities available.
1721

1822
## WAF overview

0 commit comments

Comments
 (0)