> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/detection-strategy-guides/d-m/mimecast-detection-strategy.md).
# Mimecast Detection Strategy
## Product Overview
Mimecast is a cybersecurity solution that helps organizations detect, analyze, and block advanced threats targeting people through email, including malicious attachments and URLs, and offers real-time threat prevention and forensic analysis.
## Detection Strategy for Email Integrations
### Detection
Expel integrates directly with email security providers and uses their data to quickly identify and investigate email and identity-based attacks to:
* generate Expel alerts for investigation
* provide enriched context to a threat
* offer decision support for incident scoping and severity identification
Expel consumes email security provider events through a mix of raw log analysis and security alert processing, which pass through our detection engine to identify signs of post-exploitation activity. When a threat is detected, our automated response bot takes action by enriching evidence fields with first- and third-party threat intelligence. Additional bot actions query a wide span of technologies in order to directly arm analysts with key pieces of investigative information and related events.
Email security providers do not provide full-body email text to Workbench analysts, but rather the alert data provided by the email security providers' devices. Full-text analysis of user-submitted emails is offered via [Expel’s Managed Phishing service](/more-features/expel-managed-phishing.md) offering. When events are promoted to Expel alerts, additional workflows are used to query to enrich the event with context.
### Response
Email alerts are useful to identify and mitigate email threats such as phishing, business email compromise (BEC), and malware. Additionally, telemetry from other integrations with Expel is used to correlate activity across the kill chain to paint a more comprehensive picture of an attack beyond the email threat surface. For example, for an onboarded EDR or network security device, Expel can correlate the observation of a malicious attachment in the email security provider with the downloading and execution of that attachment in these integrations. If no other integrations are onboarded, analysts will use the context from the alert as well as Expel-internal enrichment sources (file/IP/URL lookups) to make the best determination of an alert.
To learn more about our overall approach to detection strategy, see [About Detection Strategy](/workbench-reference/detections/about-detection-strategy.md) in the Help Center.
## What We Support for Mimecast
To see a comprehensive list of the most up-to-date Expel detection rules, vendor detection rules, opt-in detections, and available DUETs (did you expect this) that we support for Mimecast, you can visit the [Detections page](https://workbench.expel.io/tools/detections/all?filter=%7B%22supportedTech%22%3A%7B%22is%22%3A%5B%22mimecast%3A1.0.0%22%5D%7D%7D) in Workbench or ask your Sales or Support rep for the most recent download.
| **Supported versions** | |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Supported event log sources** | - Attachment
- Impersonation
- URL (with a focus on click events)
|
| **Mimecast detection rules support** | Yes. |
| **Detection rules written by Expel** | Yes. |
| **Investigative support through Workbench** | Yes. We are able to take the following investigative actions to gather data for triage and investigation of events:
- Query Mimecast URL Protection
- Query Mimecast Attachment Protection
- Query Mimecast Impersonation Protection
- Query Mimecast Threat Activity
|
| **Hunting support** | No. Hunting is not currently available for this integration. |
## Additional Details and Common Questions
### DUET
A DUET (did you expect this) rule flags certain events as needing an immediate verification or notification, and bypasses the normal internal event triage process. The events subject to DUET rules contain behaviors that are not typically indicative of true security incidents, as they are related to policy violations or potential risk.
There are a number of workflows that a DUET may follow. When enabled, the activity will be flagged for investigation and will be routed to you (rather than to us) to take a specified first action. To see the specific DUET rules currently supported for this integration, visit the [Detections page](https://workbench.expel.io/tools/detections/all) in Workbench.
### Use Cases Not Supported
| Use Case | Reason |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Abuse Mailbox (User Reported Emails) Support | Not included as part of the Mimecast MDR integration. Support for this feature requires the Expel Managed Phishing service. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.expel.io/detection-strategy-guides/d-m/mimecast-detection-strategy.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.