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/cloudflare-one/email-security/setup/index.mdx
+30-21Lines changed: 30 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,36 +10,40 @@ sidebar:
10
10
11
11
import { Markdown } from"~/components";
12
12
13
-
Before you start the onboarding process, you will have to choose a deployment path. Email Security provides two deployment modes: [post-delivery](/cloudflare-one/email-security/setup/) (for API and BCC/Journaling), and [pre-delivery](/cloudflare-one/email-security/setup/#pre-delivery-deployment) (for MX/Inline).
13
+
## Before you begin
14
14
15
-
## Post-delivery deployment
15
+
Before you start the onboarding process, you will have to:
16
16
17
-
### How it works
17
+
1. Choose a deployment path: Email Security provides two deployment modes, [post-delivery](/cloudflare-one/email-security/setup/) for API and BCC/Journaling and [pre-delivery](/cloudflare-one/email-security/setup/#pre-delivery-deployment) for MX/Inline.
18
+
2. Learn about dispositions, impersonation registry, and reclassifications.
19
+
3. Know the steps to configure your email environment correctly.
20
+
21
+
## 1. Choose a deployment
22
+
23
+
### Post-delivery deployment
18
24
19
25
When you choose post-delivery deployment, Cloudflare scans emails **after** they reach a users' inbox.
20
26
21
-
If you are a Microsoft 365 user, this is done via Microsoft's Graph API or journaling.
27
+
If you are a Microsoft 365 user, this is done via [Microsoft's Graph API](/cloudflare-one/email-security/setup/post-delivery-deployment/api/office365-api/) or [journaling](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/journaling-setup/office365-journaling/).
22
28
23
-
If you are a Google Workspace or Microsoft Exchange user, this is done via BCC.
29
+
If you are a [Google Workspace](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/gmail-bcc-setup/gmail-bcc-setup/) or [Microsoft Exchange](/cloudflare-one/email-security/setup/post-delivery-deployment/bcc-journaling/bcc-setup/bcc-microsoft-exchange/) user, this is done via BCC.
24
30
25
-
### Why you should consider post-delivery deployment
31
+
####Why you should consider post-delivery deployment
26
32
27
33
Post-delivery deployment is time-efficient, because it does not involve MX changes. Post-delivery deployment does not disrupt mail flow. Post-delivery deployment allows you to enable [auto-move events](/cloudflare-one/email-security/auto-moves/) to hard or soft delete messages, and synchronize your [directory](/cloudflare-one/email-security/directories/) when you use Microsoft Graph API or Google Workspace.
28
34
29
35
:::note
30
36
When you choose post-delivery deployment:
31
37
- The threat is removed **after** the message has been delivered to the inbox.
32
-
- It requires API scopes, or BCC/journaling rule configuration.
38
+
- It requires API scopes, or BCC/Journaling rule configuration.
33
39
- Auto-move is only available in BCC/Journaling if you associate an integration.
34
40
:::
35
41
36
-
## Pre-delivery deployment
37
-
38
-
### How it works
42
+
### Pre-delivery deployment
39
43
40
44
When you choose pre-delivery deployment, Cloudflare scans emails **before** they reach a users' inbox. The MX record points to Cloudflare.
41
45
42
-
### Why you should consider pre-delivery deployment
46
+
####Why you should consider pre-delivery deployment
43
47
44
48
Pre-delivery deployment provides you with the highest level of protection. It enforces [text add-ons](/cloudflare-one/email-security/detection-settings/configure-text-add-ons/) or link rewrite at delivery.
45
49
@@ -52,13 +56,13 @@ When you choose pre-delivery deployment:
52
56
- Cloudflare [egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips/) are allowed on downstream mail servers.
53
57
:::
54
58
55
-
## Dispositions
56
-
57
-
Email traffic that flows through Email Security is given a final disposition, which represents Email Security's evaluation of that specific message. Refer to [Dispositions and attributes](/cloudflare-one/email-security/reference/dispositions-and-attributes/) to learn more.
59
+
## 2. Understand dispositions
58
60
59
61
Dispositions allow you to configure policies and tune reporting. For example, you can configure a policy to move suspicious emails to your junk folder.
60
62
61
-
## Impersonation registry
63
+
Refer to [Dispositions](/cloudflare-one/email-security/reference/dispositions-and-attributes/#dispositions) to learn more about dispositions.
64
+
65
+
## 3. Set up the impersonation registry
62
66
63
67
Most [Business email compromise(BEC)](https://www.cloudflare.com/en-gb/learning/email-security/business-email-compromise-bec/) targets executives or finance roles. You must add addresses of roles who are likely to be impersonated. Refer to [Impersonation registry](/cloudflare-one/email-security/detection-settings/impersonation-registry/) to learn how to add a user to the impersonation registry.
64
68
@@ -67,17 +71,18 @@ Roles you may want to include in the impersonation registry are:
67
71
- C-suites
68
72
- Finance roles
69
73
- HR
70
-
- IT help-desk.
74
+
- IT help-desk
71
75
72
76
You should review your impersonation registry on a quarterly basis as roles change.
73
77
74
-
## Reclassifications
78
+
## 4. Reclassify messages
79
+
80
+
A reclassification is a change to an email's disposition **after** initial scanning. It is Cloudflare's built-in feedback loop for correcting false positives/negatives **and** training the detection models to get smarter over time. Refer to [Reclassify messages](/cloudflare-one/email-security/email-monitoring/search-email/#reclassify-messages) to learn how to reclassify a message.
75
81
76
-
A reclassification is a change to an email's disposition **after** initial scanning. It is Cloudflare's built-in feedback loop for correcting false positives/negatives **and** training the detection models to get smarter over time.
77
82
78
83
### Who can reclassify messages
79
84
80
-
[Security teams](/cloudflare-one/email-security/email-monitoring/search-email/#team-submissions) and [end users](/cloudflare-one/email-security/email-monitoring/search-email/#user-submissions) can submit a reclassification. Refer to [Reclassify messages](/cloudflare-one/email-security/email-monitoring/search-email/#reclassify-messages) to learn how to reclassify a message.
85
+
[Security teams](/cloudflare-one/email-security/email-monitoring/search-email/#team-submissions) and [end users](/cloudflare-one/email-security/email-monitoring/search-email/#user-submissions) can submit a reclassification.
81
86
82
87
### Why you should reclassify messages
83
88
@@ -96,7 +101,9 @@ To make the most of reclassifications:
96
101
97
102
A correct use of reclassifications ensures that Email Security delivers a stronger protection with less manual tuning.
98
103
99
-
## Configuration checklist
104
+
## 5. Configuration checklist
105
+
106
+
Ensure you follow the below checklist to ensure your email environment is set up correctly:
@@ -111,4 +118,6 @@ A correct use of reclassifications ensures that Email Security delivers a strong
111
118
| Send a test email and verify it appears in **Monitoring** > [**Email activity**](/cloudflare-one/email-security/email-monitoring/#email-activity) with expected disposition | Required | Required |
112
119
113
120
[^1]: Alternatively, you can create a service account and add BCC rules.
114
-
[^2]: Still used for directory/auto‑move insight if desired as well as authorizing free API CASB.
121
+
[^2]: Still used for directory/auto‑move insight if desired as well as authorizing free API CASB.
122
+
123
+
Now that you know which deployment path to choose, you can begin your onboarding process.
0 commit comments