Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 5 min read

Business email security policy checklist

A working email security policy checklist with owners, evidence, frequency and sign-off, from account access and DMARC to fraud escalation and review.

E
EncryptTechBD · 0 comments
Bundle of keys on a dark surface
Photo: George Becker / StockSnap

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

SectionControlOwnerEvidenceFrequency
GovernanceName a policy owner and a deputyManaging directorSigned appointmentAnnual
GovernanceDefine scope: domains, mailboxes, aliases and contractorsIT leadMailbox inventoryAnnual
GovernanceApprove acceptable use and data classification rulesManagementSigned policyAnnual
GovernanceSet retention, export and legal hold rulesIT and legalRetention scheduleAnnual
AccessEnforce MFA on every mailbox, including administratorsIT leadTenant MFA reportMonthly
AccessUse single sign-on and role-based administrationIT leadRole exportQuarterly
AccessProhibit shared passwords for shared mailboxesIT leadMailbox access reviewQuarterly
AccessRun a joiner and leaver checklist within one business dayHR and ITClosed ticketsEvery event
AccessDisable dormant accounts after the agreed periodIT leadDormant account reportQuarterly
DomainPublish SPF and keep it within DNS lookup limitsIT leadDNS record and checkQuarterly
DomainSign all sending domains with DKIM and rotate keysIT leadSelector and key recordAnnual
DomainMove DMARC from monitoring to quarantine or rejectIT leadPolicy record and reportsQuarterly
DomainMonitor lookalike domains and brand abuseIT and communicationsTakedown logQuarterly
DevicesRequire managed, patched devices for mail accessIT leadDevice compliance reportMonthly
DevicesEncrypt laptops and phones that hold mailIT leadEncryption reportQuarterly
DevicesSet session timeout and re-authentication for webmailIT leadConfiguration exportAnnual
Data handlingRequire a verified callback for bank detail changesFinance controllerChange logEvery event
Data handlingClassify and protect sensitive attachmentsData ownerDLP rules and exceptionsQuarterly
Data handlingProhibit personal mailboxes for business recordsOperationsPolicy acknowledgementAnnual
PhishingProvide a report button and a triage routeIT leadReport queueMonthly
PhishingRun simulations and targeted trainingIT and HRCompletion and failure trendQuarterly
PhishingPublish payment-fraud escalation stepsFinance and ITOne-page procedureAnnual
MonitoringAlert on forwarding rules, mass deletes and impossible travelIT leadAlert rule listQuarterly
MonitoringReview DMARC aggregate reportsIT leadReview notesMonthly
MonitoringRetain mail logs for incident investigationIT leadRetention settingAnnual
Third partiesAssess mail-related vendors and subprocessorsIT and procurementQuestionnaireAnnual
ContinuityDocument mail flow fallback and mailbox exportIT leadRunbook and test recordAnnual

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

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes