You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: umbraco-cloud/build-and-customize-your-solution/set-up-your-project/security/managing-transport-security.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Currently, these options are available:
10
10
* Web Application Firewall (WAF) (default: on)
11
11
* Web Application Firewall Sensitivity (default: off)
12
12
* Managed Challenge (default: off)
13
-
* Continent Managed Challenge (default: empty)
13
+
* Continent Managed Challenge (default: none)
14
14
15
15
When a new custom hostname is added to a Project it will have the default settings applied. But you can change the defaults for your Project, so new custom hostnames will get the default settings you have chosen.
16
16
@@ -32,17 +32,23 @@ A Web Application Firewall (WAF) is a security solution designed to protect web
32
32
33
33
## Web Application Firewall Sensitivity
34
34
35
-
The Umbraco Cloud WAF supports sensitivity configuration, extending the default [WAF](web-application-firewall.md) protection. **Low** sensitivity WAF configuration will block malicious requests with high confidence. **High**sensitivity configuration will block malicious requests with medium confidence, providing stricter filtering. By default, the WAF sensitivity is **off**and only the standard [WAF](web-application-firewall.md) is in place. Customers are encouraged to experiment with the WAF configuration at the beginning of the project and adjust based on the WAF performance.
35
+
The Umbraco Cloud WAF supports sensitivity configuration, extending the default [WAF](web-application-firewall.md) protection. The default [WAF](web-application-firewall.md) and WAF sensitivity configuration options don't interact and can be controlled separately. Customers are encouraged to experiment with the WAF configuration at the beginning of the project and adjust based on the performance.
36
36
37
-
## Managed Challenge
37
+
-**Low** severity configuration will block malicious requests with high confidence - blocks less requests.
38
+
-**High** severity configuration will block malicious requests with medium confidence, providing stricter filtering - blocks more requests.
39
+
-**Off** configuration will not block any requests.
38
40
39
-
Managed Challenge gives you the ability to present an automatic captcha to all requests for the project/hostname. The managed challenge will ensure that only human users will be able to access the content on the website. Presenting an automatic managed captcha is useful in cases when a website is under attack, aggressively scraped by bots or in extremely high demand and you'd like to ensure that all of your website's resources are delivering value to the end users.
41
+
## Managed Challenge
40
42
41
43
A managed challenge is a lightweight JavaScript-based page that detects users without user inputs. After successfully passing a challenge, the user will receive a cookie and won't be asked to pass another challenge for 30 minutes anywhere on the project/hostname.
42
44
45
+
Enabling the Managed Challenge presents an automatic captcha to all requests for the project/hostname. The managed challenge will ensure that only human users will be able to access the content on the website. Presenting an automatic managed captcha is useful in cases when a website is under attack, aggressively scraped by bots or in extremely high demand and you'd like to ensure that all of your website's resources are delivering value to the end users.
46
+
43
47
## Continent Managed Challenge
44
48
45
-
Continent-based managed challenge presents a challenge meant to only pass through the human users requesting the website from selected continents. A continent-based managed challenge is useful when a website's primary users live in a specific continent and you can safely treat any other geographical visitors with a challenge. Presenting a challenge to all automated traffic from continents that the end content isn't meant for easily blocks all malicious automated traffic.
49
+
Selecting continent(s) in the list will present a managed challenge to all traffic from the continent(s).
50
+
Continent-based managed challenge presents a challenge meant to only pass through the human users requesting the website from selected continents. A continent-based managed challenge is useful when a website's primary users live in a specific continent and you can safely treat any other geographical visitors with a challenge.
51
+
can block all malicious automated traffic.
46
52
47
53
All continents are supported as well as presenting a challenge to all requests from the [Tor](https://en.wikipedia.org/wiki/Tor_(network)) network.
0 commit comments