Mimecast API 2.0

Configure the Mimecast API 2.0 data connector.

In this guide, you'll configure the integration between Radiant and Mimecast. Adding this data connector gives your organization visibility into phishing links accessed from unmanaged devices. With this data, Radiant Security can detect users who clicked on malicious links from personal devices, enabling deeper investigations and uncovering the full scope of an incident.

At the end of this configuration, you will provide Radiant Security with these values:

• Client ID
• Client Secret

Available actions

The following actions are available after you set up the Mimecast data connector. Keep in mind, additional permissions are required.

• Block Sender
• Block URLs

Prerequisites

Admin access to Mimecast, with a Role that grants:

• Read and Edit API Application Permissions under the Service Menu
• Security Permissions setting must permit the Management of Application Roles

Create the custom role

1. Log in to your Mimecast console with an admin account.
2. In the menu, click Account, then select Roles.
3. Click New Role, set the Name and Description as Radiant Security API 2.0.
4. On Security Permissions, select Cannot Manage Roles.
5. On Application Permissions, leave the following settings enabled:

   • Account Menu | Logs | Read
   • Gateway Menu | Policies | All
   • Gateway Menu | Managed Senders | All
   • Services Menu | URL Protection | All
   • Directories | Groups | All
   • Monitoring Menu | URL Protection | All
   • Directories Menu | Managed Senders | All (in case it exists on the UI)
6. Click Save and Exit.

Configure the Mimecast API

1. Log in to your Mimecast console with an admin account.

1. In the administration menu, click Services, then select API and Platform Integrations.
2. Under Mimecast API 2.0, click Generate Keys.

1. On Application Details, fill the form with the following values:

   • Application Name: Radiant Security API 2.0
   • Category: Others
   • Products: Select the following entries:

     • Email Security Cloud Gateway
     • Policy Management
     • Threat Management
     • Audit Events
     • Security Events
     • User and Group Management
   • Application Role: Radiant Security API 2.0
   • Description: Radiant Security API 2.0 Connector

1. Click Next.
2. Fill in the following values:

   • Technical Point of Contact: <internal user responsible for managing the integration>
   • Email: <associated email of the technical point of contact>
3. Click Next.
4. Confirm the values in the summary.
5. The wizard completes and displays a pop-up window including your Client ID and Client Secret, where you can copy and save the credentials for the API application.

1. Copy the application values for:

• Client ID
• Client Secret

Important note: Be sure to document and store the Client ID and Client Secret carefully, as they cannot be retrieved later. Also, remember to label which is which, as these will need to be provided to Radiant Security later.

Add the data connector in Radiant Security

1. Log in to Radiant Security.
2. From the navigation menu, select Settings > Data Connector and click + Add Connector.
3. Search for and select the Mimecast option from the list and then click Data Feeds.
4. Under Select your data feeds, select the URL Protection click Credentials.
5. Under Credential Name, give the credential an identifiable name (e.g. Mimecast Credentials).
6. Under Required Credentials, add the Client ID and the Client Secret Token that you copied from the previous section.
7. Click Add Connector to save the changes.

Add the action connector in Radiant Security

1. From the navigation menu, select Settings > Action Connectors and click + Add Connector to create a new action connector.
2. Select the Mimecast API 2.0 connector and click Credentials.
3. Select the credential for the data connector that you created previously from the drop-down menu.
4. Click Add Connector to save your changes.

Verify ingestion

After Mimecast begins forwarding, confirm events are reaching Radiant.

1. In Radiant, navigate to Log Management.
2. Filter by rs_connectorType:"mimecast_url_protection_api_v2".
3. Confirm recent events appear.

Allow several minutes for events to be parsed, indexed, and available for search.