Performing DMARC Policy Enforcement Rollout
Overview
Domain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.
When to Use
- When conducting security assessments that involve performing dmarc policy enforcement rollout
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Administrative access to DNS management for the domain
- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)
- Complete inventory of all legitimate email sending sources
- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)
- Email gateway with DMARC enforcement capability
Key Concepts
DMARC Policy Levels
| Policy |
Behavior |
Use Case |
| p=none |
Monitor only, no action on failures |
Discovery phase |
| p=quarantine |
Send failing messages to spam/junk |
Transition phase |
| p=reject |
Block failing messages entirely |
Full enforcement |
DMARC Record Anatomy
v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1
- p: Policy for organizational domain
- sp: Policy for subdomains
- pct: Percentage of messages subject to policy (for gradual rollout)
- rua: Aggregate report destination (daily XML reports)
- ruf: Forensic report destination (per-failure reports)
- adkim: DKIM alignment mode (r=relaxed, s=strict)
- aspf: SPF alignment mode (r=relaxed, s=strict)
- fo: Failure reporting options (0=both fail, 1=either fails)
SPF and DKIM Alignment
- SPF Alignment: The domain in the Return-Path (envelope sender) must match the From header domain
- DKIM Alignment: The d= domain in the DKIM signature must match the From header domain
- Relaxed: Organizational domain match (sub.example.com matches example.com)
- Strict: Exact domain match required
Workflow
Step 1: Inventory All Sending Sources (Week 1-2)
- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)
- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.
- Identify internal mail servers, applications, and relay hosts
- Check for shadow IT email sending (departments using unauthorized services)
Step 2: Configure SPF and DKIM (Week 2-4)
- Consolidate SPF record with all legitimate sending IPs and includes
- Ensure SPF record stays under 10 DNS lookup limit
- Generate and publish DKIM keys for each sending source
- Verify DKIM signing works for all outbound mail paths
- Test with MX Toolbox or dmarcian SPF/DKIM validators
Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)
- Publish initial DMARC record:
v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1
- Wait 1-2 weeks to collect representative aggregate reports
- Analyze reports to identify unauthorized senders and alignment failures
- Fix SPF/DKIM for all legitimate sources showing failures
- Iterate until all legitimate mail passes DMARC
Step 4: Move to Quarantine with pct Tag (Week 6-12)
- Update to quarantine at 10%:
v=DMARC1; p=quarantine; pct=10; rua=...
- Monitor for false positives (legitimate mail being quarantined)
- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%
- Each increase: wait 1-2 weeks and review reports before advancing
- Fix any remaining alignment issues discovered at each stage
Step 5: Advance to Reject Policy (Week 12-20)
- After stable quarantine at 100%, move to reject at 10%:
v=DMARC1; p=reject; pct=10; rua=...
- Gradually increase pct: 10% -> 25% -> 50% -> 100%
- Monitor closely for legitimate mail being rejected
- Establish emergency rollback procedure (revert to quarantine)
- Apply subdomain policy:
sp=reject for subdomains
Step 6: Ongoing Monitoring and Maintenance
- Continuously monitor DMARC aggregate reports
- Add new sending sources before they start sending
- Review forensic reports for spoofing attempts
- Maintain SPF record as sending infrastructure changes
- Rotate DKIM keys annually
Tools & Resources
- EasyDMARC: DMARC monitoring dashboard with aggregate/forensic report analysis
- DMARCLY: SPF, DKIM, DMARC monitoring with auto-DNS updates
- dmarcian: DMARC deployment and management platform
- Valimail: Automated DMARC enforcement with hosted authentication
- MX Toolbox: DNS record lookup and DMARC validator
- Google Admin Toolbox: DMARC check and diagnostic tools
Validation
- DMARC record published and resolving correctly at _dmarc.domain.com
- All legitimate sending sources pass SPF and/or DKIM alignment
- Aggregate reports show >99% legitimate mail passing DMARC
- Spoofed messages from unauthorized senders are rejected
- No legitimate mail blocked after full p=reject enforcement
- Subdomain policy (sp=) also set to reject
1---2name: performing-dmarc-policy-enforcement-rollout3description: Execute a phased DMARC rollout by inventorying sending sources, configuring4 SPF/DKIM alignment, and progressing DNS policy from p=none monitoring through p=quarantine5 to p=reject enforcement, ensuring all legitimate email sources authenticate before6 unauthorized senders are blocked. Use when deploying or advancing an organization's7 DMARC anti-spoofing posture, or when meeting bulk-sender authentication requirements8 from Google and Yahoo.9domain: cybersecurity10subdomain: phishing-defense11tags:12- dmarc13- spf14- dkim15- email-authentication16- anti-spoofing17- phishing18- dns19- email-security20version: '1.0'21author: mahipal22license: Apache-2.023nist_csf:24- PR.AT-0125- DE.CM-0926- RS.CO-0227- DE.AE-0228mitre_attack:29- T156630- T159831- T153432- T103633metadata:34 source: https://skillmd.com/skills/26zl/performing-dmarc-policy-enforcement-rollout35---3637# Performing DMARC Policy Enforcement Rollout3839## Overview40Domain-based Message Authentication, Reporting and Conformance (DMARC) is the cornerstone of email anti-spoofing protection. A DMARC rollout progresses through three phases: monitoring (p=none), quarantine (p=quarantine), and full enforcement (p=reject). When configured at p=reject, any email that fails both SPF and DKIM checks is outright rejected. Google and Yahoo now require DMARC for bulk senders (5,000+ emails), driving a 65% reduction in unauthenticated messages. The rollout typically takes 3-6 months for safe deployment.414243## When to Use4445- When conducting security assessments that involve performing dmarc policy enforcement rollout46- When following incident response procedures for related security events47- When performing scheduled security testing or auditing activities48- When validating security controls through hands-on testing4950## Prerequisites51- Administrative access to DNS management for the domain52- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)53- Complete inventory of all legitimate email sending sources54- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)55- Email gateway with DMARC enforcement capability5657## Key Concepts5859### DMARC Policy Levels60| Policy | Behavior | Use Case |61|---|---|---|62| p=none | Monitor only, no action on failures | Discovery phase |63| p=quarantine | Send failing messages to spam/junk | Transition phase |64| p=reject | Block failing messages entirely | Full enforcement |6566### DMARC Record Anatomy67```68v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=169```70- **p**: Policy for organizational domain71- **sp**: Policy for subdomains72- **pct**: Percentage of messages subject to policy (for gradual rollout)73- **rua**: Aggregate report destination (daily XML reports)74- **ruf**: Forensic report destination (per-failure reports)75- **adkim**: DKIM alignment mode (r=relaxed, s=strict)76- **aspf**: SPF alignment mode (r=relaxed, s=strict)77- **fo**: Failure reporting options (0=both fail, 1=either fails)7879### SPF and DKIM Alignment80- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain81- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain82- **Relaxed**: Organizational domain match (sub.example.com matches example.com)83- **Strict**: Exact domain match required8485## Workflow8687### Step 1: Inventory All Sending Sources (Week 1-2)88- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)89- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.90- Identify internal mail servers, applications, and relay hosts91- Check for shadow IT email sending (departments using unauthorized services)9293### Step 2: Configure SPF and DKIM (Week 2-4)94- Consolidate SPF record with all legitimate sending IPs and includes95- Ensure SPF record stays under 10 DNS lookup limit96- Generate and publish DKIM keys for each sending source97- Verify DKIM signing works for all outbound mail paths98- Test with MX Toolbox or dmarcian SPF/DKIM validators99100### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)101- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`102- Wait 1-2 weeks to collect representative aggregate reports103- Analyze reports to identify unauthorized senders and alignment failures104- Fix SPF/DKIM for all legitimate sources showing failures105- Iterate until all legitimate mail passes DMARC106107### Step 4: Move to Quarantine with pct Tag (Week 6-12)108- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`109- Monitor for false positives (legitimate mail being quarantined)110- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%111- Each increase: wait 1-2 weeks and review reports before advancing112- Fix any remaining alignment issues discovered at each stage113114### Step 5: Advance to Reject Policy (Week 12-20)115- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`116- Gradually increase pct: 10% -> 25% -> 50% -> 100%117- Monitor closely for legitimate mail being rejected118- Establish emergency rollback procedure (revert to quarantine)119- Apply subdomain policy: `sp=reject` for subdomains120121### Step 6: Ongoing Monitoring and Maintenance122- Continuously monitor DMARC aggregate reports123- Add new sending sources before they start sending124- Review forensic reports for spoofing attempts125- Maintain SPF record as sending infrastructure changes126- Rotate DKIM keys annually127128## Tools & Resources129- **EasyDMARC**: DMARC monitoring dashboard with aggregate/forensic report analysis130- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates131- **dmarcian**: DMARC deployment and management platform132- **Valimail**: Automated DMARC enforcement with hosted authentication133- **MX Toolbox**: DNS record lookup and DMARC validator134- **Google Admin Toolbox**: DMARC check and diagnostic tools135136## Validation137- DMARC record published and resolving correctly at _dmarc.domain.com138- All legitimate sending sources pass SPF and/or DKIM alignment139- Aggregate reports show >99% legitimate mail passing DMARC140- Spoofed messages from unauthorized senders are rejected141- No legitimate mail blocked after full p=reject enforcement142- Subdomain policy (sp=) also set to reject