Skip to content

Commit e212469

Browse files
[Email Security (formerly Area 1)] Restructure Gmail BCC setup and retraction
1 parent 49f6911 commit e212469

File tree

7 files changed

+126
-13
lines changed

7 files changed

+126
-13
lines changed
Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
title: Find BCC address and add domain
3+
pcx_content_type: how-to
4+
sidebar:
5+
order: 2
6+
---
7+
8+
import { Render } from "~/components"
9+
10+
:::caution[Area 1 has been renamed]
11+
<Render file="rename-area1-to-ces" />
12+
:::
13+
14+
To set up Email Security (formerly Area 1) phishing risk assessment for Gmail:
15+
16+
1. Log in to the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/).
17+
2. Select the question mark, where you will be able to find your BCC address.
18+
3. Once you found your address, select **Settings** (the gear icon), then select **New Domain**.
19+
4. Fill in the information needed to add your domain, then select **Publish Domain**.
20+
21+
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: Add retraction
3+
pcx_content_type: how-to
4+
sidebar:
5+
order: 5
6+
---
7+
8+
import { Render } from "~/components"
9+
10+
1. On the [Email Security (formerly Area 1) dashboard](https://horizon.area1security.com/), select **Domains** under **DOMAINS & ROUTING**, then select **NEW DOMAIN**. Fill in the information to add a new domain:
11+
- On **FORWARDING TO**: Enter **Google.com**.
12+
- Adjust **Hops** to 2.
13+
- On **Outbound TLS**: Ensure you select **Forward all messages over TLS**.
14+
2. Select **Publish Domain**.
15+
3. Select **RETRACT SETTINGS** > **Authorize Gmail**.
16+
4. Upload the JSON file [previously generated](/email-security/deployment/api/setup/gsuite-bcc-setup/create-service-account/).
17+
5. Under **DOMAINS**, select the domain you added previously, then select **SAVE**.
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
title: Add BCC rules to Area 1
3+
pcx_content_type: how-to
4+
sidebar:
5+
order: 3
6+
---
7+
8+
import { Render } from "~/components"
9+
10+
1. In the [Google Admin console](https://admin.google.com/), go to **Menu** > **Apps** > **Google Workspace** > **Gmail** > **Compliance**.
11+
2. Go to **Content Compliance** > Select **Edit**.
12+
3. Add a **Content Compliance** filter, and name it `Email Security (Area 1) - BCC`.
13+
4. In **Email messages to affect**, select **Inbound**.
14+
5. Select the recipients you want to send emails to Area 1 via BCC:
15+
1. Select **Add** to configure the expression.
16+
2. Select **Advanced content match**.
17+
3. In **Location**, select **Headers + Body**.
18+
4. In **Match type**, select **Matches regex**.
19+
5. In **Regexp** input `.*`. You can customize the regex as needed and test within the admin page or on sites like [Regexr](https://regexr.com/).
20+
6. Select **SAVE**.
21+
6. In **If the above expressions match, do the following**, select **Modify message**, select **Add more recipients** > Select **ADD** > Choose **Advanced**:
22+
1. Under **Envelope recipient**, select **Change envelope recipient** > **Replace recipient** > Enter the email of the recipient.
23+
2. Under **Spam and delivery options**, select **Suppress bounces from this recipient**.
24+
3. Under **Headers**, select **Add X-Gm-Spam and X-Gm-Phishy headers**.
25+
4. Select **SAVE**.
26+
7. In **Account types to affect**, select **Users** and **Groups**.
27+
8. Select **SAVE**.
28+
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
title: Create a project on Google Cloud Console
3+
pcx_content_type: how-to
4+
updated: 2022-10-11
5+
sidebar:
6+
order: 4
7+
---
8+
9+
import { Render } from "~/components"
10+
11+
1. Log in to the [Google Cloud Console](https://console.cloud.google.com/welcome/new). From the dashboard, select **CREATE OR SELECT PROJECT**.
12+
2. Provide the details for the new project, and select **CREATE** to start your new project.
13+
3. Once the new project has been created, the Google Cloud Platform console will automatically redirect you to the Project console. If not, you can use the Project selector to change to the project you created.
14+
4. In **Getting Started**, select **Explore and enable APIs** > Select **ENABLE APIs & SERVICES**.
15+
5. On search bar, search for "Admin SDK API". Select **Admin SDK API**, then select **ENABLE**.
16+
6. Go back to the sidebar, select **Library**, and search for Gmail API. Select **Gmail API**, then select **ENABLE**.
Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
title: Create service account
3+
pcx_content_type: how-to
4+
updated: 2022-10-11
5+
sidebar:
6+
order: 4
7+
---
8+
9+
import { Render } from "~/components"
10+
11+
1. On the [Google Cloud Console](https://console.cloud.google.com/welcome/new), select **Credentials**.
12+
2. Select **CREATE CREDENTIALS** > **Service account**.
13+
3. Fill in the details to create a service account:
14+
- **Service account name**: Enter **Message Retraction Service Account**.
15+
- **Service account ID**: Enter **message-retraction-service-acc**.
16+
- **Service account description**: Enter **Email Security Message Retraction**.
17+
- Select **CREATE AND CONTINUE**.
18+
4. In **Grant this service account access to project**, select **Select a role** > Choose **Owner**. Select **CONTINUE**, then **DONE**.
19+
5. Go back to **Credentials**, and select your service account under **Service Accounts**. In **Details**, take note of the **Unique ID**.
20+
6. Select **Advanced settings** > **VIEW GOOGLE WORKSPACE ADMIN CONSOLE**, then enter your password.
21+
7. On the sidebar, select **Security** > **Access and data control** > **API controls** > Select **MANAGE DOMAIN WIDE DELEGATION**.
22+
8. Select **Add new** > Add a new client ID:
23+
- **Client ID**: Enter the **Unique ID** you took note of.
24+
- **OAuth scopes**: Enter the following URL:
25+
26+
```txt
27+
https://www.googleapis.com/auth/admin.directory.user.readonly, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.alias.readonly, https://www.googleapis.com/auth/gmail.labels, https://mail.google.com/
28+
```
29+
- Select **AUTHORIZE**.
30+
31+
9. Go back to the sidebar > **Service Accounts**.
32+
10. Select the three dots > **Manage keys** > **ADD KEY** > **Create new key** > Select **JSON** > Select **CREATE**. This downloads a `.json` file which you will use at a later stage.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
title: Geographic locations
3+
pcx_content_type: reference
4+
sidebar:
5+
order: 6
6+
---
7+
8+
import { Render } from "~/components"
9+
10+
<Render file="deployment/bcc-table-geographic-locations" />
Lines changed: 2 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: Gmail BCC setup
33
pcx_content_type: integration-guide
4-
updated: 2022-10-11
54
sidebar:
65
order: 1
76
head:
@@ -11,24 +10,14 @@ head:
1110

1211
---
1312

14-
import { Render } from "~/components"
13+
import { Render, Details } from "~/components"
1514

1615
:::caution[Area 1 has been renamed]
1716

18-
1917
<Render file="rename-area1-to-ces" />
2018

21-
2219
:::
2320

2421
For customers using Gmail, setting up Email Security via BCC is quick and easy. All you need to do is create a content compliance filter to send emails to Email Security through BCC. The following email flow shows how this works:
2522

26-
![Email flow when setting up a phishing assessment risk for Gmail with Email Security.](~/assets/images/email-security/deployment/api-setup/gmail/gmail-bcc-flow.png)
27-
28-
To setup Email Security (formerly Area 1) phishing risk assessment for Gmail:
29-
30-
<Render file="deployment/gmail-bcc-setup" />
31-
32-
## Geographic locations
33-
34-
<Render file="deployment/bcc-table-geographic-locations" />
23+
![Email flow when setting up a phishing assessment risk for Gmail with Email Security.](~/assets/images/email-security/deployment/api-setup/gmail/gmail-bcc-flow.png)

0 commit comments

Comments
 (0)