Mimecast Secure Email Gateway

>**NOTE:** This connector uses Azure Functions to connect to a Mimecast API to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) for details.

>**(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.

Configuration:

**STEP 1 - Configuration steps for the Mimecast API** Go to ***Azure portal ---> App registrations ---> [your_app] ---> Certificates & secrets ---> New client secret*** and create a new secret (save the Value somewhere safe right away because you will not be able to preview it later)

**STEP 2 - Deploy Mimecast API Connector** >**IMPORTANT:** Before deploying the Mimecast API connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Mimecast API authorization key(s) or Token, readily available.

Workspace ID

Primary Key

Deploy the Mimecast Secure Email Gateway Data Connector:

1. Click the **Deploy to Azure** button below. [](https://aka.ms/sentinel-MimecastSEG-azuredeploy) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the following fields: - appName: Unique string that will be used as id for the app in Azure platform - objectId: Azure portal ---> Azure Active Directory ---> more info ---> Profile -----> Object ID - appInsightsLocation(default): westeurope - mimecastEmail: Email address of dedicated user for this integraion - mimecastPassword: Password for dedicated user - mimecastAppId: Application Id from the Microsoft Sentinel app registered with Mimecast - mimecastAppKey: Application Key from the Microsoft Sentinel app registered with Mimecast - mimecastAccessKey: Access Key for the dedicated Mimecast user - mimecastSecretKey: Secret Key for dedicated Mimecast user - mimecastBaseURL: Regional Mimecast API Base URL - activeDirectoryAppId: Azure portal ---> App registrations ---> [your_app] ---> Application ID - activeDirectoryAppSecret: Azure portal ---> App registrations ---> [your_app] ---> Certificates & secrets ---> [your_app_secret] - workspaceId: Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Agents ---> Workspace ID (or you can copy workspaceId from above) - workspaceKey: Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Agents ---> Primary Key (or you can copy workspaceKey from above) - AppInsightsWorkspaceResourceID : Azure portal ---> Log Analytics Workspaces ---> [Your workspace] ---> Properties ---> Resource ID >Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) for further details. 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy. 6. Go to ***Azure portal ---> Resource groups ---> [your_resource_group] ---> [appName](type: Storage account) ---> Storage Explorer ---> BLOB CONTAINERS ---> SIEM checkpoints ---> Upload*** and create empty file on your machine named checkpoint.txt, dlp-checkpoint.txt and select it for upload (this is done so that date_range for SIEM logs is stored in consistent state)