In short
An email security policy is the document that states how an organisation protects its email. It should cover acceptable use, account security, handling of suspicious messages, sending sensitive data, technical controls and incident reporting. Each clause works only if a control enforces it, such as filtering, authentication, encryption or DLP. We can help put those controls in place.
Get a quote for email security
Tell us roughly how many users or sites you have and we will come back to you with options and a quote.
What an email security policy is for
A policy does three jobs. It tells staff what is expected of them in plain terms. It records the decisions the organisation has made about its email, so they survive a change of IT manager or supplier. And it gives an auditor, insurer or customer something to check your practice against.
A good policy is short. Staff rules go in the main body; technical standards go in an appendix that IT maintains. The policy should name an owner and a review date, and be reviewed when your mail platform or email security products change.
The sections to include
| Section | What it should say |
|---|---|
| Scope and ownership | Who and what the policy covers (staff, contractors, shared mailboxes, personal devices) and who owns it |
| Acceptable use | What business email may be used for, and the rule on forwarding work mail to personal accounts |
| Accounts and sign-in | Multi-factor authentication for every mailbox, password rules and what happens to a leaver's mailbox |
| Suspicious messages | How to report a suspected phishing email and what not to do with it |
| Payments and bank details | That a change of bank details or an urgent payment request received by email is always verified by another route |
| Sending sensitive information | Which information must be encrypted, and how |
| Signatures and disclaimers | That business email carries the approved signature and company details |
| Retention | How long email is kept, and where |
| Technical controls | The filtering, authentication, encryption and DLP the organisation runs (as an appendix) |
| Incidents | Who to tell, and how quickly, if a mailbox is compromised or data is sent to the wrong person |
Not sure which option fits? Ask us
Tell us what you need and we will recommend the right option for your organisation, with a quote.
Best practices to write in
These are the email security best practices that most often separate organisations that suffer email fraud from those that do not:
- Turn on multi-factor authentication for every mailbox, including shared and administrator accounts
- Configure the protection you already own in Microsoft 365 or Google Workspace before buying more
- Publish SPF, DKIM and DMARC (opens in a new tab) for every domain you own, including the ones that send no mail
- Verify any change of bank details by phone, using a number you already hold
- Encrypt personal and financial data sent outside the organisation
- Give staff one obvious way to report a suspicious message, and act on the reports
- Remove mailbox access on the day someone leaves
- Review mailbox forwarding rules and third-party app access regularly
- Practise: run awareness training and simulated phishing through the year
The NCSC publishes guidance for organisations on defending against phishing and on email security and anti-spoofing, and both are a sound basis for the technical appendix.
Sources (checked 11 November 2026): NCSC, "Phishing attacks: defending your organisation" and "Email security and anti-spoofing".
The controls each clause relies on
A clause that nothing enforces is a hope. This table pairs each policy area with the control that makes it real:
| Policy clause | Control that enforces it | Read more |
|---|---|---|
| Staff must not be exposed to phishing and malware | Email filtering and an anti-phishing layer | Email filtering, anti-phishing solutions |
| Nobody may send email as our domain | SPF, DKIM and DMARC | Email authentication |
| Sensitive data must be encrypted in transit | Policy-based encryption | Email encryption |
| Sensitive data must not leave by mistake | Email DLP and misdirected-email checks | Email DLP |
| Payment fraud must be caught | Impersonation detection, plus the verification rule | Business email compromise |
| Compromised accounts must be found quickly | Account takeover detection and sign-in controls | Email account takeover |
| Every email carries the approved signature and disclaimer | Central email signature management | Exclaimer |
| Staff must recognise and report phishing | A report button and awareness training | Phishing protection |
If a clause in your draft has no control behind it, either add the control or reword the clause to what you can enforce.
Is email security the right fit for you?
We will check it against your systems and requirements and recommend the right option.
How we help
We supply and help set up the controls a policy depends on: filtering and anti-phishing, authentication, encryption, DLP and signature management. If you are writing or revising a policy, we can review what your mail platform and current products already enforce and where the gaps are, so the document matches what really happens. Contact us with your mail platform and what you run today.
What affects email security pricing
Writing the policy costs only time. The cost comes with the controls each clause relies on: filtering and impersonation protection in an email security plan, encryption for sensitive mail and authentication on your domains, each priced by the product and plan you choose. We can quote the controls your policy calls for.
Get a quote for email security
Tell us what you need and we will come back to you with a quote.
How Forever Systems helps with email security
We are an independent UK IT and cyber security provider. We supply several email security platforms, so we can suggest what suits your mail system, your risks and your budget.
- Start with what you have: we can review the protection already built into Microsoft 365 or Google Workspace before suggesting anything extra
- Compare like for like: API-based protection, secure email gateways and email filtering, encryption services and DLP from the vendors we supply, explained in plain English
- Get authentication right: we help you plan SPF, DKIM, DMARC and MTA-STS so genuine mail is delivered and spoofed mail is not
- Deployment help: connecting a platform to Microsoft 365 or Google Workspace, mail routing changes and policy set-up, scoped at quote
- Email signatures: one approved signature and disclaimer on every email with Exclaimer email signature management
- People and backup too: security awareness training, Check Point Email Security and Sophos from our specialist sites
Tell us about your mail system and we will suggest options, with pricing confirmed at quote.
Frequently asked questions
What is an email security policy?
An email security policy is a written statement of how an organisation protects its email. It sets rules for staff, such as reporting suspicious messages and encrypting sensitive data, and records the technical controls the organisation runs, such as filtering, authentication and encryption.
What should an email security policy include?
Scope and ownership, acceptable use, account security and multi-factor authentication, handling of suspicious messages, verification of payment requests, rules for sending sensitive information, signatures and disclaimers, retention, the technical controls in place and how to report an incident.
What are email security best practices for a business?
Use multi-factor authentication on every mailbox, configure the protection built into your mail platform, publish SPF, DKIM and DMARC, verify bank detail changes by another route, encrypt sensitive data, make reporting easy, remove leavers' access promptly and train staff regularly.
Who should own the email security policy?
Usually the person responsible for information security or IT, with input from compliance or legal for the data protection clauses and from finance for the payment verification rule. It needs a named owner and a review date.
How often should an email security policy be reviewed?
At least once a year, and whenever something material changes: a new mail platform, a new email security product, a merger, or an incident that showed a gap.
Still have a question about email security?
Ask us and a member of our team will get back to you.