requests recipient email services to report email sources and origins; provides visibility over potentially illegitimate or fraudulent email. 15.2.8. DMARC builds on SPF and DKIM protocols, adding links to the author (“From:”) domain name, published policies for recipient handling of authentication failures, and reporting from receivers to senders, in order to improve and monitor protection of the recipient domain from fraudulent email. 15.2.9. Most email services will check your DMARC record and send aggregated reports including details of all email the service received from the agency, and its origin. This assists in identifying if an individual within the agency is sending email inappropriately or if the agency domain is being spoofed. Background, Reference and Implementation Guidance Sources 15.2.10. The IETF published RFC 7489, “Domain-based Message Authentication, Reporting, and Conformance (DMARC)” March 18th, 2015. RFC 7489. This is the principal standards guidance on the implementation and use of DMARC. Further guidance is available from The Global Cyber Alliance (GCA) - see References below. Using DMARC 15.2.11. By establishing DMARC, SPF, and DKIM records in DNS, it's possible to advise email service providers which servers should be legitimately sending email from the agency’s domain, and what action to take with mail received from any other domains. 15.2.12. In support of DMARC agencies must publish an SPF and a DKIM record. Agencies must also ensure emails agencies send (including those from third party services that send on behalf of the agency) have a DKIM signature that matches the signature in the DKIM record. 15.2.13. Agencies can choose to quarantine or reject messages that fail checks. More specifically: Sender Policy Framework (SPF) is used to specify legitimate locations of servers which can send email for your domain; DomainKeys Identified Mail (DKIM) isn't supported by all mail servers, but if it is, it can be used to cryptographically sign outgoing mail sent by your servers to give email service providers further confidence that it's legitimate; DMARC is used to inform email service providers what action they should take if SPF or DKIM (or both) validation fails; One important aspect of DMARC is the action you ask email service providers to take when SPF or DKIM validation fails: a policy of p=none means that they should allow non-compliant emails to be delivered but report the failure to the agency; a policy of p=quarantine requests that they mark the email as spam; a policy of p=reject requests the email service provider to refuse to deliver the email. 15.2.14. Many organisations start with a policy of p=none, then modify the configuration to p=reject as confidence is gained in the accuracy of the configuration and in systems performance. 15.2.15. To notify other organisations of the use of DMARC agencies may publish a text record in their DNS similar to the following: v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@agency.govt.nz (where agency is the name of the respective agency). 15.2.16. This informs email recipients that: you have a DMARC policy (v=DMARC1) any messages that fail DMARC checks should be treated as spam (p=quarantine) they should treat 100% of your messages this way (pct=100) they should send reports of email received back to you (rua=mailto:dmarc@agency.govt.nz) 15.2.17. It is not unusual to experience minor errors in syntax or other elements of DMARC configuration when first implementing DMARC. Some discussion on common problems, issues and solutions can be found on the DMARC website (see the References table below). 15.2.18. It is unwise for an agency to attempt to move to full implementation of DMARC until there is certainty that the configuration and implementation are stable and operating as intended. The following implementation outline is recommended by the GCA/DMARC organisation (see References below): 1. Deploy DKIM & SPF; 2. Ensure mailers are correctly aligning the appropriate identifiers; 3. Publish a DMARC record with the “none” flag set for the policies, which requests data reports; 4. Analyse the data and modify mail streams as appropriate; and 5. Modify DMARC policy flags from “none” to “quarantine” to “reject” as experience dictates. DMARC Reporting 15.2.19. DMARC reporting provides information to assist an agency’s IT system and email administrators. It can also provide an email asset inventory as well as providing data on spam, phishing and other email exploitation techniques. 15.2.20. DMARC can be configured to produce an aggregate report and a forensic report. In some cases agencies may also send reports to an external organisation such as a DMARC reporting service or a third-party IT service provider. Discretion should be used when providing such information to third parties in order to maintain security and privacy. References 15.2.21. Further information on email security is available from the following sources: Reference 200 Title Publisher Source Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents