Deployment
Cloud SEG — MX records point to Proofpoint, which scans inbound/outbound mail…
before delivery; supplemental API integration for some use cases
API-based integration with Microsoft 365 or Google Workspace via three-click connection
no MX record changes, no mail flow disruption
Cloud Secure Email Gateway
MX records redirect mail through Mimecast for scanning and policy enforcement before delivery to Microsoft 365 or Google Workspace; some hybrid/on-prem options for specific use cases
Self-hosted on Linux mail servers
integrates with Postfix, Sendmail, Exim, Qmail, Zmailer as a content scanner; commonly paired with SpamAssassin (spam), ClamAV (malware), and optionally F-Prot, Sophos, or other commercial AV engines
Typical deployment time
Days for Essentials deployments with mail flow cutover
weeks for enterprise with TAP, DLP, archiving, awareness training, and DMARC integration
Minutes for API integration
days to weeks for full tuning, vendor relationship baselining, and workflow integration
Days to weeks for SEG mail flow cutover
weeks to months for full deployments with archiving, continuity, training, and DLP integration
Hours for basic install on existing mail server
days to weeks for production tuning, rule customization, quarantine workflows, and reporting setup
Key integrations
Microsoft 365, Google Workspace, Splunk, Microsoft Sentinel, IBM QRadar,…
CrowdStrike, Okta, ServiceNow; integrates with Proofpoint Security Awareness Training, DLP, and Archiving products
Microsoft 365, Google Workspace
SIEM forwarding (Splunk, Microsoft Sentinel); CrowdStrike, Okta, Slack, ServiceNow; identity and SSO platforms
Microsoft 365, Google Workspace, Microsoft Sentinel, Splunk, CrowdStrike,…
ServiceNow, Okta, Active Directory; 30+ integrations for IAM/PAM, endpoint, SOAR, SIEM
Postfix, Sendmail, Exim, Qmail, Zmailer
SpamAssassin, ClamAV, F-Prot, Sophos, Avira, BitDefender, Kaspersky engines via integration; MailWatch web UI for monitoring; SIEM forwarding via syslog