Safelisting in Mimecast

Overview

If you’re using Mimecast security software, you can safelist PhishingBox to allow your users to receive our simulated phishing emails and system emails.

Jump to a section by clicking one of the following links:

1. Creating a Permitted Senders Policy
2. Greylisting in Mimecast
3. Creating an Anti-Spoofing Policy
4. Creating an Impersonation Protection Bypass Policy
5. Creating an Attachment Protection Bypass Policy

The below section is necessary only if the associated package is activated:

• URL Protection Bypass Policy

Please allow each rule some time to propagate before testing. If you run into problems while safelisting in Mimecast, we suggest you first reach out directly to Mimecast for assistance.

Creating a Permitted Senders Policy

We advise creating a new Permitted Sender Policy within your Mimecast console in order to safelist PhishingBox.

WARNING: Do not edit your default Permitted Sender Policy. Instead, create a new one.

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Select Gateway | Policies.
3. Select Permitted Senders.
4. Select New Policy.
5. Select the below settings under the Options, Emails From, Emails To, and Validity sections. For more information, see Mimecast's Configuring a Permitted Senders Policy.
6. Enter PhishingBox's IP Address in the Source IP Ranges field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top

Greylisting in Mimecast

Adding PhishingBox to the permitted senders list (see above) should bypass Greylisting. However, we recommend following the below Greylisting steps to improve email deliverability.

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Select Gateway | Policies.
3. Select Greylisting.
4. Click the New Policy button.
5. Select the below settings under the Options, Emails From, Emails To, and Validity sections.
6. Enter PhishingBox's IP Address in the Source IP Ranges Field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top

Creating an Anti-Spoofing Policy

If you're spoofing the From or Reply-to domain on your template, then follow the below steps in Mimecast to allow simulated phishing emails to be sent from your domain.

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Select Gateway | Policies.
3. Select Anti-Spoofing from the policies list.
4. Select New Policy.
5. Use the below settings under the Options, Emails From, Emails To, and Validity sections. For more information, read this article from Mimecast: Configuring an Anti-Spoofing Policy.
6. Enter PhishingBox's IP Address in the Source IP Ranges Field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top

Creating an Impersonation Protection Bypass Policy

To allow PhishingBox simulated phishing emails that are from spoofed domains to reach your targets, you will want to create an Impersonation Protection Policy as well as an Anti-Spoofing Policy in the Mimecast Console. 

To begin, you’ll need to make an impersonation protection definition (if not already done).

How to Create an impersonation protection definition

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Choose Gateway | Policies.
3. Hover over Impersonation Protection and click on Definitions.
4. Click New Definition.
5. Name the definition something unique, like "Portal Impersonation Protection Bypass Def."
6. Choose the relevant settings (shown below). For more information, see Mimecast's documentation in this article: https://community.mimecast.com/docs/DOC-1908#jive_content_id_Configuring_an_Impersonation_Protection_Definition.

How to Create an Impersonation Bypass Policy

1. First, log into your Mimecast Administration Console.
2. Click on Administration toolbar.
3. Select Gateway | Policies.
4. Select Impersonation Protection Bypass.
5. Click on the New Policy button.
6. Select the appropriate policy settings under the Options, Emails From, Emails To, and Validity sections. For more information on these settings, see Mimecast's Configuring an Impersonation Protection Bypass Policy article.
   

   NOTE: In the Select Option field under Options, select the impersonation protection definition you want to be bypassed. If you have multiple definitions you would like to bypass, you will need to create a separate Impersonation Protection Bypass Policy for each one.

7. Enter PhishingBox's IP Address in the Source IP Ranges field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top

Creating an Attachment Protection Bypass Policy

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Click the Administration toolbar button.
3. Select Gateway | Policies.
4. Select Attachment Protection Bypass.
5. Click the New Policy button. 
6. Select the appropriate policy settings under the Options, Emails From, Emails To, and Validity sections. For more information on these settings, see Mimecast's Configuring an Impersonation Protection Bypass Policy article.
7. Enter PhishingBox's IP Address in the Source IP Ranges field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top

URL Protection Bypass Policy

Mimecast's URL Protection service scans links sent within emails as they are delivered. Occasionally, this causes simulated phishing emails to trigger this service. Follow the below steps to create a URL Protection Bypass policy.

NOTE: Configuring this policy is only necessary if Mimecast URL Protection has been enabled.

1. From the Mimecast Administration console, open the Administration Toolbar.
2. Select Gateway | Policies.
3. Select URL Protection Bypass.
4. Select New Policy.
5. Select the appropriate settings (below) under the Options, Emails From, Emails To, and Validity sections. For more information, see Mimecast's article on Configuring a URL Protection Bypass Policy.
6. Enter PhishingBox's IP Address in the Source IP Ranges field. (You can find a list of IP addresses in our Safelisting Basics article.)

Back to top