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, configuring SPF/DKIM alignment, and progressing DNS policy from p=none monitoring through p=quarantine to p=reject enforcement, ensuring all legitimate email sources authenticate before unauthorized senders are blocked. Use when deploying or advancing an organization's DMARC anti-spoofing posture, or when meeting bulk-sender authentication requirements from Google and Yahoo.4license: Apache-2.05---6# Performing DMARC Policy Enforcement Rollout
7
8## Overview
9Domain-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.
10
11
12## When to Use
13
14- When conducting security assessments that involve performing dmarc policy enforcement rollout
15- When following incident response procedures for related security events
16- When performing scheduled security testing or auditing activities
17- When validating security controls through hands-on testing
18
19## Prerequisites
20- Administrative access to DNS management for the domain
21- Understanding of SPF, DKIM, and DMARC protocols (RFC 7208, 6376, 7489)
22- Complete inventory of all legitimate email sending sources
23- DMARC reporting analysis tool (EasyDMARC, DMARCLY, Valimail, or dmarcian)
24- Email gateway with DMARC enforcement capability
25
26## Key Concepts
27
28### DMARC Policy Levels
29| Policy | Behavior | Use Case |
30|---|---|---|
31| p=none | Monitor only, no action on failures | Discovery phase |
32| p=quarantine | Send failing messages to spam/junk | Transition phase |
33| p=reject | Block failing messages entirely | Full enforcement |
34
35### DMARC Record Anatomy
36```
37v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-agg@company.com; ruf=mailto:dmarc-forensic@company.com; adkim=r; aspf=r; fo=1
38```
39- **p**: Policy for organizational domain
40- **sp**: Policy for subdomains
41- **pct**: Percentage of messages subject to policy (for gradual rollout)
42- **rua**: Aggregate report destination (daily XML reports)
43- **ruf**: Forensic report destination (per-failure reports)
44- **adkim**: DKIM alignment mode (r=relaxed, s=strict)
45- **aspf**: SPF alignment mode (r=relaxed, s=strict)
46- **fo**: Failure reporting options (0=both fail, 1=either fails)
47
48### SPF and DKIM Alignment
49- **SPF Alignment**: The domain in the Return-Path (envelope sender) must match the From header domain
50- **DKIM Alignment**: The d= domain in the DKIM signature must match the From header domain
51- **Relaxed**: Organizational domain match (sub.example.com matches example.com)
52- **Strict**: Exact domain match required
53
54## Workflow
55
56### Step 1: Inventory All Sending Sources (Week 1-2)
57- Audit all systems sending email as your domain (marketing, CRM, ticketing, transactional)
58- Document third-party services: Salesforce, Mailchimp, SendGrid, Zendesk, etc.
59- Identify internal mail servers, applications, and relay hosts
60- Check for shadow IT email sending (departments using unauthorized services)
61
62### Step 2: Configure SPF and DKIM (Week 2-4)
63- Consolidate SPF record with all legitimate sending IPs and includes
64- Ensure SPF record stays under 10 DNS lookup limit
65- Generate and publish DKIM keys for each sending source
66- Verify DKIM signing works for all outbound mail paths
67- Test with MX Toolbox or dmarcian SPF/DKIM validators
68
69### Step 3: Deploy DMARC in Monitoring Mode (Week 4-6)
70- Publish initial DMARC record: `v=DMARC1; p=none; rua=mailto:dmarc@company.com; fo=1`
71- Wait 1-2 weeks to collect representative aggregate reports
72- Analyze reports to identify unauthorized senders and alignment failures
73- Fix SPF/DKIM for all legitimate sources showing failures
74- Iterate until all legitimate mail passes DMARC
75
76### Step 4: Move to Quarantine with pct Tag (Week 6-12)
77- Update to quarantine at 10%: `v=DMARC1; p=quarantine; pct=10; rua=...`
78- Monitor for false positives (legitimate mail being quarantined)
79- Increase pct gradually: 10% -> 25% -> 50% -> 75% -> 100%
80- Each increase: wait 1-2 weeks and review reports before advancing
81- Fix any remaining alignment issues discovered at each stage
82
83### Step 5: Advance to Reject Policy (Week 12-20)
84- After stable quarantine at 100%, move to reject at 10%: `v=DMARC1; p=reject; pct=10; rua=...`
85- Gradually increase pct: 10% -> 25% -> 50% -> 100%
86- Monitor closely for legitimate mail being rejected
87- Establish emergency rollback procedure (revert to quarantine)
88- Apply subdomain policy: `sp=reject` for subdomains
89
90### Step 6: Ongoing Monitoring and Maintenance
91- Continuously monitor DMARC aggregate reports
92- Add new sending sources before they start sending
93- Review forensic reports for spoofing attempts
94- Maintain SPF record as sending infrastructure changes
95- Rotate DKIM keys annually
96
97## Tools & Resources
98- **EasyDMARC**: DMARC monitoring dashboard with aggregate/forensic report analysis
99- **DMARCLY**: SPF, DKIM, DMARC monitoring with auto-DNS updates
100- **dmarcian**: DMARC deployment and management platform
101- **Valimail**: Automated DMARC enforcement with hosted authentication
102- **MX Toolbox**: DNS record lookup and DMARC validator
103- **Google Admin Toolbox**: DMARC check and diagnostic tools
104
105## Validation
106- DMARC record published and resolving correctly at _dmarc.domain.com
107- All legitimate sending sources pass SPF and/or DKIM alignment
108- Aggregate reports show >99% legitimate mail passing DMARC
109- Spoofed messages from unauthorized senders are rejected
110- No legitimate mail blocked after full p=reject enforcement
111- Subdomain policy (sp=) also set to reject
gabrielmoreira