An email policy that lives in a shared drive and says "employees must be careful" is not a control. A useful policy names who owns each control, what evidence proves it is working and how often someone checks. This checklist is designed to be copied into a spreadsheet, assigned and signed, not read once and filed.
How to use this checklist
Give every row one accountable owner, even where several people do the work. Evidence means an export, a screenshot, a ticket or a report that can be produced on request. Frequency should match the risk: monthly for access and monitoring, quarterly for configuration, annual for policy and supplier review. Keep the checklist short enough for each owner to finish their section in one sitting. Sign-off happens at approval, at the annual review and whenever a material change occurs, such as a new domain, a merger or a major incident.
Policy checklist
| Section | Control | Owner | Evidence | Frequency |
|---|---|---|---|---|
| Governance | Name a policy owner and a deputy | Managing director | Signed appointment | Annual |
| Governance | Define scope: domains, mailboxes, aliases and contractors | IT lead | Mailbox inventory | Annual |
| Governance | Approve acceptable use and data classification rules | Management | Signed policy | Annual |
| Governance | Set retention, export and legal hold rules | IT and legal | Retention schedule | Annual |
| Access | Enforce MFA on every mailbox, including administrators | IT lead | Tenant MFA report | Monthly |
| Access | Use single sign-on and role-based administration | IT lead | Role export | Quarterly |
| Access | Prohibit shared passwords for shared mailboxes | IT lead | Mailbox access review | Quarterly |
| Access | Run a joiner and leaver checklist within one business day | HR and IT | Closed tickets | Every event |
| Access | Disable dormant accounts after the agreed period | IT lead | Dormant account report | Quarterly |
| Domain | Publish SPF and keep it within DNS lookup limits | IT lead | DNS record and check | Quarterly |
| Domain | Sign all sending domains with DKIM and rotate keys | IT lead | Selector and key record | Annual |
| Domain | Move DMARC from monitoring to quarantine or reject | IT lead | Policy record and reports | Quarterly |
| Domain | Monitor lookalike domains and brand abuse | IT and communications | Takedown log | Quarterly |
| Devices | Require managed, patched devices for mail access | IT lead | Device compliance report | Monthly |
| Devices | Encrypt laptops and phones that hold mail | IT lead | Encryption report | Quarterly |
| Devices | Set session timeout and re-authentication for webmail | IT lead | Configuration export | Annual |
| Data handling | Require a verified callback for bank detail changes | Finance controller | Change log | Every event |
| Data handling | Classify and protect sensitive attachments | Data owner | DLP rules and exceptions | Quarterly |
| Data handling | Prohibit personal mailboxes for business records | Operations | Policy acknowledgement | Annual |
| Phishing | Provide a report button and a triage route | IT lead | Report queue | Monthly |
| Phishing | Run simulations and targeted training | IT and HR | Completion and failure trend | Quarterly |
| Phishing | Publish payment-fraud escalation steps | Finance and IT | One-page procedure | Annual |
| Monitoring | Alert on forwarding rules, mass deletes and impossible travel | IT lead | Alert rule list | Quarterly |
| Monitoring | Review DMARC aggregate reports | IT lead | Review notes | Monthly |
| Monitoring | Retain mail logs for incident investigation | IT lead | Retention setting | Annual |
| Third parties | Assess mail-related vendors and subprocessors | IT and procurement | Questionnaire | Annual |
| Continuity | Document mail flow fallback and mailbox export | IT lead | Runbook and test record | Annual |
Verification tests
A policy is only real when someone tests it. Run these checks at least once a year, and record the result next to the control:
- Send a spoofed message from an external address and confirm the DMARC policy rejects or quarantines it.
- Try an obsolete authentication path, such as legacy IMAP or SMTP, and confirm it is blocked.
- Ask HR for a leaver from last month and confirm access was removed on the recorded date.
- Send a fake supplier email changing bank details and confirm finance calls a known number before acting.
- Restore a deleted mailbox and measure how long it takes.
- Sample ten mailbox forwarding rules and confirm each one has a business reason.
- Confirm a mailbox export can be read by the finance team without the original vendor's tool.
Sign-off
The policy owner signs the annual review. The IT lead signs the technical controls and test results. The finance controller signs the payment-change procedure. Management signs the exceptions, with an expiry date and a remediation owner. Keep the signed copy with the evidence pack, not only in the policy folder. That pack is the first thing an auditor or insurer will ask for.
Review triggers
Review the policy outside the annual cycle when a domain is added, a mailbox is migrated, a senior administrator leaves, a supplier changes its mail platform, an incident involves email, or the business opens a new office. Record the trigger, the change made and who approved it. A policy that only changes at the annual meeting is usually out of date within a quarter. Set the next review date at sign-off, and treat an unrenewed exception as an expired control.
Common gaps
- MFA enforced for staff but not for administrators or shared mailboxes.
- SPF and DKIM published, while DMARC stays in monitoring mode indefinitely.
- A leaver checklist that starts when IT is told, rather than when HR records the exit.
- Phishing training measured by completion, with no review of reported messages.
- No out-of-band verification for payments, so a convincing email is enough to change a bank account.
- An acceptable-use policy that ignores personal devices and messaging apps used for business.
Numbers for the monthly review
- Mailbox MFA coverage, including administrators.
- Domains with an enforcing DMARC policy.
- Time from leaver record to access removal.
- Phishing reports per hundred staff and the share confirmed as malicious.
- Open policy exceptions and their age.
- Payment-change requests verified by callback.
Implementing the policy with support
We implement and review these controls through Managed Technology & Cybersecurity, from domain authentication to mailbox monitoring. The pricing page explains how an assessment or a monthly retainer is scoped. For the human side of the same risk, read what phishing prevention for employees costs.
Sources
- RFC 7208, Sender Policy Framework, accessed 17 November 2026.
- RFC 6376, DomainKeys Identified Mail, accessed 17 November 2026.
- RFC 7489, Domain-based Message Authentication, Reporting and Conformance, accessed 17 November 2026.
- NIST SP 800-63B-4, Digital Identity Guidelines, accessed 17 November 2026.
- CISA, Recognize and Report Phishing, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.