Mimecast is a cloud-based, anti-spam, and archive filtering service for securing email accounts and communications for businesses. This collector protects an enterprise’s email infrastructure from viruses, malware, phishing, and the rise of deep-fake attacks. It also makes it possible to automate the recovery of archived and affected emails for continuous use. It can predict and anticipate attacks and deal with losses from ransomware attacks using data archiving.
The Devo Mimecast Collector uses the Mimecast API to extract all the relevant information and send it as events to Devo.
For more information on how the events are parsed, visit our page.
Vendor setup
There are some requirements to configure the Mimecast collector:
Accessing your API applications.
Creating user API keys. Refer to the Mimecast official documentation for more information.
Access your API applications
Log in to the Administration Console.
Click on the Administration toolbar button.
Select the Services/API and Platform Integrations menu item.
Once your API applications display you can:
Add an application.
Edit an application.
Delete an application.
Refer to the Mimecast official documentation for more information.
Create API keys
Scroll to the middle of API Concepts for detailed instructions.
Authentication
The Mimecast Collector API 2.0 needs two keys that the API uses:
Client ID (client_id).
Client secret (client_secret)
Credentials
Steps and information to generate these keys can be found in this article.
Permissions
Each API call has a prerequisite section that tells you what permissions are needed for the call. Usually, a basic administrator role will be enough, which should allow you to use the same API keys generated for multiple API calls under the application.
If you want to create a custom administrative role for this API service account user, follow these steps:
Navigate to Administration → Account → Roles.
Click New Role.
Enter a Role Nameand Description.
In the Application Permissions section, select the boxes for each required role to be used by the service user account.
Click Save and Exit.
Locate the newly created role and click on the role name.
Click Add User to Role.
Select the email address of the API service user account.
If you want to add the service account user to an existing role:
Navigate to Administration → Account → Roles.
Click on the administrator role the user will be added to.
Click Add User to Role.
Select the email address of the API service user account.
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
