What is email encryption, and how do you choose the right solution?
Email encryption is a method of encoding the content of an email so that only the intended recipient, with the correct key, can read the message. This protects against eavesdropping during transmission and helps organizations comply with privacy laws such as the GDPR. There are various forms of email encryption, each with its own strengths and weaknesses, and for organizations, this usually raises an additional question: how do you demonstrate that the transmission actually took place in a careful and controlled manner?
What types of email encryption are there?
TLS (Transport Layer Security). The most common form of encryption. TLS secures the connection between mail servers during transmission—often automatically—and is indicated by a padlock icon. However, once an email has been delivered, it remains unencrypted in the recipient’s inbox, in backups, and on any device that syncs with it.
S/MIME (Secure/Multipurpose Internet Mail Extensions). Provides end-to-end security via a digital certificate, for example in Outlook or Gmail. The downside: both the sender and the recipient need to have a certificate installed, which makes communication with external parties difficult in practice.
End-to-end encryption (such as PGP). Only the sender and recipient can decrypt the message—not even the email provider can. This offers the strongest protection, but requires a compatible recipient and usually a separate application or plug-in.
Why Standalone Encryption Is Often Not Enough for Organizations
TLS, S/MIME, and PGP primarily protect the content of a message during transmission. For organizations that send personal data or confidential documents, however, there is more at stake than just encryption: who has access to the message, how long will it remain available, and can the organization subsequently demonstrate that the transmission was carried out with due care?
The GDPR requires organizations to implement appropriate technical and organizational measures to protect personal data (Article 32 of the GDPR). Encryption is an important part of this, but not the only one: recipient verification, access control, and logging also play a role. This is where general encryption solutions often fall short, and where enterprise security platforms go a step further.
How FileCap Solves Email Encryption for Organizations
With FileCap, you can add an extra layer of security to your existing Outlook, Microsoft 365, or Gmail environment without requiring the recipient to have a certificate or a separate account. You send an email as usual, select the secure sending option, and the recipient verifies their identity before they can open the message.
This includes, among other things:
- Multiple verification methods for the recipient (password, code sent by email or text message, company password);
- Customizable availability and the ability to cancel a shipment after it has been shipped;
- DLP policies that automatically issue warnings or enforce secure transmission for sensitive data such as social security numbers or credit card numbers;
- Comprehensive logging and reporting for administrators;
- Storage within the EU with a European cloud provider.
FileCap is ISO 27001-certified. Learn more about FileCap’s approach to security on our security page, or about its compliance with the NTA 7516 healthcare standard on the page about FileCap and NTA 7516.
FileCap vs. Microsoft, S/MIME, and PGP
If you're already using Microsoft 365 or Outlook, it's worth taking a look first at the built-in options you already have and where their limitations lie. To do so, read our guide on email encryption in Microsoft 365 and Outlook.
Are you unsure whether encryption alone is sufficient, or whether your organization also needs access control and audit trails? Read about the difference between email encryption and secure email.
Conclusion
Email encryption comes in various forms, ranging from automatic TLS security to S/MIME and end-to-end encryption with PGP. For personal use, this is often sufficient, but organizations that send personal data or confidential documents generally need more: control over access, recipient verification, and the ability to demonstrate compliance with the GDPR.
With FileCap, you can add that extra layer of security to your existing email environment—without certificates, separate software, or complicated IT processes.
Want to see how this works in your organization?
Request a demo or try FileCap free for 30 days.
Frequently Asked Questions
What is the difference between TLS and end-to-end encryption?
TLS only secures the connection between mail servers during transmission; the email is then stored unencrypted in the mailbox. End-to-end encryption, such as PGP, ensures that only the sender and recipient can read the message—not even the email provider itself.
Is email encryption required under the GDPR?
The GDPR does not prescribe any specific technology, but it does require organizations to implement appropriate technical and organizational measures when processing personal data. Encryption is often considered an appropriate measure, especially when dealing with sensitive data.
Can I use email encryption without the recipient needing any additional software?
With S/MIME and PGP, the recipient usually needs a certificate or application. With FileCap, the recipient verifies their identity using a simple method, such as a password or code, without having to create an account or install any software.
Does FileCap also work with Gmail?
Yes, in addition to the Outlook add-in and Microsoft 365 integration, you can also use FileCap via the web portal from any browser, including Gmail or Hotmail/Outlook.com.