How to Encrypt Email Attachments — and Why Most Organizations Still Get It Wrong
Most organizations have some form of email encryption in place. What far fewer realize is that their encryption stops at the email — not the attachment. The file that contains the sensitive data (the contract, the patient record, the financial report) travels onward without protection the moment it's downloaded, forwarded, or saved to a new device.
Understanding how to encrypt email attachments — not just the message — is the difference between security that holds and security that only looks good until something goes wrong.
Why Email Encryption Doesn't Automatically Protect Your Attachments
There are two common forms of email encryption, and neither one fully solves the attachment problem on its own.
TLS (Transport Layer Security) protects email and attachments in transit between servers — usually just for an instant while it's in motion. It's built into most major email providers and operates invisibly — which is useful, but limited. TLS provides no protection once the email is delivered. If a message is forwarded, a server is compromised, or an attachment is saved locally, your file is not protected by TLS.
Standard end-to-end encryption protects the message body from sender to recipient, which is meaningfully stronger. But many implementations don't extend that protection to the attachment itself after it's been saved to a desktop — and none of them give the sender ongoing control over what happens to the file.
That's the gap where data breaches happen. The most sensitive information in most emails isn't the message body — it's what's attached to it. And once that data has left your organization's perimeter, it's incredibly difficult (if not impossible) to claw back.
Recommended Reading: TLS vs. End-to-End Encryption — What's the Difference?
What's at Stake with Unencrypted Attachments
The consequences of unprotected attachments have grown significantly more severe.
According to IBM's 2025 Cost of a Data Breach Report, the average U.S. data breach now costs $10.22 million — an all-time high. Customer PII is the most frequently compromised data type, appearing in 53% of all breaches analyzed. And email remains one of the primary attack vectors: a misdirected email attachment, a forwarded thread, a downloaded file on an unmanaged device — each one is a potential breach with real regulatory exposure.
The regulatory environment has tightened to match. In January 2025, HHS proposed amendments to the HIPAA Security Rule that would transform encryption from an "addressable" specification — meaning organizations could opt out with justification — to an effective requirement for all covered entities and business associates. For healthcare organizations, the question of how to encrypt email attachments is no longer discretionary.
Similar requirements apply under CMMC for defense contractors handling Controlled Unclassified Information (CUI), FedRAMP for cloud services used by federal agencies, and a growing body of state privacy laws now in effect across 20 U.S. states. In each case, the expectation is the same: sensitive data in transit must be protected, and "protected in transit" means the attachment, not just the email wrapper.
How to Encrypt Email Attachments with Virtru
Virtru for Email integrates directly into Gmail and Microsoft Outlook, adding attachment encryption without changing how your team works. There's no separate portal, no password-protected ZIP files, no friction for recipients.
When you compose a message with Virtru enabled, attachments are encrypted using the Trusted Data Format (TDF) — an open standard that embeds encryption and access policy directly into the file itself. Protection is applied at the source, before the file leaves your environment, and it stays with the file regardless of where it goes next.
Beyond encryption, Virtru for Email lets you apply granular controls to every attachment you send:
- Access controls — specify exactly who can open the file, down to the individual recipient
- Expiration dates — set a time limit after which the file can no longer be accessed
- Watermarks — add visible attribution to help deter unauthorized sharing
- Real-time revocation — change or remove access at any point, even after the email has been delivered and the attachment downloaded

That last capability is where TDF-based encryption fundamentally differs from conventional approaches. Because policy is embedded in the file rather than managed at the email server level, access decisions are enforced at the moment someone attempts to open the file — not at the moment it was sent. An attachment that shouldn't be accessible anymore isn't, regardless of where it has traveled or how many times it was forwarded.
Protection That Travels With the File
The core limitation of most email security tools is that they secure the channel, not the content. Once an attachment clears the perimeter — forwarded externally, downloaded to a personal device, saved to a shared drive — the protection ends.
Virtru's approach is different by design. Because TDF embeds the access policy into the file itself, that policy portability means protection travels with the data through every environment it enters. A recipient opening a protected attachment two weeks later, on a different device, after forwarding the message internally — the access check still runs. If access has been revoked, the file doesn't open.
This is data-centric security applied to one of the most common workflows in any organization: sending a file by email. The encryption isn't attached to the network path. It's attached to the data.
Works Where Your Team Already Works
Virtru for Email doesn't ask your organization to change tools, retrain staff, or adopt a new communication platform. It works within Gmail and Outlook — the email clients your teams use today. Encryption is applied with a toggle; controls are set in a sidebar; recipients access protected files through a straightforward, browser-based flow that requires no software installation.
Security should empower, not stifle. The right attachment encryption solution makes secure behavior the easiest behavior — not an additional step that gets skipped when someone is in a hurry.
For organizations managing compliance requirements, Virtru for Email also maintains comprehensive audit logs of all access attempts and decisions, giving you the visibility you need without manual tracking.
Start Protecting Attachments Today
Email attachment encryption isn't a premium feature reserved for high-security environments. It's the baseline that responsible data handling requires — and with HIPAA amendments, CMMC requirements, and a tightening state privacy landscape, the window for treating it as optional is closing.
Virtru Email Encryption is available for Gmail and Microsoft Outlook. Integration takes minutes. The protection lasts as long as the data does. To see how it works, contact our team for a demo.
Frequently Asked Questions about Encrypting Email Attachments
The fastest way to encrypt email attachments in Outlook is with an add-in like Virtru for Outlook. Once installed, you'll see a toggle in the Outlook compose window. Flip it on before you hit send, and every file attached to that message — Word docs, PDFs, spreadsheets — is encrypted with the message.
Native Microsoft 365 encryption (via Microsoft Purview) is another option. Go to New Message > Options > Encrypt, then choose an encryption policy. The limitation: this approach relies on Microsoft's key management, and recipients outside your Microsoft tenant may hit friction when opening attachments.
For organizations with stricter requirements — healthcare, legal, defense contracting — a dedicated solution like Virtru gives you persistent controls that travel with the file: you can set expiration dates, disable forwarding, and revoke access even after the email lands in the recipient's inbox.
If you've just received a file you can't open, don't worry — you almost certainly don't need to install anything. How you proceed depends on how the attachment was encrypted.
- Virtru-encrypted attachments: The sender's email will include a secure link or a protected file. Click Open with Virtru or open the file directly — you'll be prompted to authenticate (usually via Google or Microsoft sign-in, or a one-time verification code). No software installation required for recipients.
- Microsoft 365 / Purview-encrypted attachments: If you're in the same Microsoft tenant, attachments open normally. If you're external, you'll receive a message from Microsoft with a link to read the content in the browser or via a passcode. You may have to create an account or password to do so.
- S/MIME-encrypted attachments: You need the sender's public certificate installed in your email client. Open the email in Outlook or Apple Mail — if the certificate is in place, the attachment decrypts automatically.
- PGP/GPG-encrypted files: You need a PGP-compatible tool (like Kleopatra or GPG Keychain) and the sender's public key to decrypt the attachment locally.
If an encrypted attachment won't open, the most common reasons are: you're accessing it from a different email address than the one it was sent to, the sender has already revoked access, or the attachment has passed its expiration date.
There are two approaches: password-protect the PDF itself, or encrypt it as part of the email.
Option 1: Password-Protect the PDF file directly
Adobe Acrobat lets you add password protection to a PDF before you attach it. Go to File > Protect Using Password, set a password, and save. The recipient needs the password to open it. This works across any email platform but requires you to share the password separately — ideally through a different channel.
Option 2: Encrypt the PDF as part of an encrypted email
This is the more practical approach for business use. With Virtru for Outlook or Gmail, you compose your email with the PDF attached, toggle encryption on, and send. The PDF is wrapped in a Trusted Data Format (TDF) container that enforces access policy at the point of opening — no separate password to manage, and you retain the ability to revoke access or set an expiration date.
For regulated environments (HIPAA, CMMC, ITAR), encrypting at the email level — rather than password-protecting the file — is generally preferred because it creates an audit trail and gives administrators persistent control over the document after it's shared.
It depends on the encryption method.
TLS (Transport Layer Security) — the default "encryption" in most email systems, including Gmail and Outlook — protects data in transit between mail servers. It does not encrypt the content of the email or its attachments at rest. Once the message is delivered, TLS provides no protection.
End-to-end encryption tools like Virtru encrypt both the message body and all attachments together. The protection is tied to the content, not the connection — so the files remain encrypted even after delivery, and access is controlled by policy, not by network proximity.
Microsoft Purview / Office 365 Message Encryption: Yes, attachments sent with OME are encrypted. However, the encryption is managed by Microsoft, and control is limited once the message leaves your tenant. Persistent controls like revocation are not available in standard OME configurations.
S/MIME: Encrypts the entire message including attachments, but only between parties who have exchanged certificates.
The short answer: if you want attachment encryption that persists after delivery and gives you ongoing control, you need protection that travels with the data itself — not just with the connection.
Whether an encrypted attachment can be forwarded depends on the access controls set by the sender.
With native Microsoft 365 encryption, for example, forwarding restrictions can be applied — but only if the sender selects the Do Not Forward policy. By default, recipients can forward the email and, in some cases, the attachment becomes accessible to the new recipient.
With Virtru, forwarding is governed by the sender's policy settings. You can:
- Disable forwarding entirely — the recipient cannot share the file with others
- Allow forwarding while maintaining the encryption (the new recipient still has to authenticate)
- Revoke access at any time, which instantly locks the file for all recipients, including any forwarded copies
This matters because the threat isn't always an external attacker — it's a well-intentioned employee forwarding a sensitive document to a personal account, or sending it to the wrong external contact. Persistent forward controls close that gap.
That's what "integration, not replacement" means in practice — the same Outlook workflow you already use, with persistent control over where your files end up.
Most encryption tools designed for email support all common file types. With Virtru for Outlook and Gmail, any file you can attach to an email can be encrypted — including:
- Documents: PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), text files
- Images: JPEG, PNG, TIFF, and other image formats
- Compressed files: ZIP, 7-Zip
- CAD and design files: DWG, DXF (common in defense and manufacturing)
- Video and audio files
The encryption wraps the file in a protected container regardless of the file format. The recipient's access policy is enforced at the moment they try to open the file — the file type itself doesn't change that.
One practical note: some file types (like ZIP archives) should be encrypted at the email level rather than relying on the ZIP's built-in password protection, since ZIP encryption standards vary in strength and don't provide audit trails or revocation capabilities.
With modern email encryption solutions like Virtru, external recipients typically do not need to install any software.
When a recipient gets a Virtru-protected attachment, they open it through a secure web reader. Authentication is handled via their existing Google or Microsoft account, or through a one-time passcode sent to their email. The experience takes about 30 seconds for first-time users.
Older encryption standards require more setup:
- S/MIME requires recipients to have the sender's certificate installed in their email client — practical for internal use or established partner relationships, but creates friction for one-off external sharing.
- PGP requires recipients to have a PGP-compatible application and manage their own key pairs, which is too complex for most business workflows.
For organizations sharing sensitive files with clients, vendors, or partners who aren't on the same email platform, a solution that removes recipient-side friction is important. High-friction encryption tends to get bypassed — users find workarounds, and the files end up unprotected.
Signs that an attachment is encrypted:
- File extension change: Virtru-protected files have a
.tdfor.htmlextension wrapping the original file. If you seequarterly-report.xlsx.tdf, it's Virtru-encrypted. - Password prompt on open: A PDF or ZIP that immediately asks for a password has been encrypted at the file level.
- Secure reader redirect: If clicking the attachment opens a browser window asking you to sign in before viewing, the file is encrypted (common with Virtru, Microsoft Purview, and similar tools).
- Lock icon in email client: Some email clients (Outlook, Gmail) display a lock icon next to encrypted messages or attachments.
- Microsoft OME wrapper: If you receive a message from
no-reply@notify.microsoft.comwith a link to "Read the message," the original email and any attachments were encrypted with Microsoft 365 encryption.
If you're the sender and want to confirm that your attachments are encrypted — not just the message body — review your email encryption tool's settings. With Virtru, the encryption status (on/off) and access controls are visible in the compose window before you send.
Want to see how this works in Outlook? Virtru for Outlook integrates directly into your compose window — no IT overhaul, no new workflow. You can request a demo to see persistent attachment controls in action.
Editorial Team
The editorial team consists of Virtru brand experts, content editors, and vetted field authorities. We ensure quality, accuracy, and integrity through robust editorial oversight, review, and optimization of content from trusted sources, including use of generative AI tools.
View more posts by Editorial TeamSee Virtru In Action
Sign Up for the Virtru Newsletter
Dive Deeper

ITAR Compliant File Sharing: The Encryption Carve-Out Explained
/blog%20-%20enclave%20provider%20closing%20doors/enclave-closing-doors.webp)
When Your CMMC Enclave Provider Closes Its Doors: Why Ownership Matters More Than Ever

Three Strikes, You're Out: MOVEit's Latest Critical Flaw and What Comes Next
/blog%20-%20microsoft%20legal%20AI/miscrosoftlegal%20copy.webp)
Why Microsoft's New Legal Agent Needs Data-Centric Security to Deliver on Its Promise

HIPAA Compliance for HR Departments: What's Changed, What's Coming, and What to Do Now

How Banks, Mortgage Lenders, and Fintechs Protect Sensitive Financial Data with Virtru

Sent Doesn't Mean Gone: Why 'Revoke Access' Is a Finance Game-Changer

"This Message Will Self-Destruct": Secure Document Sharing With an Access Kill Switch

Email Encryption for Banks: What CISOs Need to Know in 2026
/blog%20-%20anthropic%20boat/anthropic-boat.webp)
Mythos Is a "Walls Crumbling" Moment — And We're Gonna Need a Smaller Boat
Book a Demo
Become a Partner
Contact us to learn more about our partnership opportunities.
Become a Compliance Champion
Contact us to learn more about our partnership opportunities.