Skip to content

Commit b040a84

Browse files
Apply suggestions from code review
Co-authored-by: Pedro Sousa <[email protected]>
1 parent cb06e69 commit b040a84

File tree

2 files changed

+34
-6
lines changed

2 files changed

+34
-6
lines changed

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

Lines changed: 27 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,17 +24,41 @@ In this tutorial, you will learn how to configure Google Workspace with Email Se
2424

2525
## 1. Set up Inbound Email Configuration
2626

27-
Set up [Inbound Email Configuration](https://support.google.com/a/answer/60730?hl=en) with the following details: - In **Gateway IPs**, select the **Add** link, and add the IPs mentioned in [Egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips/). - Select **Automatically detect external IP (recommended)**. - Select **Require TLS for connections from the email gateways listed above**. - Do not select **Reject all mail not from gateway IPs**. You will enable this option at a later time to ensure your mail flows. - Select **SAVE**.
27+
Set up [Inbound Email Configuration](https://support.google.com/a/answer/60730?hl=en) with the following details:
28+
29+
- In **Gateway IPs**, select the **Add** link, and add the IPs mentioned in [Egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/egress-ips/).
30+
- Select **Automatically detect external IP (recommended)**.
31+
- Select **Require TLS for connections from the email gateways listed above**.
32+
- Do not select **Reject all mail not from gateway IPs**. You will enable this option at a later time to ensure your mail flows.
33+
- Select **SAVE**.
2834

2935
## 2. (Optional) Set up an email quarantine
3036

31-
[Set up an email quarantine](https://support.google.com/a/answer/6104172?hl=en#:~:text=Sign%20in%20with%20an%20administrator,t%20access%20the%20Admin%20console.&text=Manage%20quarantines.,Click%20Add%20Quarantine.) with the following details: - **Name**: Email Security Malicious. - **Description**: Email Security Malicious. - For the **Inbound denial consequence**, select **Drop message**. - For the **Outbound denial consequence**, select **Drop message**. - Select **SAVE**.
37+
[Set up an email quarantine](https://support.google.com/a/answer/6104172?hl=en#add-new-quarantine) with the following details:
38+
39+
- **Name**: Email Security Malicious.
40+
- **Description**: Email Security Malicious.
41+
- For the **Inbound denial consequence**, select **Drop message**.
42+
- For the **Outbound denial consequence**, select **Drop message**.
43+
- Select **SAVE**.
3244

3345
To access the newly created quarantine, select **GO TO ADMIN QUARANTINE** or access the quarantine directly by pointing your browser to https://email-quarantine.google.com/adminreview.
3446

3547
## 3. (Optional) Create a content compliance filter
3648

37-
Go to **Compliance**, and create a [content compliance filter](https://support.google.com/a/answer/1346934?hl=en#zippy=%2Cstep-go-to-gmail-compliance-settings-in-the-google-admin-console%2Cstep-enter-email-messages-to-affect) to send malicious messages to quarantine. Enter the following details: - **Content compliance**: Add `Quarantine Email Security Malicious`. - **Email messages to affect**: Select **Inbound**. - **Add expressions that describe the content you want to search for in each message**: - Select **Add** to add the condition. - In **Simple content match**, select **Advanced content match**. - In **Location**, select **Full headers**. - In **Match type**, select **Contains text**. - In **Content**, enter `X-CFEmailSecurity-Disposition: MALICIOUS`. - Select **SAVE** to save the condition. - If the above expression match, do the following, select **Quarantine message** and the **Email Security Malicious** quarantine that was created in the previous step. - Select **SAVE**.
49+
Go to **Compliance**, and create a [content compliance filter](https://support.google.com/a/answer/1346934?hl=en#zippy=%2Cstep-go-to-gmail-compliance-settings-in-the-google-admin-console%2Cstep-enter-email-messages-to-affect) to send malicious messages to quarantine. Enter the following details:
50+
51+
- **Content compliance**: Add `Quarantine Email Security Malicious`.
52+
- **Email messages to affect**: Select **Inbound**.
53+
- **Add expressions that describe the content you want to search for in each message**:
54+
- Select **Add** to add the condition.
55+
- In **Simple content match**, select **Advanced content match**.
56+
- In **Location**, select **Full headers**.
57+
- In **Match type**, select **Contains text**.
58+
- In **Content**, enter `X-CFEmailSecurity-Disposition: MALICIOUS`.
59+
- Select **SAVE** to save the condition.
60+
- If the above expression match, do the following, select **Quarantine message** and the **Email Security Malicious** quarantine that was created in the previous step.
61+
- Select **SAVE**.
3862

3963
If you would like to quarantine the other dispositions, repeat the above steps and use the following strings for the other dispositions:
4064

src/content/docs/cloudflare-one/identity/devices/access-integrations/mutual-tls-authentication.mdx

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,13 @@ The mTLS certificate is used only to verify the client certificate. It does not
5454
9. If this is for a client who does not need to log in through an IdP, set the policy **Action** to _Service Auth_.
5555

5656
<Example>
57-
**Example mTLS policy** | Action | Rule type | Selector | Value | | ------
58-
| --------- | -------- | ----------------- | | Service Auth | Include |
59-
Common Name | `John Doe` |
57+
58+
**Example mTLS policy**
59+
60+
| Action | Rule type | Selector | Value |
61+
| ------------ | --------- | ----------- | ---------- |
62+
| Service Auth | Include | Common Name | `John Doe` |
63+
6064
</Example>
6165

6266
10. Save the policy, then go to **Access** > **Applications**.

0 commit comments

Comments
 (0)