This article contains information on the DMARC implementation workflow, detailing tasks for domain policy changes, vendor compliance via SPF/DKIM, and data-driven progress tracking to ensure email authentication and domain protection.
DMARC Implementation workflow
- Analysis of data
- Planning and executing the next actions
- Monitoring changes
- (Repeat)
DMARC workflow applies to a domain
- Domain moves through various policy states
- Within the scope of a domain, various vendors could send email
- All vendors need to be compliant to allow moving to a different policy state
- Vendors are made compliant by SPF and DKIM authentication (aligned)
Workflow
- Consists of tasks:
-
-
-
-
- That serves the goal of allowing a domain to change policy state
- That allows vendor compliance across domains
-
-
-
- Based on available DMARC data tasks can be assigned (based on vendor)
-
-
-
-
- Assigned tasks are driven by data
- The user can confirm task has been performed, data is used to confirm
- Domain can have multiple tasks
- Vendor could have 1 task for multiple domains
-
-
-
- Tasks/progress/project is trackable
- All combined can suggest a data-driven DMARC implementation approach
- The system offers suggestions based on trends/analytics and data when it is possible to move to the next state to protect domains.
- Can predict what would happen in a specific policy situation, based on DMARC logic
Comments
Please sign in to leave a comment.