Skip to content

Commit aba2fee

Browse files
Update heading
1 parent 8a76208 commit aba2fee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/prerequisites/gsuite-email-security-mx.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ If desired, you can create a separate quarantine for each of the dispositions.
6666

6767
<Render file="email-security/deployment/set-up-mx-inline-step"/>
6868

69-
## 5. (Recommended) Secure your email flow
69+
## 5. (Recommended) Secure Google Workspace from MX records bypass
7070

7171
One method of DNS attacks is to search for old MX records and send <GlossaryTooltip term="phishing">phishing</GlossaryTooltip> emails directly to the mail server. To secure the email flow, you will want to enforce an email flow where inbound messages are accepted by Google Workspace only when they originate from Email Security. This can be done by adding a connector to only allow email from Email Security with TLS encryption. This step is optional but recommended.
7272

0 commit comments

Comments
 (0)