Mimecast DMARC Analyzer
Configure the Mimecast DMARC Analyzer integration with RAD Security to ingest DMARC domain posture, DNS record-change/issue events, and DMARC reports.
This guide walks you through integrating Mimecast DMARC Analyzer with RAD Security to ingest your DMARC posture and email-authentication telemetry for external attack-surface and email-security analysis.
Mimecast DMARC Analyzer is an email-authentication (DMARC/SPF/DKIM) platform. RAD Security connects to the Mimecast API 2.0 and pulls your monitored domains, DNS record-change/issue events, and DMARC reports on a scheduled basis. It complements the registration/DNS providers in Domain Security (CSC Global, DNS Made Easy) by adding DMARC posture and reporting on top of domain data.
Read-only integration: RAD Security only reads data from Mimecast DMARC Analyzer. It never creates, modifies, or deletes domains, DNS records, or reports in your account.
Beta: This integration is in beta while DMARC report parsing is validated against live tenants. Domain posture and DNS record-change/issue events are the primary streams.
Prerequisites
Before you begin, ensure you have:
- A Mimecast account with access to the Administration Console
- A Mimecast API 2.0 Application with the DMARC Analyzer Product entitlement
- The application's Client ID and Client Secret
- Access to a RAD Security workspace with integration permissions
API access is entitlement-gated: Mimecast API 2.0 Applications are scoped by immutable Products, and some endpoints additionally require an account-level product entitlement. The application must have the DMARC Analyzer Product added, or the integration cannot connect.
Understanding Integration Components
Step 1: Create an API 2.0 Application in Mimecast
Sign in to the Administration Console
Log in to the Mimecast Administration Console with an administrator.
Create an API 2.0 Application
Navigate to the API 2.0 application settings and create a new application. Associate the DMARC Analyzer Product with the application so it is entitled to the DMARC Analyzer endpoints.
Generate the Client ID and Client Secret
Generate the application's Client ID and Client Secret.
Copy the Client Secret immediately and store it securely in a password manager or secrets vault. You will need both values to configure the integration.
Confirm the account entitlement
Confirm your Mimecast account is entitled to DMARC Analyzer. Some endpoints require an account-level product entitlement in addition to the application's Product.
Exact console navigation and labels may vary by Mimecast plan and region. See the Mimecast API 2.0 documentation for the current steps to create an application, associate Products, and generate credentials.
Configure in RAD Security
Navigate to your RAD Security workspace and configure the Mimecast DMARC Analyzer integration with the following parameters:
Required Parameters
| Parameter | Description |
|---|---|
| Client ID | Client ID of the Mimecast API 2.0 Application (with the DMARC Analyzer Product entitlement) |
| Client Secret | Client Secret paired with the Client ID, used to mint short-lived API tokens |
Optional Parameters
| Parameter | Description |
|---|---|
| Ingest failure reports (RUF) | Also ingest forensic failure reports once the Reports subsystem is enabled. These carry message-level PII (sender, recipient, subject); RAD hashes addresses and redacts subjects before storage. Boolean; default off. |
RAD Security handles token exchange and refresh automatically — you provide the Client ID and Client Secret.
Verify Integration
Check Connection Status
- Navigate to Data Sources > Integrations > Domain Security in RAD Security
- Locate your Mimecast DMARC Analyzer integration
- Verify the connection status shows as Connected
Your Mimecast DMARC Analyzer integration is now configured! RAD Security will ingest your DMARC domain posture and DNS record-change/issue events on a scheduled basis (and DMARC reports as validated, including failure reports if you enabled them).
What Data is Synced
On first connection RAD backfills recent events, then syncs incrementally (only new events each cycle). Domain posture is refreshed each cycle; the re-insert is skipped when the snapshot is unchanged.
Use Cases
Email Authentication Posture Track DMARC/SPF/DKIM coverage and enforcement policy across your domains.
DNS Change Monitoring Surface DNS record changes and DMARC issues as they are detected.
Enforcement Rollout Monitor progress toward p=quarantine/reject without breaking legitimate mail.
Attack Surface Analysis Combine DMARC posture with domain and DNS data for a fuller external view.
Mimecast DMARC Analyzer focuses on email authentication. Pair it with CSC Global and DNS Made Easy for registration, TLS, and operational DNS coverage.
Troubleshooting
Security Best Practices
Use a Dedicated Application Create a dedicated API 2.0 Application for RAD rather than reusing one scoped to other integrations.
Rotate Credentials Regenerate the Client ID and Client Secret periodically according to your security policy.
Secure Storage Store the Client Secret in a secrets vault. Never commit it to version control.
Treat RUF as Sensitive Enable failure-report (RUF) ingestion only when needed; RAD hashes addresses and redacts subjects, but RUF is inherently more sensitive than RUA.
Additional Resources
Mimecast API 2.0 Docs
Official Mimecast API developer documentation
Domain Security Overview
Learn about RAD's domain security integrations