Mimecast

Anomali supports the ingestion of Mimecast logs through the Mimecast API 2.0 and AWS S3.

Version 2.0 API call

You can use your existing Mimecast Client ID and Client Secret or create them to add a new log source in the Anomali platform.

Onboarding steps

Prerequisites

Admin access to the Mimecast admin console.
The admin must be assigned a role with read and edit API app permissions.
Security permissions must permit the management of app roles.

See the Mimecast documentation on Managing API 2.0 and integrations for more information.

Step 1: Create custom API App

To create a custom API app, see the Mimecast guide to Creating an API 2.0 application.

Once you finish creating the app, the Mimecast console displays the Client ID and Client Secret. Securely store these details for the next step.

Step 2: Add Mimecast as new log source

To add Mimecast as a new log source on the Anomali platform:

Navigate to Search > Log Source Management.
Click New to add a new log source.
Enter a name for the log source.
(Optional) Enter a description for the log source.
Select Mimecast v2 as the source type.
Select API as the ingestion method.
Select API as the ingest method.
Provide the Basic Configuration details:
1. Client ID: Enter the Client ID to authenticate requests.
2. Client Secret: Enter the Client Secret to authenticate requests.
3. (Optional) TTP Attachment Logs: Select whether to collect these TTP attachment logs. Enabled by default.
4. (Optional) TTP URL Logs: Select whether to collect these TTP URL logs. Enabled by default.
5. (Optional) TTP Impersonation Logs: Select whether to collect these TTP impersonation logs. Enabled by default.
6. (Optional) Rejection Logs: Select whether to collect these rejection logs. Enabled by default.
7. (Optional) Threat Intel Feed: Select whether to collect these threat intel feed logs. Disabled by default.
8. (Optional) Ingestion Interval: Specify a number of minutes, hours, or days between API requests.
(Optional) Next to the Basic Configuration section, click on the Advanced Options link to provide additional information about the event log data:
1. Enter one or more parameters that provide additional context about the data. For example, "File format" indicates the format of the event log data being shipped, or "File extension" that indicates the extension of the logs.
2. Enter the corresponding value of the parameter. For example, CSV is a file format. Similarly, ".gzip" is a file extension.
Click Save to add the log source.

Step 3: Configure permissions

You can set permissions to decide which roles can view, add, or edit log sources. To do so, configure the following parameters:

Owner: Select an owner of the view from the list of users. This is the email address of the owner.
Type: Select the type of permission assigned to the view:
1. Private: Only the owner has read and write privileges, that is, no other user can access or edit the view.
2. Shared: Allows you to set the read-write privileges for a role that is mapped to different users, granting read-write permissions to all users assigned that role. You can also assign read or write permissions to everyone in your organization.

Step 4: Check log source status

Once added, the status of the log source becomes Create Requested. See Log Source Statuses to understand the different types statuses assigned to log sources.

Step 5: Receive confirmation email

You will receive a notification email from Anomali once you have created a new log source request. The Log Source Management page will show the status as Create Requested.

Once the log source has been provisioned and is ready for use, Anomali will send you another email and the Log Source Management page status for the log source will change to Active.

API 1.0 call

See Mimecast 1.0 documentation for more information on using ingesting logs using Mimecast API 1.0.

AWS S3

If your logs are already in S3, you can proceed directly to Step 2: Set up SQS queue. If not, Anomali recommends following Step 1: Ship data to S3 using NXLog to use NXLog to first ship the logs to S3. After S3 receives the data, it sends updates to an Amazon SQS queue you designate, enabling Anomali to automatically pull the logs from S3 whenever it receives a new notification from the queue.

Onboarding Steps

Step 1: Ship data to S3 using NXLog

See Using NXLog to Ship Data to set up NXLog to send data into S3.

Step 2: Set up SQS queue

Once your data is in S3, you can send it to Anomali using Amazon SQS. See Setting up Amazon SQS queue for more information.

Step 3: Enable AWS S3 notifications

Enable AWS S3 notifications for Amazon SQS to receive change notifications when you add logs. See Amazon's guide to configuring AWS S3 notification for SQS for more information.

Step 4: Add Mimecast as new log source

On the Anomali platform, add Mimecast as a new log source, as follows:

Navigate to Search > Log Source Management.
Click New to add a new log source.
Enter a name for the log source.
(Optional) Enter a description for the log source.
Select it as the log source.
Select AWS S3 as the ingest method.
Ensure S3 notification are enabled. See Step 2: Enable AWS S3 notifications for more information.
Provide the Basic Configuration details:
1. AWS SQS Queue URL: Enter the URL of your AWS SQS queue. See Setting up Amazon SQS queue for more information.
2. AWS Secret Access Key: Provide the AWS secret access key.
3. AWS Access Key ID: Enter the AWS Access ID.
4. File Selector: Provide the path to the event log data files. Anomali recommends the following practices for the path:

Sourcetype must be the path prefix, as follows:
<sourcetype>/year=2025/month=04/day=05/path/to/file.
For example: mimecast/year=2025/month=03/day=22/events/event_data_logs/.
Sourcetype name must not contain any spaces: For example, "mimecast" or "mimecast_sourcetype" are correct, however "mimecast sourcetype" is incorrect.

(Optional) Next to the Basic Configuration section, click on the Advanced Options link to provide additional information about the event log data:
1. Enter one or more parameters that provide additional context about the data. For example, "File format" indicates the format of the event log data being shipped, or "File extension" that indicates the extension of the logs.
2. Enter the corresponding value of the parameter. For example, CSV is a file format. Similarly, ".gzip" is a file extension.
Click Save to add the log source.

Step 5: Configure permissions

You can set permissions to decide which roles can view, add, or edit log sources. To do so, configure the following parameters:

Owner: Select an owner of the view from the list of users. This is the email address of the owner.
Type: Select the type of permission assigned to the view:
1. Private: Only the owner has read and write privileges, that is, no other user can access or edit the view.
2. Shared: Allows you to set the read-write privileges for a role that is mapped to different users, granting read-write permissions to all users assigned that role. You can also assign read or write permissions to everyone in your organization.

Step 6: Check log source status

Once added, the status of the log source becomes Create Requested. See Log Source Statuses to understand the different types statuses assigned to log sources.

Step 7: Receive confirmation email

You will receive a notification email from Anomali once you have created a new log source request. The Log Source Management page will show the status as Create Requested.

Once the log source has been provisioned and is ready for use, Anomali will send you another email and the Log Source Management page status for the log source will change to Active.