Brand Exploit Protect - Integration With Mimecast API 2.0 - Jun 2025

Service Update

Availability	June 17th, 2025
Product(s)	Brand Exploit Protect (BEP)
Who's affected	Brand Exploit Protect, Administrators

Overview

Mimecast is pleased to announce the enhanced version of Brand Exploit Protect (BEP), which enables administrators to seamlessly integrate it with the Mimecast API 2.0.

Mimecast API 1.0 will remain unchanged and continue to be available through our API and Platform Integrations.

What's changing

• We will be deleting all BEP system-related API keys on the 20th of July. Customers should familiarize themselves with the steps for creating new API keys for version 2.0 in the Mimecast Administrator Console, as well as how to insert them into BEP.
• Successful integration enables the blocking of suspicious domains and URLs using BEP.

A toast message will appear in the user interface after a customer updates their keys. It will be shown to all Mimecast API users and will disappear for everyone at the same time.

Recommended actions

To set up API 2.0, please follow the detailed steps outlined in the configuration guide below:
 

Configuring Mimecast API 2.0

Mimecast Administration Console

1. Log on to the Mimecast Administration Console.
2. Navigate to Integrations | API and Platform Integrations | Mimecast API 2.0.
3. Click on the box below to accept Application Program Interface Terms and Conditions.
4. Enter Application name, Category,  Products, Application Role, and Description. Then click Next.

Field/Option	Description
Products	The product permissions granted for these API keys. We need the following: User and Group Management Policy Management
Application Role	Basic Administration

5. In the notification settings, enter the Technical point of contact and Email.
6. Review your information, click Add, and Generate Keys.
7. Copy the Client ID and Client Secret key to a safe place, e.g., a secure Password Management system. The secret key will be needed during the BEP integration with the Mimecast API 2.0.

The API credentials will be displayed on your screen. These secrets should be handled carefully and not stored as plain text or sent through any communication channels, as they provide access to your account.

If these steps are completed before enabling API 2.0 integration in BEP, store the credentials in a secret manager until the integration is enabled, or discard them at that moment. You will be able to generate new keys for this integration as needed.

Re-Generate API 2.0 Application Keys

In case you need to re-generate your API keys:

1. Navigate to Services | Your API 2.0 Applications | Select and click your desired application.
2. A pane will appear with the integration details. Click the Manage API 2.0 Credentials.

A warning message will be displayed. Notifying that this action will invalidate your existing keys. While it will not alter any current policies configured by BEP, it will prevent you from making any new changes to your policy until the new keys are provided.

3. To continue, click on the Generate button.
4. The new credentials will be displayed, allowing you to copy them into BEP.

Brand Exploit Protect

1. Log on to Brand Exploit Protect.
2. Navigate to Settings | General.
3. On the Mimecast Integration widget, click Edit.
4. Enter the Client ID and Client Secret key credentials from the Mimecast Administration Console BEP 2.0 and click the Test New Key button.

5. After receiving a success message, click the Save button to securely store the credentials in BEP.

If there is an error, try pressing the button again to see if it persists. Sometimes, a network issue may cause the test to fail temporarily.

See Also...

• Brand Exploit Protect - Integration With Mimecast API 2.0
• Managing API Applications