Email Security
SPF, DKIM, DMARC, anti-phishing, and safe attachments — extended with court-admissible proof of encrypted external delivery.
Your auditor will ask you to prove sensitive email was encrypted, delivered, and received. That proof gap is what even the most comprehensive Purview deployments leave open. We deploy SPF, DKIM, DMARC, and anti-phishing — then extend it with court-admissible proof of every encrypted delivery. The evidence exists before the auditor asks.
Here is the complete email security stack we deploy and operate. Every capability below produces auditable evidence of protection.
Foundation (Plan 1)
- SPF Configuration — Configure SPF records for email authentication and anti-spoofing
- DKIM Configuration — Configure DKIM signing for email authentication
- DMARC Configuration — Configure DMARC policy for email authentication enforcement
- Email Branding — Configure organisation branding and external sender warnings
- Email Disclaimers — Configure email disclaimers and transport rules
- Network Service Security — Email gateway security, Safe Links, Safe Attachments, transport rule hardening, SMTP auth, and mail forwarding controls
- Safe Links — Microsoft Defender for Office 365 Safe Links URL protection
- Malware Protection — Microsoft Defender for Office 365 malware protection: Safe Attachments, AV signatures, endpoint security profiles, device compliance
Added in Information Governance (Plan 3)
- Registered Email Encryption — Court-admissible proof of encrypted delivery for external communications, closing the evidence gap for A.5.14 (Information Transfer) and A.5.31 (Legal/Regulatory Requirements)
- Adaptive Encryption — Dynamic TLS-first encryption with AES-256 PDF fallback, delivering securely to recipients’ inboxes without portal friction — complementing Purview Message Encryption where external recipients lack Microsoft accounts
- Proof of Delivery — Registered Receipt records with immutable timestamps, content proof, and self-authenticating encryption evidence — directly addressing A.8.24 (Use of Cryptography) audit requirements
- Outbound AI Threat Detection — AI-driven detection of sensitive content, lookalike domains, and business email compromise at the point of send, reinforcing A.8.12 (Data Leakage Prevention) with human-in-the-loop awareness
What you receive
| Delivery Package | Duration | Stakeholders | Key Deliverables |
|---|---|---|---|
| Email Security Hardening | 3–8 days | IT Admin, Email Admin | SPF/DKIM/DMARC configuration per domain; Safe Links and malware policies; Transport rule review; Email branding templates |
| Registered Email & Proof of Delivery | 2–5 days | Legal, Compliance, CISO | RMail encryption policies configured; Registered Receipt configuration and testing; Outbound AI content detection rules; Purview complementary guidance document |
Risk impact
| Risk | Before | After | Reduction |
|---|---|---|---|
| Communications Interception | 12 | 2 | 83% |
| Communications Manipulation | 12 | 2 | 83% |
Risk scores use a likelihood × impact matrix (1–25). Lower is better.
Ready to see where you stand? Our free assessment benchmarks your email security against these capabilities — in 30 minutes, no tenant access required. Start your assessment.