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: src/content/docs/page-shield/how-it-works/index.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ description: Page Shield tracks resources (such as scripts) loaded by your
12
12
13
13
import { GlossaryTooltip } from"~/components";
14
14
15
-
Page Shield helps manage resources loaded by your website visitors, including scripts, their connections, and cookies. It can trigger alert notifications when resources change or are considered malicious.
15
+
Page Shield helps manage resources loaded by your website visitors, including scripts, their connections, and [cookies](https://www.cloudflare.com/learning/privacy/what-are-cookies/). It can trigger alert notifications when resources change or are considered malicious.
16
16
17
17
Enabling Page Shield adds a <GlossaryTooltipterm="content security policy (CSP)"link="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP">Content Security Policy (CSP)</GlossaryTooltip> deployed with a [report-only directive](/page-shield/reference/csp-header/) to collect information from the browser. This allows Cloudflare to provide you with a list of all scripts running on your application and the connections they make to third-party endpoints. Page Shield also monitors ingress and egress traffic for cookies, either set by origin servers or by the visitor's browser.
Copy file name to clipboardExpand all lines: src/content/docs/ruleset-engine/reference/phases-list.mdx
+36-46Lines changed: 36 additions & 46 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,18 +3,15 @@ title: Phases list
3
3
pcx_content_type: reference
4
4
sidebar:
5
5
order: 1
6
-
7
6
---
8
7
9
-
import { Render } from"~/components"
8
+
import { Render } from"~/components";
10
9
11
10
The following tables list the [phases](/ruleset-engine/about/phases/) of Cloudflare products powered by the Ruleset Engine, in the order those phases are executed. Some products such as the Cloudflare Web Application Firewall have more than one associated phase.
12
11
13
12
## Network layer
14
13
15
-
Network-layer phases apply to packets received on the Cloudflare global network.
16
-
17
-
14
+
[Network-layer](https://www.cloudflare.com/learning/ddos/glossary/open-systems-interconnection-model-osi/) phases apply to packets received on the Cloudflare global network.
Copy file name to clipboardExpand all lines: src/content/docs/waf/analytics/security-analytics.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Security Analytics displays information about all incoming HTTP requests for you
12
12
Use the Security Analytics dashboard to:
13
13
14
14
- View the traffic distribution for your domain.
15
-
- Understand which traffic is being mitigated by Cloudflare security products, and where non-mitigated traffic is being served from (Cloudflare global network or origin server).
15
+
- Understand which traffic is being mitigated by Cloudflare security products, and where non-mitigated traffic is being served from (Cloudflare global network or [origin server](https://www.cloudflare.com/learning/cdn/glossary/origin-server/)).
16
16
- Analyze suspicious traffic and create tailored WAF custom rules based on applied filters.
17
17
- Learn more about Cloudflare's security scores (<GlossaryTooltipterm="attack score"link="/waf/detections/attack-score/">attack score</GlossaryTooltip>, [bot score](/bots/concepts/bot-score/), [malicious uploads](/waf/detections/malicious-uploads/), and [leaked credentials](/waf/detections/leaked-credentials/) results) with real data.
18
18
-[Find an appropriate rate limit](/waf/rate-limiting-rules/find-rate-limit/) for incoming traffic.
Copy file name to clipboardExpand all lines: src/content/docs/waf/custom-rules/use-cases/challenge-bad-bots.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ When a request is definitely automated (score of 1) or likely automated (scores
57
57
58
58
#### Exempt API traffic
59
59
60
-
Since Bot Management detects automated users, you need to explicitly allow your **good** automated traffic — this includes your APIs and partner APIs.
60
+
Since Bot Management detects automated users, you need to explicitly allow your **good** automated traffic — this includes your [APIs](https://www.cloudflare.com/learning/security/api/what-is-an-api/) and partner APIs.
61
61
62
62
This example offers the same protection as the browser-only rule, but allows automated traffic to your API.
You can use these fields in expressions of [custom rules](/waf/custom-rules/) and [rate limiting rules](/waf/rate-limiting-rules/). Attack score fields of data type `Number` vary between `1` and `99` with the following meaning:
Copy file name to clipboardExpand all lines: src/content/docs/waf/detections/leaked-credentials/get-started.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ For additional examples, refer to [Mitigation examples](/waf/detections/leaked-c
76
76
77
77
### Handle detected leaked credentials at the origin server
78
78
79
-
Additionally, you may want to handle leaked credentials detected by Cloudflare at your origin server.
79
+
Additionally, you may want to handle leaked credentials detected by Cloudflare at your [origin server](https://www.cloudflare.com/learning/cdn/glossary/origin-server/).
80
80
81
81
1. Turn on the [**Add Leaked Credentials Checks Header** managed transform](/rules/transform/managed-transforms/reference/#add-leaked-credentials-checks-header).
Copy file name to clipboardExpand all lines: src/content/docs/waf/detections/leaked-credentials/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ sidebar:
7
7
label: Leaked credentials
8
8
---
9
9
10
-
The leaked credentials [traffic detection](/waf/detections/) scans incoming requests for previously leaked credentials (usernames and passwords) previously leaked from data breaches.
10
+
The leaked credentials [traffic detection](/waf/detections/) scans incoming requests for previously leaked credentials (usernames and passwords) previously leaked from [data breaches](https://www.cloudflare.com/learning/security/what-is-a-data-breach/).
11
11
12
12
:::note
13
13
If you are currently using [Exposed Credentials Check](/waf/managed-rules/check-for-exposed-credentials/) (a previous implementation) and want to upgrade to leaked credentials detection, refer to our [upgrade guide](/waf/managed-rules/check-for-exposed-credentials/upgrade-to-leaked-credentials-detection/).
@@ -26,7 +26,7 @@ In addition, leaked credentials detection provides a [managed transform](/rules/
26
26
One common approach used in web applications when detecting the use of stolen credentials is to warn end users about the situation and ask them to update their password. You can do this based on the managed header received at your origin server.
27
27
28
28
:::note
29
-
Cloudflare may detect leaked credentials either because an attacker is performing a credential stuffing attack or because a legitimate end user is reusing a previously leaked password.
29
+
Cloudflare may detect leaked credentials either because an attacker is performing a [credential stuffing](https://www.cloudflare.com/learning/bots/what-is-credential-stuffing/) attack or because a legitimate end user is reusing a previously leaked password.
0 commit comments