9.5 Implement DMARC
Reduce the chance of spoofed or altered email appearing to come from legitimate domains by putting a DMARC policy and verification in place, building first on SPF and DKIM. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Network. Security function: Protect.
Source: CIS Controls v8.1, 9.5. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CIS Controls v8.1 in the compliance library.
Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- DNS records for SPF, DKIM and DMARC for all sending domains · Document repository
- DMARC aggregate report analysis · Document repository
governing documentDocuments that govern the control
- Plan for moving DMARC to quarantine or reject · Policy repository / GRC workspace
First move
Common gaps auditors find
- DMARC stuck at p=none
- Parked domains without records
- Third-party senders not aligned
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet9.4 Restrict Unnecessary or Unauthorized Browser and Email Client Extensions · 9.6 Block Unnecessary File Types