| 1 | --- |
| 2 | title: Mimecast |
| 3 | description: Ingest Mimecast security events and turn them into dashboards and alerts in CoPilot. |
| 4 | --- |
| 5 | |
| 6 | ## What this integration is |
| 7 | |
| 8 | Mimecast telemetry provides email security signals (policy actions, suspicious messages, detections) that are useful for SOC alerting and investigation. |
| 9 | |
| 10 | ## Data path (how it flows) |
| 11 | |
| 12 | **Typical flow:** |
| 13 | |
| 14 | 1. Mimecast → **External Service integration** (API collector) |
| 15 | 2. Events → **SIEM storage** (Wazuh Indexer / OpenSearch-backed) |
| 16 | 3. Optional: events → **Graylog** alert definitions |
| 17 | 4. Alerts → `gl-events*` → **CoPilot Incident Management → Alerts** |
| 18 | 5. Operator workflow → **Cases** |
| 19 | |
| 20 | ## What data you get (high level) |
| 21 | |
| 22 | - Email security events |
| 23 | - Policy actions / detections (depends on API endpoints enabled) |
| 24 | |
| 25 | ## Setup (wireframe) |
| 26 | |
| 27 | - Configure Mimecast under **External Services / 3rd Party Integrations**. |
| 28 | - Confirm events are tenant-aware. |
| 29 | |
| 30 | ## Success criteria |
| 31 | |
| 32 | - [ ] You can locate at least one recent Mimecast event |
| 33 | - [ ] Events map to the correct customer |
| 34 | |
| 35 | ## Dashboards |
| 36 | |
| 37 | - [ ] After provisioning, confirm dashboards populate for this customer |
| 38 | |
| 39 | ## Alerts (starter set) |
| 40 | |
| 41 | - Spike in blocked/quarantined messages |
| 42 | - Repeated phishing detections for a user |
| 43 | - High-risk sender domains or attachment types (if available) |
| 44 | |
| 45 | ## Troubleshooting |
| 46 | |
| 47 | - Verify external service is connected/verified |
| 48 | - Confirm API credentials/permissions |
| 49 | - Confirm routing/tenant association |