The secure email standard
Emails sent to and from health and social care organisations must meet the secure email standard (DCB1596) so that everyone can be sure that sensitive and confidential information is kept secure.
Meeting the secure email standard
There are two ways to meet the secure email standard. Organisations must select one of these methods to comply.
- Implement an already compliant service such as NHSmail, Office 365 or Google Workspace for all staff at your organisation.
- Demonstrate your own service is compliant with the secure email standard by following the secure email accreditation process.
Implement an already compliant service
NHSmail
Meet the organisation requirements of the standard by following the steps below.
- Ensure there is a process in place to notify the NHSmail team upon becoming aware of any breach of security, including an actual, potential or attempted breach of, or threat to, the security policy and / or the security of the services or the systems used to provide the services.
- Health and care organisations SHOULD set policies and procedures for the use of secure email using mobile devices and ensure the email service enforces them.
- Health and care organisations SHOULD comply with the provisions of DCB0160: Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems.
- Health and care organisations MUST set policies and procedures for staff who use the secure email service to ensure that they understand how to use it appropriately and safely, including how to send emails to insecure email systems such as those used by patients.
- Migrate all users/staff to the NHSmail email service: To migrate all email users to NHSmail follow the migration guidance on the NHSmail support site.
Microsoft Office 365 (O365): Secure email configuration guide
Meet the organisation requirements of the standard by following the steps below.
- Ensure there is a process in place to notify the NHSmail team upon becoming aware of any breach of security, including an actual, potential or attempted breach of, or threat to, the security policy and/or the security of the services or the systems used to provide the services.
- Health and care organisations SHOULD set policies and procedures for the use of secure email using mobile devices and ensure the email service enforces them.
- Health and care organisations SHOULD comply with the provisions of DCB0160: Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems.
- Health and care organisations MUST set policies and procedures for staff who use the secure email service to ensure that they understand how to use it appropriately and safely, including how to send emails to insecure email systems such as those used by patients.
- Register compliance with the NHSmail team.
It is the responsibility of each organisation to verify their own configuration, to ensure that their environment has been configured appropriately. To assist we are providing a CIS (centre for Internet Security) Microsoft Office 365 foundation benchmark assessment Level 2 criteria that we assess against for compliance to the secure email standard.
Conformance to this standard will therefore be evidenced by completing an ITHC using the scope and CIS MIcrosoft 365 Foundation Benchmark Testing Results and Corrective Action Plan template. Each organisation should define any mitigation or remedial action plans and submit to NHS Digital Secure email standard service for assessment/approval. Further guidance can be found in the CIS Microsoft 365 Foundation Benchmark Testing Results and Corrective Action Plan template.
Microsoft Office 365 (O365) accreditations must include confirmation that the email service has been configured to securely communicate with NHSmail. The Microsoft Office 365: Secure email configuration guide has been co-produced with Microsoft, allowing instances of O365 to be enabled to securely route emails to and from NHSmail.
Google Workspace Secure email configuration guide
Meet the organisation requirements of the standard by following the steps below.
- Ensure there is a process in place to notify the NHSmail team upon becoming aware of any breach of security, including an actual, potential or attempted breach of, or threat to, the security policy and/or the security of the services or the systems used to provide the services.
- Health and care organisations SHOULD set policies and procedures for the use of secure email using mobile devices and ensure the email service enforces them.
- Health and care organisations SHOULD comply with the provisions of DCB0160: Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems.
-
Health and care organisations MUST set policies and procedures for staff who use the secure email service to ensure that they understand how to use it appropriately and safely, including how to send emails to insecure email systems such as those used by patients.
-
Register compliance with the NHSmail team: Google Workspace accreditations must include confirmation that the email service has been configured to securely communicate with NHSmail.
Google workspace: Secure email configuration guide has been co-produced with Google, allowing instances of Workspace to be enabled to securely route emails to and from NHSmail.
Exchange, hybrid or other email services
In addition to completing the organisation section of the standard, those hosting their own email services must submit assertions and evidence that they meet the ICT Service Provider elements of the standard. These will be reviewed by the NHS Digital Data Security Centre.
To help organisations with their accreditation process to the DCB1596 standard, we have provided Secure email standard (DCB159) guidance to help you understand what actions organisations need to take to make the changes in the DCB1596 secure email standard.
This list is maintained and updated as soon as an organisation accredits to the DCB1596 standard.
It was last updated on 16 January 2025.
Secure email accreditation process
The steps below illustrate the end to end accreditation process.
- Submission of a signed self-accreditation statement, with evidence.
- Evidence checked by the NHS Digital Data Security Centre and NHSmail team.
- Rectification of findings and re-submission to the NHSmail team.
- DCB1596 met.
Secure email accreditation templates
For any further queries regarding the secure email standard please log a request via NHS England ServiceNow You will receive a response within 10 working days.
In the 'Health and Care Organisation' section of the templates, please provide the name and date of the policy or document covering each requirement and ensure the requisite approvals are in place.
Conformance statements
The statements below confirm how Microsoft Office 365 and Google Workspace meet their email security obligations:
- DCB 1596 conformance statement for Microsoft Office 365
- DCB1596 conformance statement for Google Workspace
Re-accreditation
Accreditations to the secure email standard last for one calendar year. After this period organisations are required to re-accredit.
The re-accreditation process will involve the organisation re-submitting evidence for review. In most instances this will be very similar to the information previously submitted.
Penetration test results and ISO27001 certificates must be within the last 12 months.
As accreditations come to the end of their term the NHSmail team will send out a reminder to each organisation.
Contact
Accreditations are valid for one year and organisations should submit updated accreditation evidence via NHS England ServiceNow prior to the expiry date.
Last edited: 17 January 2025 9:50 am