> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/connect-your-technology/l-p-integrations/mimecast-advanced-email-security-setup-for-workbench.md).

# Mimecast Advanced Email Security Setup for Workbench

This integration allows Expel to apply our detection strategy to Mimecast Targeted Threat Protection (TTP) alerts and pull them into the Workbench queue for investigation and remediation.

## Prerequisites <a href="#h_01kmk36pna9vdhxsj9dpyndvm7" id="h_01kmk36pna9vdhxsj9dpyndvm7"></a>

1. You must have the [Organization Admin role](/workbench-setup/get-started/add-and-manage-users/user-role-rights.md) in Workbench to set up this integration.
2. You must have a Mimecast administrator account with permissions to create API 2.0 Applications and manage Roles.
3. Your organization must have Mimecast Targeted Threat Protection (TTP) enabled for at least one of the following: URL Protect, Attachment Protect, or Impersonation Protect.

## Step 1: Create a Custom Role for the Expel Integration <a href="#h_01kmk385vznq68hw032em96z2n" id="h_01kmk385vznq68hw032em96z2n"></a>

Mimecast recommends creating a dedicated custom role with only the permissions required for the integration.

1. Log in to the [Mimecast Administration Console](https://login.mimecast.com/admin).
2. Navigate to **Account > Admin Roles**.
3. Select **New Role**.
4. Configure the role as follows:
   1. **Role Name** - enter "Expel Integration Role".
   2. **Description** - enter "Role for Expel integration".
   3. **Cannot Manage Roles** - leave **selected**.
   4. **Application Permissions** - ensure the following required permissions are selected. *If your organization does not have all TTP products enabled, you only need to grant permissions for the products you have.*

| Permission                                                 | Purpose                                               |
| ---------------------------------------------------------- | ----------------------------------------------------- |
| **Monitoring Menu > URL Protection > Read**                | Allows retrieval of TTP URL click protection logs     |
| **Monitoring Menu > Attachment Protection > Read**         | Allows retrieval of TTP attachment sandbox logs       |
| **Monitoring Menu > Impersonation Protection Logs > Read** | Allows retrieval of TTP impersonation protection logs |

5. Select **Save and Exit**.

## Step 2: Create an API 2.0 Application in Mimecast <a href="#h_01kmk44zscfye536sf4wxx1n43" id="h_01kmk44zscfye536sf4wxx1n43"></a>

Next, you will create an API 2.0 Application to generate the Client ID and Client Secret that Expel uses to authenticate.

1. In the Mimecast Administration Console, navigate to **Integrations > API and Platform Integrations**.
2. Select the **Available Integrations** tab.
3. Locate the **Mimecast API 2.0** tile and select **Generate Keys**.<br>

   <div align="left"><figure><img src="https://2371323735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F82234aPbNfd179j5U4ti%2Fuploads%2FjLArx71rEJZz5AVcnKnL%2Fmimecast-api2-generatekeys.png?alt=media&amp;token=24453b8a-2354-495b-9e6e-724f4627df05" alt="Mimecast API 2.0 option." width="375"><figcaption></figcaption></figure></div>
4. Select **Create New Integration**.
5. If applicable, read the Terms & Conditions and select **I accept**.
6. Complete the Details section as follows:
   * **Application Name** - enter "Expel Integration".
   * **Products** - Select **Select All** (or choose the specific TTP products you have enabled)
   * **Application Role** - Select "**Expel Integration Role**" (the role you created in Step 1).
   * **Description** - enter "Expel API Integration."
7. In **Notification Settings**, provide a point of contact name and email address. Mimecast uses this to notify you about API updates or issues.
8. Scroll to the top of the page and select **Save**.
9. A dialog displays confirming the credentials were created successfully. **Copy and save the Client ID and Client Secret** to a safe place for use in the next step. *The Client Secret is only displayed once. If you lose these credentials, you must generate new ones.*

## Step 3: Add Mimecast as a Security Device in Workbench <a href="#h_01kmk4d06ezf6mw75hqeyg1bnb" id="h_01kmk4d06ezf6mw75hqeyg1bnb"></a>

Now that you have your API credentials, you can configure the integration in Workbench.

1. [Log in to Workbench](https://workbench.expel.io/auth/login?orig=%2F).
2. In the side menu, navigate to **Organization Settings > Security Devices**.
3. Select **Add Security Device**.
4. In the search box, type “Mimecast” and then select the **Mimecast** integration.<br>

   <div align="left"><figure><img src="https://2371323735-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F82234aPbNfd179j5U4ti%2Fuploads%2FibLRJilWRYHuWohBJ2AI%2FWB_mimecast_securitydevice.png?alt=media&amp;token=851c6f91-e552-4ba0-8814-71f18ca0fb02" alt="Mimecast Add a Security Device screen in Workbench." width="326"><figcaption></figcaption></figure></div>
5. A configuration pane displays. Complete the fields as follows:
   1. **Name** - enter a name that might help you more easily identify this integration, such as “CompanyName Mimecast”; this name will display in Workbench under the Name column, and is a text string that you can filter on.
   2. **Location** - enter the location of your integration, for example “cloud.” This is also a text string that you can filter on, so we recommend being consistent with location naming across your Expel integrations.
   3. **Server URL -** enter the Mimecast API base URL for your region:
      * **Global (recommended)** - `https://api.services.mimecast.com`
      * **U.S. Regional** - `https://us-api.services.mimecast.com`
      * **U.K. Regional** - `https://uk-api.services.mimecast.com`\
        *The Global URL automatically routes traffic to the nearest Mimecast instance. Use regional URLs only if you have specific compliance or data residency requirements.*&#x20;
   4. **Client ID** - enter the Client ID from [Step 2](#h_01kmk44zscfye536sf4wxx1n43).
   5. **Client secret** - enter the Client Secret from [Step 2](#h_01kmk44zscfye536sf4wxx1n43).
6. Select **Save**.
7. On the console access screen, select **No thanks, I will not provide console access** from the dropdown.
8. Select **Save**.

Your device should be created successfully within a few seconds. A few reminders:

* After your connection is healthy, it will take some time for your device to begin polling and receiving data.
* To check on the status, select the downward arrow for your device in the first column and choose **View details**.
* Polling will happen first; data will be received after that. **You must refresh the page to see updates.**
* If your device does not begin polling within 15 minutes, and does not begin receiving data within 30 minutes, [contact our support team for help](/support/how-to-reach-us.md).
* To check if alerts are coming through, navigate to **Dashboards > Alert Analysis**. Scroll to the device you want to check, and select the **Expel Alerts** tab to reveal more alert information. It can take 36 to 72 hours for alerts to appear after setup, as we [tune your device](/workbench-reference/alerts/how-expel-alerts-work.md#device-tuning).

## Step 4: (Optional) Set Up Auto Email Deletion <a href="#h_01jsq7m96qw55b6v8gsp1nkw6c" id="h_01jsq7m96qw55b6v8gsp1nkw6c"></a>

The preceding steps of this guide enable Expel to ingest Mimecast alerts and investigate any malicious activity. This optional configuration lets us use detection strategy to immediately delete any email that Mimecast identifies as malicious *as soon as we ingest its associated alert*.

This means those emails will be assumed as correctly flagged by Mimecast as malicious, and then deleted for every email user without a SOC investigation. We will instead focus all of our SOC efforts on other types of Sublime Security alerts. However, the Mimecast alert that references the deleted email will still be available to our SOC analysts and can be correlated to other suspicious activity where needed.

[Learn more about how remediation works](/connect-your-technology/about-integrations/about-mdr-for-email.md#h_01jrjp0rrke00fk9dm80bevyg8) in this process.

{% hint style="warning" %}
You must have Microsoft 365 or Google Workspace as your email provider to use this feature.
{% endhint %}

### Step 1: Enable Permissions in Your Email Provider

1. Set up appropriate permissions within your email provider by selecting one of the links below for instructions.\
   ***If you have already enabled the Remove Malicious Email auto remediation in support of a different integration, you can skip this step (because you will have already set this part up).***
   * [Microsoft 365](/workbench-setup/auto-remediations/remove-malicious-email/microsoft-365-remove-malicious-email.md#step-2-add-an-additional-api-permission): Follow *only* the Step 2 section of this guide, then return to this page and continue to step 2.&#x20;
   * [Google Workspace](/workbench-setup/auto-remediations/remove-malicious-email/google-workspace-formerly-g-suite-remove-malicious-email.md#h_01jh5zgcgw8ekzjnfd2tzwjvat): Follow *only* the Step 1 and Step 2 sections of this guide, then return to this page and continue to step 2.&#x20;

### Step 2: Enable the Auto Remediation in Workbench

1. Contact your Customer Success Manager (CSM) and ask that they enable the **Auto-Remediate Suspicious Delivered Email Alerts** (`org.preference.email.auto_remediate_delivered`) value in Workbench.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.expel.io/connect-your-technology/l-p-integrations/mimecast-advanced-email-security-setup-for-workbench.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.