We identify the services sending mail using your domain and set up SPF, DKIM and DMARC according to those senders. We apply separate controls for malicious attachments, impersonation and unauthorized forwarding.
With SPF, DKIM and DMARC we strengthen protection against unauthorized use of your own domain. Lookalike domains, display name spoofing and a genuinely compromised account are separate scenarios; each requires its own control.
01
Will our emails get lost when we set DMARC to reject?
We don’t move to an enforcement policy until legitimate sending services are aligned with SPF or DKIM. Reports are monitored and the migration is done per domain. The receiving server decides how to apply the policy.
02
Isn’t Microsoft 365’s own protection enough?
Exchange Online Protection provides basic protection. Defender for Office 365 adds advanced link/attachment analysis and impersonation protection; the need is determined by the risk profile.
03
Are our website’s form emails affected too?
Yes. Emails sent from the web server on behalf of your domain must be authorized in SPF or sent through authenticated SMTP.
04
What should we do if a phishing email is clicked?
A response procedure is prepared that includes changing the password, ending open sessions, checking mailbox rules and purging similar emails from all mailboxes.
Implementation approach
Controlled, documented, sustainable
01 / ANALYSIS
Inventory and DNS analysis
Sending services and existing DNS records are reviewed.
02 / PLAN
Authentication setup
SPF/DKIM are fixed and DMARC reporting starts.
03 / EXECUTION
Protection policies
Inbound mail, phishing and forwarding policies are configured.
04 / HANDOVER
Phased tightening
While monitoring reports, the DMARC policy is moved to quarantine and then reject.