[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Collect Mimecast Mail logs\n==========================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document describes how you can collect Mimecast Secure Email Gateway logs by\nsetting up a Google Security Operations feed.\n\nFor more information, see [Data ingestion to Google Security Operations](/chronicle/docs/data-ingestion-flow).\n\nAn ingestion label identifies the parser which normalizes raw log data\nto structured UDM format. The information in this document applies to the parser with the `MIMECAST_MAIL` ingestion label.\n\nConfigure Mimecast Secure Email Gateway\n---------------------------------------\n\n1. [Enable logging for the login account](/chronicle/docs/preview/siem-integrations/mimecast-email-parser#enable-logging-for-login-account).\n2. [Create the API application](/chronicle/docs/preview/siem-integrations/mimecast-email-parser#create-api-application).\n3. [Get the application ID and application key](/chronicle/docs/preview/siem-integrations/mimecast-email-parser#get-application-id-and-application-key).\n\n### Enable logging for the login account\n\n1. Sign in to the [Mimecast Administration](https://login-us.mimecast.com/u/login/?gta=administration&link=administration-dashboard#/login) console.\n2. In the **Account** menu, click **Account Settings**.\n3. Expand **Enhanced Logging**.\n4. Select the types of logs to enable:\n - **Inbound**: logs messages from external senders to internal recipients.\n - **Outbound**: logs messages from internal senders to external recipients.\n - **Internal**: logs messages within internal domains.\n5. Click **Save** to apply the changes.\n\n### Create the API application\n\n1. Sign in to the [Mimecast Administration](https://login-us.mimecast.com/u/login/?gta=administration&link=administration-dashboard#/login) console.\n2. Click **Add API Application**.\n3. Enter the following details:\n 1. Application name.\n 2. Description for the application.\n 3. Category: Enter one of the following categories:\n - **SIEM Integration**: provides real-time analysis of the security alerts generated by the application.\n - **MSP Ordering and Provisioning**: available for select partners to manage orders in the MSP Portal.\n - **Email / Archiving**: refers to messages and alerts stored in Mimecast.\n - **Business Intelligence**: enables application's infrastructure and tools to access and analyse information to improve and optimize decisions and performance.\n - **Process Automation**: allows for automation of business processes.\n - **Other**: in case the application doesn't fit within any other category.\n4. Click **Next**.\n5. Specify values for the following input parameters:\n - **Authentication HTTP Header Configuration:** enter authentication details in the following format: `secret_key:{Access Secret}` \n `access_key:{Access key}` \n `app_id:{Application ID}` \n `app_key:{application key}`\n - **API Hostname:** fully qualified domain name of your Mimecast API endpoint. The typical format is `xx-api.mimecast.com`. If not provided, it will be region-specific in the US and Europe. This field cannot be empty for other regions.\n - **Asset namespace** : the [asset namespace](/chronicle/docs/investigation/asset-namespaces).\n - **Ingestion labels**: the label applied to the events from this feed.\n6. Click **Next**.\n7. Review the information displayed on the **Summary Page**.\n8. To fix errors, follow these steps:\n - Click **Edit** buttons next to **Details** or **Settings**.\n - Click **Next** and go to the **Summary** page again.\n\n### Get the application ID and application key\n\n1. Click **Application** and then click **Services**.\n2. Click **API Application**.\n3. Select the created API application.\n4. View the application details.\n\n### Creating API access and secret key\n\nFor information about generating access and secret key, see [Creating User Association Key](https://community.mimecast.com/s/article/api-integrations-managing-api-applications#Creating-User-Association-Keys).\n\nSet up feeds\n------------\n\nTo configure this log type, follow these steps:\n\n1. Go to **SIEM Settings \\\u003e Feeds**.\n2. Click **Add New Feed**.\n3. Click the **Mimecast** feed pack.\n4. Specify the values for the following fields:\n\n - **Source Type**: Third party API (recommended)\n - **Authentication HTTP header**: provide the providing the application ID, access key, secret ID, and application key.\n - **API Hostname**: specify the domain name of your Mimecast host.\n\n **Advanced options**\n - **Feed Name**: A prepopulated value that identifies the feed.\n - **Asset Namespace** : [Namespace associated with the feed](/chronicle/docs/investigation/asset-namespaces).\n - **Ingestion Labels**: Labels applied to all events from this feed.\n5. Click **Create Feed**.\n\nFor more information about configuring multiple feeds for different log types within this product family, see [Configure feeds by product](/chronicle/docs/ingestion/ingestion-entities/configure-multiple-feeds).\n\nField mapping reference\n-----------------------\n\nThis parser extracts key-value pairs from Mimecast email server logs, categorizes the log entry stage (RECEIPT, PROCESSING, or DELIVERY), and maps the extracted fields to the UDM. It also performs specific logic to handle security-related fields, determining the security result action, category, severity, and related details based on values like `Act`, `RejType`, `SpamScore`, and `Virus`.\n\n### UDM mapping table\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]